remove $^U dependent behaviors in runtime; chr() and sprintf('%c',...)

now return bytes all the way to 255, they will be transparently
coerced (in future) to UTF-8 when they are used in operations
involving other UTF-8 strings; C<use utf8> doesn't set $^U anymore

p4raw-id: //depot/perl@5013

1 files changed, 3 insertions, 6 deletions

diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index 5a73d4e959..bebf7aadec 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -31,12 +31,9 @@ or from literals and constants in the source text.  Later, in
 L</Character encodings for input and output>, we'll see how such
 inputs may be marked as being Unicode character data sources.
 
-One particular condition will enable character semantics on the entire
-program, bypassing the compatibility mode: if the C<$^U> global flag is
-set to C<1>, nearly all operations will use character semantics by
-default.  As an added convenience, if the C<utf8> pragma is used in the
-C<main> package, C<$^U> is enabled automatically.  [XXX: Should there
-be a -C switch to enable $^U?]
+If the C<$^U> 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?]
 
 Regardless of the above, the C<byte> pragma can always be used to force
 byte semantics in a particular lexical scope.  See L<byte>.