X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2Fbytes.pm;h=cd82abc75b5b360d2b13c77dee26444dd41394c6;hb=5ec554fbe2d22a7213ac94890d84ed925ba9af4b;hp=f93d6158d9fc6f177eac2335a9948ba076df7a54;hpb=21bad92165270edd85ff697c883b65506d5af626;p=p5sagit%2Fp5-mst-13.2.git diff --git a/lib/bytes.pm b/lib/bytes.pm index f93d615..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,18 +33,32 @@ 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 for the exact details. - The C pragma disables character semantics for the rest of the lexical scope in which it appears. C can be used to reverse the effect of C within the current lexical scope. -Perl normally assumes character semantics in the presence of -character data (i.e. data that has come from a source that has -been marked as being of a particular character encoding). - -To understand the implications and differences between character +Perl normally assumes character semantics in the presence of character +data (i.e. data that has come from a source that has been marked as +being of a particular character encoding). When C is in +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 UTF-8 and stores it in $x. Then it is marked as character data, so, +for instance, C returns C<1>. However, in the scope of the +C pragma, $x is treated as a series of bytes - the bytes that make +up the UTF8 encoding - and C returns C<2>: + + $x = chr(400); + print "Length is ", length $x, "\n"; # "Length is 1" + printf "Contents are %vd\n", $x; # "Contents are 400" + { + use bytes; + print "Length is ", length $x, "\n"; # "Length is 2" + printf "Contents are %vd\n", $x; # "Contents are 198.144" + } + +For more on the implications and differences between character semantics and byte semantics, see L. =head1 SEE ALSO