https://bugs.exim.org/show_bug.cgi?id=2120
--- Comment #18 from Philip Hazel <ph10@???> ---
I have just committed a documented patch that implements additional options
within the compile context, the first of which is
PCRE2_EXTRA_ALLOW_SURROGATE_ESCAPES. This is available in UTF-8 and UTF-32
modes.
I see your point, and indeed I did play with turning all escape errors into
literals, but I can't bring myself to implement a feature whereby a simple typo
such as missing a } or typing something like \o{182} instead of \o{172} causes
no error, but goes on to behave completely differently to what the user might
have been expecting.
Is there a definitive JavaScript regex document anywhere? Perhaps I should read
it and see whether I can think of some compromise here.
--
You are receiving this mail because:
You are on the CC list for the bug.
