Re: Is the documentation for Perl 5.20 'pack' correct?

Replies are listed 'Best First'.
Re^2: Is the documentation for Perl 5.20 'pack' correct? (l2r) by tye (Sage) on Jul 06, 2015 at 21:19 UTC
Depending on how you display "increasing address space", the values/ordering may appear the other way around. The OP was using strings and Perl strings (displayed in English) increase addresses to the right. So, yes, the quoted documentation disagrees with wikipedia. - tye	[reply]
Re^3: Is the documentation for Perl 5.20 'pack' correct? (l2r) by ikegami (Patriarch) on Jul 07, 2015 at 00:09 UTC
Wikipedia neither agrees nor disagrees with the OP's quote, since the part he quoted makes no sense out of context. `12345678` has no inherent endianness. Wikipedia neither agrees nor disagrees with the docs, as it is silent on the value output by `perl -V:byteorder`.	[reply] [d/l] [select]
Re^3: Is the documentation for Perl 5.20 'pack' correct? (r2l) by Anonymous Monk on Jul 06, 2015 at 21:26 UTC
'So, yes, the quoted documentation disagrees with wikipedia.' And what does that mean?	[reply]
Re^2: Is the documentation for Perl 5.20 'pack' correct? by flexvault (Monsignor) on Jul 06, 2015 at 23:52 UTC
Hello Corion, ...you'll have to tell us what the byte order on disk was :-) Displaying the disk file in hex, the packed number 16909060 is: `my $packed_number = pack( "N", 16909060 );` [download] displayed as hex '01020304' :-) Further, you can just do the following: `my $packed_number = pack( "N", 16909060 ); print unpack("H8",$packed_number),"\n";` [download] which yields hex '01020304'. Regards...Ed "Well done is better than well said." - Benjamin Franklin	[reply] [d/l] [select]