| From: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Some qualms with the current description of RegExp s,n,w modes. |
| Date: | 2014-06-06 00:56:35 |
| Message-ID: | CAKFQuwYumYU723Or79gFxd-Rr8ZtvFyk98KFG0Dm0kxYDLB65Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
>
>
>> Or just "newline-sensitive matching" ... does "full" add anything?
>>
>
And since I'm nit-picking anyway - the word "sensitive" does nothing for
me. Simply "newline-matching" would be sufficient, ideally. i.e., Do ".
[^]" and "^$" match the newline character, or not.
[w] anchor newline-matching
[n] dot/inverse-bracket newline-matching
[s] newline-matching
These are precise, what-oriented, names compared to:
[w] record mode
[n] multi-line mode
[s] single-line mode
which are more descriptive, use-oriented, names.
Use of these label sets is not mutually exclusive...
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Johnston | 2014-06-08 14:49:19 | Re: [9.3] Should we mention "set_config(...)" in 18.1.3 in Server Configuration? |
| Previous Message | David Johnston | 2014-06-06 00:32:38 | Re: Some qualms with the current description of RegExp s,n,w modes. |