From: Rafael Garcia-Suarez Date: Thu, 29 Jun 2006 16:12:05 +0000 (+0000) Subject: Typo fix. X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=8933a7400a697205027e8ea8cd44a40f2da3d4ed;p=p5sagit%2Fp5-mst-13.2.git Typo fix. p4raw-id: //depot/perl@28451 --- diff --git a/pod/perlre.pod b/pod/perlre.pod index c6dd30f..78ac358 100644 --- a/pod/perlre.pod +++ b/pod/perlre.pod @@ -70,13 +70,13 @@ your regular expression into (slightly) more readable parts. The C<#> character is also treated as a metacharacter introducing a comment, just as in ordinary Perl code. This also means that if you want real whitespace or C<#> characters in the pattern (outside a character -class, where they are unaffected by C), that you'll either have to -escape them (using blackslashes or C<\Q \E>) or encode them using octal -or hex escapes. Taken together, these features go a long way towards -making Perl's regular expressions more readable. Note that you have to -be careful not to include the pattern delimiter in the comment--perl has -no way of knowing you did not intend to close the pattern early. See -the C-comment deletion code in L. Also note that anything inside +class, where they are unaffected by C), that you'll either have to +escape them (using backslashes or C<\Q \E>) or encode them using octal +or hex escapes. Taken together, these features go a long way towards +making Perl's regular expressions more readable. Note that you have to +be careful not to include the pattern delimiter in the comment--perl has +no way of knowing you did not intend to close the pattern early. See +the C-comment deletion code in L. Also note that anything inside a C<\Q...\E> stays unaffected by C. X