summaryrefslogtreecommitdiff
path: root/lib/bytes.pm
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2001-11-10 06:10:39 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2001-11-10 06:10:39 +0000
commitc26c758be9c6b4b88aa5d07ac4631a815b5f2e2f (patch)
treec5f0fc4e3007c21d8bf9d6cd2f49b5d596813d9a /lib/bytes.pm
parentbed0e7afac8dadff911b9166e22e8a2c5a85182f (diff)
downloadperl-c26c758be9c6b4b88aa5d07ac4631a815b5f2e2f.tar.gz
Doc update.
p4raw-id: //depot/perl@12928
Diffstat (limited to 'lib/bytes.pm')
-rw-r--r--lib/bytes.pm5
1 files changed, 1 insertions, 4 deletions
diff --git a/lib/bytes.pm b/lib/bytes.pm
index 3b0268e644..cd82abc75b 100644
--- a/lib/bytes.pm
+++ b/lib/bytes.pm
@@ -33,9 +33,6 @@ bytes - Perl pragma to force byte semantics rather than character semantics
=head1 DESCRIPTION
-WARNING: The implementation of Unicode support in Perl is incomplete.
-See L<perlunicode> for the exact details.
-
The C<use bytes> pragma disables character semantics for the rest of the
lexical scope in which it appears. C<no bytes> can be used to reverse
the effect of C<use bytes> within the current lexical scope.
@@ -47,7 +44,7 @@ effect, the encoding is temporarily ignored, and each string is treated
as a series of bytes.
As an example, when Perl sees C<$x = chr(400)>, it encodes the character
-in UTF8 and stores it in $x. Then it is marked as character data, so,
+in UTF-8 and stores it in $x. Then it is marked as character data, so,
for instance, C<length $x> returns C<1>. However, in the scope of the
C<bytes> pragma, $x is treated as a series of bytes - the bytes that make
up the UTF8 encoding - and C<length $x> returns C<2>: