summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2007-11-26 06:55:03 +0200
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2007-11-26 09:17:42 +0000
commit10fdd3268bfedb0d10912f2f0ba6be13995de3fe (patch)
tree6adad448f2089e0e385bd7f9b5ead1ba60b3f11d /pod
parentc73b03b73a2e88e21ae9d9009a9d1c9cbadf2d15 (diff)
downloadperl-10fdd3268bfedb0d10912f2f0ba6be13995de3fe.tar.gz
pod/perlrebackslash.pod: small Unicode additions
Message-Id: <200711260255.lAQ2t37n188664@kosh.hut.fi> p4raw-id: //depot/perl@32493
Diffstat (limited to 'pod')
-rw-r--r--pod/perlrebackslash.pod9
1 files changed, 8 insertions, 1 deletions
diff --git a/pod/perlrebackslash.pod b/pod/perlrebackslash.pod
index d8cfb6ade2..ac95ace136 100644
--- a/pod/perlrebackslash.pod
+++ b/pod/perlrebackslash.pod
@@ -500,7 +500,9 @@ C<< (?>\x0D\x0A)|\v) >>. Since C<\R> can match a more than one character,
it cannot be put inside a bracketed character class; C</[\R]/> is an error.
C<\R> is introduced in perl 5.10.
-Mnemonic: none really. C<\R> was picked because PCRE already uses C<\R>.
+Mnemonic: none really. C<\R> was picked because PCRE already uses C<\R>,
+and more importantly because Unicode recommends such a regular expression
+metacharacter, and suggests C<\R> as the notation.
=item \X
@@ -512,6 +514,11 @@ mark character followed by zero or more mark characters. Mark characters
include (but are not restricted to) I<combining characters> and
I<vowel signs>.
+C<\X> matches quite well what normal (non-Unicode-programmer) usage
+would consider a single character: for example a base character
+(the C<\PM> above), for example a letter, followed by zero or more
+diacritics, which are I<combining characters> (the C<\pM*> above).
+
Mnemonic: eI<X>tended Unicode character.
=back