Byte-order and packing numbers into strings

[larryk]

The Situation
I need to format an integer into an 8-byte hexadecimal string as follows: if hex representation is (st uv wx yz) the formatted string must be (yz wx uv st st uv wx yz).

e.g. 305419896 in hex is (12345678) so formatted string should be (78 56 34 12 12 34 56 78)

The Question
although this works I have a nagging suspicion that this isn't The Best Way (tm) - is there some way to incorporate the reversing (little/big endian or something) into the pack/sprintf somehow - pack is still mysterious to me!

The Code

#!perl
use strict;
use warnings;

sub both_byte_orders_32 {
    my $data = shift;
    $data = pack 'H*', sprintf '%08x', $data;
    return reverse($data).$data
}

print both_byte_orders_32(305419896);

Any help much appreciated,

   larryk                                          
perl -le "s,,reverse killer,e,y,rifle,lycra,,print"

[demerphq]

This seems to work. At least it produces the same as your code...

sub bbo_32 {pack'VN',$_[0],$_[0]}

update:
When I first started out with perl I found that pack and unpack were menacing frightful things that I was never willing to spend time to grok. However it turns out that they are a lot easier than they look, just take the time to mess around with em. Very useful in a lot of places and ways. Which is not to say that I know them that well. I still use perlfunc pretty much every time I need to use either.

Yves / DeMerphq
--
When to use Prototypes?

[tadman]

To further golf this, you could do the following:

sub bbo_32 {pack'VN',@_[0,0]}


Which is a low-tech add on to an elegant solution by demerphq.

Update: demerphq points out $_[0,0] to the correct @_[0,0]. Cut and paste error.

[demerphq]

Nice! ++ for sure! (Well, overlooking that it should be @_[0,0] ;-)

Similar in length is also

sub bbo_32{pack'VN',(pop)x2}

Yves / DeMerphq
--
When to use Prototypes?

[theorbtwo]

Just wondering: what do you need this for? I know numbers like this are used internaly in some peices of ISO-9660 (and iso9660-like, like playstation) filesystems, but why do you need to print out human-readable hex in this format? Or am I smoking crack?

(I'm interested in what you're doing even if I am smoking crack. I recently tried to divine the ps1 diskformat by example (for no good reason, since I was looking for PS2 data, and it uses a different (DVD-based) disk format), but ended up using C instead, since that way I could steal more easily from the Linux iso9660 code.

TACCTGTTTGAGTGTAACAATCATTCGCTCGGTGTATCCATCTTTG ACACAATGAATCTTTGACTCGAACAATCGTTCGGTCGCTCCGACGC