https://bugs.exim.org/show_bug.cgi?id=2128
Philip Hazel <p...@hermes.cam.ac.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Philip Hazel <p...@hermes.cam.ac.uk> ---
I am amazed that nobody has picked this up before. It was in 2008 that somebody
send me a patch to implement REG_STARTEND and I don't think the code has
changed since. Googling for the spec of REG_STARTEND produces man pages that do
not seem to specify what the returns should be. However, I believe you! And the
fixed version does seem more sensible.
There are no tests for REG_STARTEND in the PCRE1 package because it is now just
too hard to hack around in pcretest. That caused there to be no tests in PCRE2
either (because the PCRE1 tests were the starting point), but I have now
rectified that, since pcre2test is a much tidier program and needed only a very
small patch.
I have patched both PCRE1 and PCRE2 (it is a very trivial patch to the code; a
bit more to the documentation) to fix this bug. The next releases will contain
the fixed code.
--
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
