Re: add function argument names to regex* functions. - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: add function argument names to regex* functions.
Date
Msg-id CAKFQuwZVrhKozs0+DQ_9zKmjAvFkQcgs9MBLMsahScqqY5n7MA@mail.gmail.com
Whole thread Raw
In response to Re: add function argument names to regex* functions.  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: add function argument names to regex* functions.
List pgsql-hackers
On Wed, May 15, 2024 at 1:19 PM Robert Haas <robertmhaas@gmail.com> wrote:

So my point was: to me, N is more self-documenting than replace_at,
and less self-documenting than count or occurrence.

If your mileage varies on that point, so be it!


Maybe just "match" instead of "replace_match".

Reading this it strikes me that any of these parameter names can and probably should be read as having "replace" in front of them:

replace N
replace count
replace occurrence
replace match

Saying replace becomes redundant:
replace replace at
replace replace match

David J.

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Why does pgindent's README say to download typedefs.list from the buildfarm?
Next
From: Chapman Flack
Date:
Subject: Re: add function argument names to regex* functions.