https://bugs.exim.org/show_bug.cgi?id=2120
--- Comment #14 from Philip Hazel <ph10@???> ---
>From many years of experience, I've learned that it's better to start off
strict rather than permissive. It bites you less and you can always relax
later. However, in the case of \o, Perl itself is strict, and PCRE does try not
to deviate from Perl's behaviour, at least not by default. (Perl itself has got
stricter over the years.)
When I get some time I will add an extra options field to the compile context,
which can do no harm. Then it will be straightforward to add options for
various special things such as \o (or more generally, backslash followed by
something not defined) and allowing \xdf00 etc in UTF-8 and UTF-32.
Zoltan's suggestion of a converter for JS is another possibility.
--
You are receiving this mail because:
You are on the CC list for the bug.
