summaryrefslogtreecommitdiff
path: root/pod/perlunicode.pod
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2011-03-26 09:45:38 -0600
committerKarl Williamson <public@khwilliamson.com>2011-03-26 09:51:19 -0600
commiteb88ed9ea9974ecc4cbfd0b64a636b00870389a1 (patch)
tree1f6b6b8666f3d1a014168f549c159861e4ef3275 /pod/perlunicode.pod
parent79de270c1b916f7aef04579a0bbc6a7cf1db38b8 (diff)
downloadperl-eb88ed9ea9974ecc4cbfd0b64a636b00870389a1.tar.gz
perlunicode: mention quotemeta utf8 inconsistency
Diffstat (limited to 'pod/perlunicode.pod')
-rw-r--r--pod/perlunicode.pod11
1 files changed, 9 insertions, 2 deletions
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index 03277dac16..c0a2ca4370 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -1616,6 +1616,12 @@ I<except> C<[[:ascii:]]>.
=item *
+In C<quotemeta> or its inline equivalent C<\Q>, all characters whose
+code points are above 127 are not quoted in UTF-8 encoded strings, but
+all are quoted in UTF-8 strings.
+
+=item *
+
User-defined case change mappings. You can create a C<ToUpper()> function, for
example, which overrides Perl's built-in case mappings. The scalar must be
encoded in utf8 for your function to actually be invoked.
@@ -1651,8 +1657,9 @@ cause Perl to use Unicode semantics on all string operations within the
scope of the feature subpragma. Regular expressions compiled in its
scope retain that behavior even when executed or compiled into larger
regular expressions outside the scope. (The pragma does not, however,
-affect user-defined case changing operations. These still require a
-UTF-8 encoded string to operate.)
+affect the C<quotemeta> behavior. Not does it affect the deprecated
+user-defined case changing operations. These still require a UTF-8
+encoded string to operate.)
In Perl 5.12, the subpragma affected casing changes, but not regular
expressions. See L<perlfunc/lc> for details on how this pragma works in