Skip to content

Commit 76ec65d

Browse files
committed
Make examples compile
1 parent 51efd08 commit 76ec65d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/Type/Cool.pod6

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -708,7 +708,7 @@ number of characters in the string. Please note that on the JVM, you currently g
708708
codepoints instead of graphemes.
709709
710710
say 'møp'.chars; # OUTPUT: «3␤»
711-
say 'ã̷̠̬̊'.chars # OUTPUT: «1␤»
711+
say 'ã̷̠̬̊'.chars; # OUTPUT: «1␤»
712712
say '👨‍👩‍👧‍👦🏿'.chars; # OUTPUT: «1␤»
713713
714714
X<|Grapheme> X<|NFG>
@@ -726,8 +726,8 @@ there are many other cases when this may happen. Another example is C<\c[ZWJ]>
726726
You can check C<Grapheme_Cluster_Break> property of a character in
727727
order to see how it is going to behave:
728728
729-
say ‘ã̷̠̬̊’.uniprops(‘Grapheme_Cluster_Break’) # OUTPUT: «(Other Extend Extend Extend Extend)␤»
730-
say ‘👨‍👩‍👧‍👦🏿’.uniprops(‘Grapheme_Cluster_Break’) # OUTPUT: «(E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ E_Modifier)␤»
729+
say ‘ã̷̠̬̊’.uniprops(‘Grapheme_Cluster_Break’); # OUTPUT: «(Other Extend Extend Extend Extend)␤»
730+
say ‘👨‍👩‍👧‍👦🏿’.uniprops(‘Grapheme_Cluster_Break’); # OUTPUT: «(E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ ZWJ E_Base_GAZ E_Modifier)␤»
731731
732732
You can read more about graphemes in the
733733
L<Unicode Standard|http://unicode.org/reports/tr29/#Grapheme_Cluster_Boundaries>,

0 commit comments

Comments
 (0)