In perl.git, the branch blead has been updated

<https://perl5.git.perl.org/perl.git/commitdiff/4c821bdad549847bbb50929bc86cc3baa3676829?hp=6ee81574cd3682da001e8c3e7a931f034c4c31b9>

- Log -----------------------------------------------------------------
commit 4c821bdad549847bbb50929bc86cc3baa3676829
Author: Karl Williamson <k...@cpan.org>
Date:   Fri Jun 29 08:29:24 2018 -0600

    perldeprecation: Clean up text about grapheme delims
    
    This changes the text to make more sense in light of the fact that the
    the deprecation has changed to illegality.

-----------------------------------------------------------------------

Summary of changes:
 pod/perldeprecation.pod | 34 +++++++++++++++-------------------
 1 file changed, 15 insertions(+), 19 deletions(-)

diff --git a/pod/perldeprecation.pod b/pod/perldeprecation.pod
index 5b4f406894..a41f2c6a35 100644
--- a/pod/perldeprecation.pod
+++ b/pod/perldeprecation.pod
@@ -230,25 +230,21 @@ A grapheme is what appears to a native-speaker of a 
language to be a
 character.  In Unicode (and hence Perl) a grapheme may actually be
 several adjacent characters that together form a complete grapheme.  For
 example, there can be a base character, like "R" and an accent, like a
-circumflex "^", that appear when displayed to be a single character with
-the circumflex hovering over the "R".  Perl currently allows things like
-that circumflex to be delimiters of strings, patterns, I<etc>.  When
-displayed, the circumflex would look like it belongs to the character
-just to the left of it.  In order to move the language to be able to
-accept graphemes as delimiters, we have to deprecate the use of
-delimiters which aren't graphemes by themselves.  Also, a delimiter must
-already be assigned (or known to be never going to be assigned) to try
-to future-proof code, for otherwise code that works today would fail to
-compile if the currently unassigned delimiter ends up being something
-that isn't a stand-alone grapheme.  Because Unicode is never going to
-assign
-L<non-character code points|perlunicode/Noncharacter code points>, nor
-L<code points that are above the legal Unicode maximum|
-perlunicode/Beyond Unicode code points>, those can be delimiters, and
-their use won't raise this warning.
-
-As of Perl 5.30, delimiters which are unassigned code points, or which
-are non-standalone graphemes are fatal.
+circumflex "^", that appear to be a single character when displayed,
+with the circumflex hovering over the "R".
+
+As of Perl 5.30, use of delimiters which are non-standalone graphemes is
+fatal, in order to move the language to be able to accept
+multi-character graphemes as delimiters.
+
+Also, as of Perl 5.30, delimiters which which are unassigned code points
+but that may someday become assigned are prohibited.  Otherwise, code
+that works today would fail to compile if the currently unassigned
+delimiter ends up being something that isn't a stand-alone grapheme.
+Because Unicode is never going to assign L<non-character code
+points|perlunicode/Noncharacter code points>, nor L<code points that are
+above the legal Unicode maximum| perlunicode/Beyond Unicode code
+points>, those can be delimiters.
 
 =head3 In XS code, use of various macros dealing with UTF-8.
 

-- 
Perl5 Master Repository

Reply via email to