diff options
| author | Marcus Holland-Moritz <mhx-perl@gmx.net> | 2004-04-21 23:09:20 +0200 |
|---|---|---|
| committer | Marcus Holland-Moritz <mhx-perl@gmx.net> | 2004-04-23 04:07:25 +0000 |
| commit | 1109a39207d99bf49cb02471368620d4a38731b2 (patch) | |
| tree | 55260221293693f4dedbdaebfdb9903e684f0ce2 /pod/perlport.pod | |
| parent | 766b36a4cf5981b911f14f15b05838d0b85a3b73 (diff) | |
| download | perl-1109a39207d99bf49cb02471368620d4a38731b2.tar.gz | |
byte-order modifiers for (un)pack templates
Message-Id: <20040421210920.3c467772@r2d2>
p4raw-id: //depot/perl@22734
Diffstat (limited to 'pod/perlport.pod')
| -rw-r--r-- | pod/perlport.pod | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/pod/perlport.pod b/pod/perlport.pod index f78e0191c8..8b8062ce2b 100644 --- a/pod/perlport.pod +++ b/pod/perlport.pod @@ -224,6 +224,10 @@ them in big-endian mode. To avoid this problem in network (socket) connections use the C<pack> and C<unpack> formats C<n> and C<N>, the "network" orders. These are guaranteed to be portable. +As of perl 5.8.5, you can also use the C<E<gt>> and C<E<lt>> modifiers +to force big- or little-endian byte-order. This is useful if you want +to store signed integers or 64-bit integers, for example. + You can explore the endianness of your platform by unpacking a data structure packed in native format such as: |