Re: [pcre-dev] Typo about (?^)

2021-06-20 Thread ND via Pcre-dev
On 2021-06-20 11:27, Philip Hazel wrote: A little bit further up from what you quoted, the docs say this: "The two "extended" options are not independent; unsetting either one cancels the effects of both of them." So (?-x) and (?-xx) are the same, and unset both (?x) and (?xx). I apologize

Re: [pcre-dev] Typo about (?^)

2021-06-20 Thread Philip Hazel via Pcre-dev
A little bit further up from what you quoted, the docs say this: "The two "extended" options are not independent; unsetting either one cancels the effects of both of them." So (?-x) and (?-xx) are the same, and unset both (?x) and (?xx). Regards, Philip On Sat, 19 Jun 2021 at 16:57, ND via

[pcre-dev] Typo about (?^)

2021-06-19 Thread ND via Pcre-dev
PCRE docs say: If the first character following (? is a circumflex, it causes all of the above options to be unset. > Thus, (?^) is equivalent to (?-imnsx). There is "xx" option. So may be docs have a typo? - "all of the above options" -> "all of the above options but xx" - or "(?^) is

[pcre-dev] Typo about \N ?

2011-05-02 Thread ND
Pcrecompat man page says: 5. The following Perl escape sequences are not supported: \l, \u, \L, \U, and \N. In fact these are implemented by Perl's general string-handling and are not part of its pattern matching engine. If any of these are encountered by PCRE, an error is generated. \N