Re: [pcre-dev] [Bug 1705] heap-buffer-overflow in match src…

On Thu, 5 Nov 2015, admin@??? wrote:

> It's a bit sad -- there's so much code using PCRE1 and UTF and can't be ported
> just yet to PCRE2. How is the problem of \C solved in PCRE2 anyhow?

PCRE2 has an option PCRE2_NEVER_BACKSLASH_C, which locks out the use of
\C. It also has --enable-never-backslash-C, which forces this option on
all patterns.

I know there's a lot of code that uses PCRE1, but I just don't have time
to backport new features. Sorry.

Philip

--
Philip Hazel