>>0xa1234567: 00 00 00 01  10
>>
>>vs (mine)
>>
>>0xa1234567: 00000001 10
>>
>>I can make the other code space the same way without too much effort but
>>otherwise it looks ok.
>
>i slightly prefer the former, but that's neither here nor there.  the
>only thing that ever irks me about hexdumps like this is the
>implication that the 00000001 (from yours) may or may not be in local
>byte order or network byte order.  for, eg, sparcs it makes no
>difference.  for intel it does.  im(ns)ho, it should *always* be in
>network byte order since that's the ordering my brain uses.

I used network byte order and did all my testing on x86 to make sure
it works correctly. (mach does the same thing).

James