We had had a similar discussion a few years back, where I stated that a certain
usage is wrong and you answered that changing PCRE will break a few patterns
who may rely on the wrong usage. In the end you've adopted my view after I'd
asked to allow me an exception in the z/OS EBCDIC specific implementation. My
view is that if something is wrong, or in this case "not well defined" then
PCRE2 should stay clear from that thing, despite the fact that some edge case
patterns may suffer and some users would be annoyed. The Perl community is
assertive enough and says No! when No is due, and the PCRE2 community should
take that position as well.
Oh, and if I read correctly, the example that was used is NOT a negative
lookaround
Ze'ev Atlas
--
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
