X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2Fbytes.pm;h=cd82abc75b5b360d2b13c77dee26444dd41394c6;hb=492652be590915fcb2621eeceaf000a1c070956a;hp=f2f7e0157cb8a92ec97e4dab2e248dc23af56781;hpb=22d4bb9ccb8701e68f9243547d7e3a3c55f70908;p=p5sagit%2Fp5-mst-13.2.git

diff --git a/lib/bytes.pm b/lib/bytes.pm
index f2f7e01..cd82abc 100644
--- a/lib/bytes.pm
+++ b/lib/bytes.pm
@@ -1,5 +1,7 @@
 package bytes;
 
+our $VERSION = '1.00';
+
 $bytes::hint_bits = 0x00000008;
 
 sub import {
@@ -31,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.
@@ -45,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>: