diff options
author | Vadim Konovalov <vkonovalov@lucent.com> | 1999-09-20 13:43:49 +0400 |
---|---|---|
committer | Jarkko Hietaniemi <jhi@iki.fi> | 1999-09-20 07:33:32 +0000 |
commit | 140cb37ed79835bf0c0cde1ebe5ce5eceaa7b04b (patch) | |
tree | 9bc04faca04c8aea9360ab1d54ec932aa2dde580 | |
parent | 30adffae6205ce03b6a039dea7bf52af0341657f (diff) | |
download | perl-140cb37ed79835bf0c0cde1ebe5ce5eceaa7b04b.tar.gz |
Fix a bug in the description of endianness. Reported in
From: "Konovalov, Vadim" <vkonovalov@lucent.com>
To: perl5-porters@perl.org
Subject: BUG: perldoc -f pack
Message-ID: <402099F49BEED211999700805FC7359F20D3F5@ru0028exch01.spb.lucent.com>
p4raw-id: //depot/cfgperl@4202
-rw-r--r-- | pod/perlfunc.pod | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 995a671110..9968ee76f4 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -2869,7 +2869,7 @@ not support long longs.) The integer formats C<"s">, C<"S">, C<"i">, C<"I">, C<"l">, and C<"L"> are inherently non-portable between processors and operating systems because they obey the native byteorder and endianness. For example a -4-byte integer 0x87654321 (2271560481 decimal) be ordered natively +4-byte integer 0x12345678 (305419896 decimal) be ordered natively (arranged in and handled by the CPU registers) into bytes as 0x12 0x34 0x56 0x78 # little-endian @@ -2885,7 +2885,7 @@ the classic "Gulliver's Travels" (via the paper "On Holy Wars and a Plea for Peace" by Danny Cohen, USC/ISI IEN 137, April 1, 1980) and the egg-eating habits of the Lilliputians. -Some systems may even have weird byte orders such as +Some systems may have even weirder byte orders such as 0x56 0x78 0x12 0x34 0x34 0x12 0x78 0x56 |