| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Dian Fay <di(at)nmfay(dot)com>, Jim Nasby <jim(dot)nasby(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: add function argument names to regex* functions. |
| Date: | 2024-05-15 20:24:40 |
| Message-ID: | CAKFQuwZVrhKozs0+DQ_9zKmjAvFkQcgs9MBLMsahScqqY5n7MA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 15, 2024 at 1:19 PM Robert Haas <robertmhaas(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chapman Flack | 2024-05-15 20:28:35 | Re: add function argument names to regex* functions. |
| Previous Message | Tom Lane | 2024-05-15 20:23:23 | Re: Why does pgindent's README say to download typedefs.list from the buildfarm? |