X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=pod%2Fperlunicode.pod;h=c5ffbaf0e49b0fadf44253ee0603c95cd4b60963;hb=35f2feb095c3dd2b77eb6efc2bf725b5886b6931;hp=bebf7aadec19d55cf3385ef725a9cca28b19030f;hpb=3969a89698ec7136fcf0eb1062fdf63f0e7726f4;p=p5sagit%2Fp5-mst-13.2.git diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index bebf7aa..c5ffbaf 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -31,12 +31,13 @@ or from literals and constants in the source text. Later, in L, we'll see how such inputs may be marked as being Unicode character data sources. -If the C<$^U> global flag is set to C<1>, all system calls will use the +If the C<-C> command line switch is used, (or the ${^WIDE_SYSTEM_CALLS} +global flag is set to C<1>), all system calls will use the corresponding wide character APIs. This is currently only implemented -on Windows. [XXX: Should there be a -C switch to enable $^U?] +on Windows. -Regardless of the above, the C pragma can always be used to force -byte semantics in a particular lexical scope. See L. +Regardless of the above, the C pragma can always be used to force +byte semantics in a particular lexical scope. See L. The C pragma is primarily a compatibility device that enables recognition of UTF-8 in literals encountered by the parser. It is also @@ -52,7 +53,7 @@ the input data came from a Unicode source (for example, by adding a character encoding discipline to the filehandle whence it came, or a literal UTF-8 string constant in the program), character semantics apply; otherwise, byte semantics are in effect. To force byte semantics -on Unicode data, the C pragma should be used. +on Unicode data, the C pragma should be used. Under character semantics, many operations that formerly operated on bytes change to operating on characters. For ASCII data this makes @@ -226,6 +227,6 @@ tend to run slower. Avoidance of locales is strongly encouraged. =head1 SEE ALSO -L, L, L +L, L, L =cut