https://bugs.exim.org/show_bug.cgi?id=1879
Philip Hazel <p...@hermes.cam.ac.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #2 from Philip Hazel <p...@hermes.cam.ac.uk> ---
I have investigated further. In PCRE2, both \A and \C give an error if
encountered anywhere in a character class. Perl gives an warning if running in
warning mode, then treats them as literals. PCRE has no facility for warning,
so I think it is right to give an error.
In PCRE1 (8.39) when [\A-\C] is processed, \A is treated as a literal, but \C
throws an error as an invalid end of range. I think it has been like this for a
very long time. \A does cause an error if PCRE_EXTRA is set (which is a bit
like Perl's warning mode). For PCRE2 I decided to turn on the extra checking
always.
At this stage in the life of PCRE1 I do not think it is worth doing anything,
so I am closing this bug.
--
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
