[pcre-dev] [Bug 2120] PCRE2_NO_UTF_CHECK does not disable all checks

https://bugs.exim.org/show_bug.cgi?id=2120 --- Comment #17 from Rob --- I appreciate the conceptual difficulty of trying to reconcile two incompatible paradigms. >From my perspective, the only change i need is that it doesnt throw an error. i rewrote your escape handler so

[pcre-dev] [Bug 2120] PCRE2_NO_UTF_CHECK does not disable all checks

https://bugs.exim.org/show_bug.cgi?id=2120 --- Comment #18 from Philip Hazel --- I have just committed a documented patch that implements additional options within the compile context, the first of which is PCRE2_EXTRA_ALLOW_SURROGATE_ESCAPES. This is available in UTF-8

Re: [pcre-dev] [Bug 2106] Please add support for parsing POSIX basic & extended regular expressions

I have had a similar problem in my port to z/OS.I am not near my computer but I will try to share my solution tonightZA Sent from Yahoo Mail on Android On Wed, May 17, 2017 at 1:20 PM, ad...@bugs.exim.org wrote: https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment

[pcre-dev] [Bug 2120] PCRE2_NO_UTF_CHECK does not disable all checks

https://bugs.exim.org/show_bug.cgi?id=2120 --- Comment #19 from Zoltan Herczeg --- Yes, the standard is quite strictly defined: https://www.ecma-international.org/ecma-262/6.0/#sec-patterns -- You are receiving this mail because: You are on the CC list for the bug. --

[pcre-dev] Fw: [Bug 2106] Please add support for parsing POSIX basic & extended regular expressions

I have checked my solution and it is somewhat relevant for the question as asked.  As I've mentioned, I'd struggled with the same issue.  In the z/OS environment I am not required to provide both POSIX and PCRE at the same time.   Also, for technical reasons I have to supply short name (8

[pcre-dev] [Bug 2106] Please add support for parsing POSIX basic & extended regular expressions

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #2 from Philip Hazel --- Thanks for this additional information. In fact we are already in the process of testing translation functions within PCRE2. There is a general API which can handle a number of different