>| 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.
>
>Umm, no. We should not choose which ordering simply to be compatible
>with _your_ brain ;-)

well, just look what's telling you that: your brain.  my brain is
different.

>More seriously, though, I think this is terribly wrong. The same ordering
>as od -b uses would seem best.

od -b displays a single byte output format in the natural order of the
bytes.  the format was talking about gave the impression that it might
be printing stuff out in a multi-byte format.  hexdump -C is my
current favorite, right behind sunos' od that prints stuff in -tx1
format.  i have a patch for this but it's too large to fit into this
margin.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."