| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Joel Jacobson <joel(at)compiler(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Bizarre behavior of \w in a regular expression bracket construct |
| Date: | 2021-02-24 17:11:51 |
| Message-ID: | 4099574.1614186711@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> On 2021-Feb-23, Tom Lane wrote:
>> * Create infrastructure to allow treating \w as a character class
>> in its own right. (I did not expose [[:word:]] as a class name,
>> though it would be a little more symmetric to do so; should we?)
> Apparently [:word:] is a GNU extension (or at least a "bash-specific
> character class"[1] but apparently Emacs also supports it?); all the
> others are mandated by POSIX[2].
> I think it'd be fine to expose [:word:] ...
Yeah, I'd independently come to the same conclusion. This GNU precedent
offers even more basis for that, though.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-02-24 17:14:47 | Re: Bizarre behavior of \w in a regular expression bracket construct |
| Previous Message | Tom Lane | 2021-02-24 17:09:02 | Re: Bizarre behavior of \w in a regular expression bracket construct |