Answering last 2 emails:
> I believe that most of the problems with PCRE 7.0 are related to possible
> empty sub patterns, which had a fix comitted a week ago:
> http://www.exim.org/mail-archives/pcre-dev/2007-June/msg00000.html
>
> In this case I'm sure it's a problem with the eempty subpattern marking.
> The pattern /(['"])((.*(\\\1)*)*)\1/ have the group ((.*(\\\1)*)*) in PCRE
> 7.0 and 7.1 will think that (.*(\\\1)*) must be non empty because (\\\1)
> is non-emty, and it misses the fact that it's a possible zero repeat.
>
> /Viktor
Thanks for bringing this up. I didn't remember that message.
So, the option now is to upgrade to PCRE 7.2 (I don't think it worth
backporting the patch). Philip: how confident are you with this new version?
Is it safe to upgrade already to PCRE 7.2 RC2?
> I am hoping to get 7.2 out within the next week or two. There are just a
> couple more Perl 5.10 features that I want to get implemented, and one
> outstanding other issue in the C++ wrapper that I have just sent to the
> folks at Google.
> Philip
That means that there are no unfixed known bugs and the only changes will be
new features? If yes, I think I can bundle the RC2 quickly (there's always
the stigma attached with non-release versions, but I think I can handle
that..).
Thanks,
Nuno
