https://bugs.exim.org/show_bug.cgi?id=1798
Philip Hazel <ph10@???> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Philip Hazel <ph10@???> ---
Thank you for noticing this, but it is in fact a deliberate change. The
ChangeLog for 10.21 says this:
108. If a pattern that was compiled with PCRE2_EXTENDED started with white
space or a #-type comment that was followed by (?-x), which turns off
PCRE2_EXTENDED, and there was no subsequent (?x) to turn it on again,
pcre2_compile() assumed that (?-x) applied to the whole pattern and
consequently mis-compiled it. This bug was found by the LLVM fuzzer. The fix
for this bug means that a setting of any of the (?imsxU) options at the start
of a pattern is no longer transferred to the options that are returned by
PCRE2_INFO_ALLOPTIONS. In fact, this was an anachronism that should have
changed when the effects of those options were all moved to compile time.
...It should have included (?J) as well as (?imsxU). The only in-pattern
options that now are returned are those that start (* for example (*UTF). I
have added some words to the pcre2api man page to clarify this.
--
You are receiving this mail because:
You are on the CC list for the bug.
