-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
t/perl/regexp.t fails with PCRE2 10.32-RC1 #31
Comments
I confirm that the failures are triggered with these new features introduced with PCRE2 commits:
and
|
Thanks, confirmed |
See [GH #31], thank to Petr Pisar. Need to check how to map these 2 new features: Allow :NAME on (*ACCEPT), (*FAIL), and (*COMMIT) and fix bug with (*MARK) followed by (*ACCEPT) in an assertion. Add support for \N{U+dd...}, for ASCII and Unicode modes only.
I've filed 2 PCRE2 bugs: https://bugs.exim.org/show_bug.cgi?id=2306 |
See [GH #31], thank to Petr Pisar. Need to check how to map these 2 new features: Allow :NAME on (*ACCEPT), (*FAIL), and (*COMMIT) and fix bug with (*MARK) followed by (*ACCEPT) in an assertion. Add support for \N{U+dd...}, for ASCII and Unicode modes only. Caused unicode regression https://bugs.exim.org/show_bug.cgi?id=2305 (need to observe unicode folding rules for \N{U+NNNN} chars)
Added the specializations to the testcases, where pcre2 deviates from perl5 for the upcoming 0.15 release fixup for libpcre2 >= 10.32 unicode semantic changes:
|
PCRE2 has a release candidate for 10.32 and these t/perl/regexp.t tests fail with it:
This may be caused by these new PCRE2 features:
The text was updated successfully, but these errors were encountered: