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

https://bugs.exim.org/show_bug.cgi?id=2106 Philip Hazel changed: What|Removed |Added Status|NEW |RESOLVED

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

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #12 from Philip Hazel --- I have implemented PCRE2_LITERAL and added REG_NOSPEC to make use of it. I have put a small warning in the pcre2api document that it is not the most efficient way of matching fixed strings,

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

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #11 from Philip Hazel --- (In reply to Kyle J. McKay from comment #9) > Bummer dude. I filed enhancement request bug #2131 asking for > support for Unicode Collation Algorithm matching (icu does that). > You can

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

https://bugs.exim.org/show_bug.cgi?id=2106 Zoltan Herczeg changed: What|Removed |Added CC||hzmes...@freemail.hu ---

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

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #9 from Kyle J. McKay --- (In reply to Philip Hazel from comment #6) > > > REG_STARTEND is already there. > > > > Except that it's not *BSD compatible -- see bug #2128 > > Now mended. Very nice. Thank you. :) > >

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

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #8 from Philip Hazel --- FYI: I have implemented REG_PEND. Awaiting any feedback on my previous long comment. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at

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

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #7 from Philip Hazel --- I've just spent some time fiddling around with timing experiments and the results are illuminating. I used gcc 7.1.1 with -O0 because optimization often defeats one's attempts to repeat code

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

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #6 from Philip Hazel --- (In reply to Kyle J. McKay from comment #5) > > REG_STARTEND is already there. > > Except that it's not *BSD compatible -- see bug #2128 Now mended. > I might expect matching a fixed pattern

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

https://bugs.exim.org/show_bug.cgi?id=2106 --- Comment #4 from Philip Hazel --- (In reply to Kyle J. McKay from comment #3) > > I'm coming at this from the point of view of wanting a drop-in replacement > (at the source code level -- in other words a recompilation is

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 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

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

https://bugs.exim.org/show_bug.cgi?id=2106 Kyle J. McKay changed: What|Removed |Added CC||mack...@gmail.com ---