In perl.git, the branch blead has been updated
<http://perl5.git.perl.org/perl.git/commitdiff/bc7bbd314b9de6da4e0b8bf6a3c1ced7645acc76?hp=b6e9e118a4133eb96eb5e5de209ea6a37fd15bfe>
- Log -----------------------------------------------------------------
commit bc7bbd314b9de6da4e0b8bf6a3c1ced7645acc76
Author: Father Chrysostomos <spr...@cpan.org>
Date: Fri Aug 19 22:10:57 2016 -0700
perldelta for #128951 / bf8a9a15
M pod/perldelta.pod
commit 24c3455551f279028661b19077eb6c0e12df2fbe
Author: Father Chrysostomos <spr...@cpan.org>
Date: Fri Aug 19 22:08:14 2016 -0700
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.
M pod/perldelta.pod
-----------------------------------------------------------------------
Summary of changes:
pod/perldelta.pod | 13 +++++++++++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/pod/perldelta.pod b/pod/perldelta.pod
index c182040..3f01895 100644
--- a/pod/perldelta.pod
+++ b/pod/perldelta.pod
@@ -424,11 +424,20 @@ 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]
+=item *
+
+C<@{x> followed by a newline where C<x> represents a control or non-ASCII
+character no longer produces a garbled syntax error message or a crash.
+[perl #128951]
+
=back
=head1 Known Problems
--
Perl5 Master Repository
