https://bugs.exim.org/show_bug.cgi?id=2495
Philip Hazel <p...@hermes.cam.ac.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|NEW |RESOLVED
--- Comment #1 from Philip Hazel <p...@hermes.cam.ac.uk> ---
As you say, this bug is fixed in PCRE2. See change #1 in the PCRE2 ChangeLog
for 10.30. This occurred during the major redesign and refactoring of the code
in PCRE2, precisely so that this and similar issues could be addressed. PCRE1
is effectively at End of Life. Only very minor fixes are happening, and there
will probably only be one more release. This is not a minor issue - it took a
big redesign to get it right. Lookarounds didn't exist in the very original
PCRE - though added soon after, they weren't being thought about at the start,
so in some sense were bodged in, and it turned out that the backtracking wasn't
quite right. The bottom line is that this will not be fixed in PCRE1. In fact,
this is a duplicate of #1887.
*** This bug has been marked as a duplicate of bug 1887 ***
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/pcre-dev
