From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Thorsten Glaser <t(dot)glaser(at)tarent(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14628: regex description in online documentation misleadingly/wrong |
Date: | 2017-04-20 17:47:02 |
Message-ID: | CAKFQuwapym_7jXXrOEFJ=yMv1zMG+d-pVHPxDK=gJGpKWhZ0EA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Apr 20, 2017 at 10:15 AM, Thorsten Glaser <t(dot)glaser(at)tarent(dot)de>
wrote:
> On Thu, 20 Apr 2017, David G. Johnston wrote:
>
> > Based on what you wrote below I'd maybe (though leaning toward not)
> modify
> > the chapter title to "POSIX (ARE) Regular Expressions"
>
> Your ARE are not POSIX regular expressions, period.
>
Skimming these:
http://www.regular-expressions.info/tcl.html
http://www.regular-expressions.info/posixbrackets.html
I suppose doing s/POSIX/TCL/g (limited to regular expression usage
obviously) would be an acceptable change.
Adding "Advanced" in appropriate places would be good too.
I suppose I took it as face value that we were POSIX compliant rather than
just POSIX ERE compatible. It sounds like that was a false premise,
though, and that our use of POSIX, for those people for whom its not just a
noise word, implies a set of acceptable behaviors that we far exceed.
Calling it TCL is more accurate and allows people to easily tie back our
implementation to external resources like the first one above.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Clough | 2017-04-21 10:28:31 | Incorrect type in pg_cast causes Postmaster to core dump |
Previous Message | Thorsten Glaser | 2017-04-20 17:15:53 | Re: BUG #14628: regex description in online documentation misleadingly/wrong |