From: Rafael Garcia-Suarez Date: Sat, 12 Dec 2009 14:57:28 +0000 (+0100) Subject: Doc nits X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e1e0053fcf33943fcf1a07bba02f04e4a0fdd3ad;p=p5sagit%2Fp5-mst-13.2.git Doc nits --- diff --git a/lib/legacy.pm b/lib/legacy.pm index 67f287f..eaab5d5 100755 --- a/lib/legacy.pm +++ b/lib/legacy.pm @@ -50,8 +50,6 @@ The one current possibility is: =head3 unicode8bit -THIS IS SUBJECT TO CHANGE - Use legacy semantics for the 128 characters on ASCII systems that have the 8th bit set. (See L below for EBCDIC systems.) Unless C> is specified, or the scalar containing such a character is @@ -62,7 +60,7 @@ anything. This behavior stems from when Perl did not support Unicode, and ASCII was the only known character set outside of C>. In order to not -possibly break pre_Unicode programs, these characters have retained their old +possibly break pre-Unicode programs, these characters have retained their old non-meanings, except when it is clear to Perl that Unicode is what is meant, for example by calling utf8::upgrade() on a scalar, or if the scalar also contains characters that are only available in Unicode. Then these 128 @@ -80,7 +78,8 @@ The behavior is known to have effects on these areas: =item * Changing the case of a scalar, that is, using C, C, C, -and C, or C<\L>, C<\U>, C<\u> and C<\l> in regular expression substitutions. +and C, or C<\L>, C<\U>, C<\u> and C<\l> in regular expression +substitutions. =item * @@ -131,7 +130,7 @@ a colon, to distinguish it from an individual legacy behavior. Specifying sub-versions such as the C<0> in C<5.10.0> in legacy bundles has no effect: legacy bundles are guaranteed to be the same for all sub-versions. -Legacy bundles are not allowed with C +Legacy bundles are not allowed with C. =cut