Re: patch adding new regexp functions - Mailing list pgsql-patches

From Neil Conway
Subject Re: patch adding new regexp functions
Date
Msg-id 46004FC9.3000204@samurai.com
Whole thread Raw
In response to Re: patch adding new regexp functions  (Jeremy Drake <pgsql@jdrake.com>)
Responses Re: patch adding new regexp functions
List pgsql-patches
Jeremy Drake wrote:
> The patch has been sitting in the unapplied patches queue for a while, and
> the inevitable bitrot finally caught up with it.  This version of the
> patch is exactly the same as the one in the patches queue, except for
> using new, non-conflicting oids for the functions.
>
Applied -- thanks for the patch. BTW, a few cosmetic comments:

* #includes should be sorted alphabetically (unless another #include
sort order rules take precedence, like including "postgres.h" first).

* patch included some trailing CR line endings

* IMHO using "++var" in the increment component of a for loop is bad
style in C (if only because it is needlessly inconsistent; good C++
style is not necessarily good C style)

* Comments like "/* get text type oid, too lazy to do it some other way
*/" do not exactly inspire confidence :)

-Neil


pgsql-patches by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Make CLUSTER MVCC-safe
Next
From: Bruce Momjian
Date:
Subject: Re: Code-Cleanup: char* -> const char*