summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2016-08-19 22:08:14 -0700
committerFather Chrysostomos <sprout@cpan.org>2016-08-19 22:08:16 -0700
commit24c3455551f279028661b19077eb6c0e12df2fbe (patch)
tree44400dbf239a4053651fea2fc80740f85c529cfd
parentb6e9e118a4133eb96eb5e5de209ea6a37fd15bfe (diff)
downloadperl-24c3455551f279028661b19077eb6c0e12df2fbe.tar.gz
Correct a perldelta entry
The termcode variable in scan_const, which was an I32 and susceptible to truncation, is not used to find the closing delimiter, but only to check for special uses of delimiters such as in qr'...' and m?...? and ‘<’ which is used internally as the ‘closing delimiter’ for here-docs, it being one that can never occur for other pyoq operators. Hence, such strings already worked before, but now they work consis- tently; \x{100000027} no longer suppresses regexep interpolation, for instance.
-rw-r--r--pod/perldelta.pod7
1 files changed, 5 insertions, 2 deletions
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index c182040945..22b066fc32 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -424,8 +424,11 @@ fixed. [perl #128686].
=item *
-Use of a string delimiter whose code point is above 2**32 is now
-supported on platforms that allow this. Note that this is non-portable,
+Use of a string delimiter whose code point is above 2**31 now works
+correctly on platforms that allow this. Previously, certain characters,
+due to truncation, would be confused with other delimiter characters
+with special meaning (such as C<?> in C<m?...?>), resulting
+in inconsistent behaviour. Note that this is non-portable,
and is based on Perl's extension to UTF-8, and is probably not
displayable nor enterable by any editor. [perl #128738]