From: Karl Williamson Date: Tue, 26 Nov 2013 02:14:46 +0000 (-0700) Subject: perlrecharclass: Add statement about above-Unicode and (?[]) X-Git-Tag: upstream/5.20.0~1120 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=f194034a5909067468cef63a1935bb519f3d0c69;p=platform%2Fupstream%2Fperl.git perlrecharclass: Add statement about above-Unicode and (?[]) The extended bracketed character class does not raise warnings when non-Unicode code points are matched against it. --- diff --git a/pod/perlrecharclass.pod b/pod/perlrecharclass.pod index 0a168a0..a8ee854 100644 --- a/pod/perlrecharclass.pod +++ b/pod/perlrecharclass.pod @@ -972,6 +972,11 @@ You have to have two hex digits after a braceless C<\x> (use a leading zero to make two). These restrictions are to lower the incidence of typos causing the class to not match what you thought it would. +If a regular bracketed character class contains a C<\p{}> or C<\P{}> and +is matched against a non-Unicode code point, a warning may be +raised, as the result is not Unicode-defined. No such warning will come +when using this extended form. + The final difference between regular bracketed character classes and these, is that it is not possible to get these to match a multi-character fold. Thus,