From eb88ed9ea9974ecc4cbfd0b64a636b00870389a1 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sat, 26 Mar 2011 09:45:38 -0600 Subject: [PATCH] perlunicode: mention quotemeta utf8 inconsistency --- pod/perlunicode.pod | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index 03277da..c0a2ca4 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -1616,6 +1616,12 @@ I C<[[:ascii:]]>. =item * +In C 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 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 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 for details on how this pragma works in -- 1.8.3.1