From: Karl Williamson <public@khwilliamson.com>
Date: Thu, 19 Jan 2012 20:23:31 +0000 (-0700)
Subject: perldelta: For bb91448 and associated commits
X-Git-Tag: accepted/trunk/20130322.191538~1079
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1ac442bc1ab0d3c88fe1dab9ef331fa9e56fcf64;p=platform%2Fupstream%2Fperl.git

perldelta: For bb91448 and associated commits
---

diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index 36cc4fc..92aabaf 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -822,6 +822,27 @@ In 5.14.0, the bitwise assignment operators C<|=>, C<^=> and C<&=> starting
 leaving the left-hand side undefined if it happened to be a copy-on-write
 string.  This has been fixed [perl #108480].
 
+=item * Three problematic Unicode characters now work better in regex pattern matching under C</i>
+
+In the past, three Unicode characters:
+LATIN SMALL LETTER SHARP S,
+GREEK SMALL LETTER IOTA WITH DIALYTIKA AND TONOS,
+and
+GREEK SMALL LETTER UPSILON WITH DIALYTIKA AND TONOS,
+along with the sequences that they fold to
+(including "ss" in the case of LATIN SMALL LETTER SHARP S),
+did not properly match under C</i>.  5.14.0 fixed some of these cases,
+but introduced others, including a panic when one of the characters or
+sequences was used in the C<(?(DEFINE)> regular expression predicate.
+The known bugs that were introduced in 5.14 have now been fixed; as well
+as some other edge cases that have never worked until now.  All these
+involve using the characters and sequences outside bracketed character
+classes under C</i>.  There remain known problems when using certain
+characters with multi-character folds inside bracketed character
+classes, including such constructs as
+C<qr/[\N{LATIN SMALL LETTER SHARP}a-z]/i>.  These remaining bugs are
+addressed in [perl #89774].
+
 =back
 
 =head1 Acknowledgements