Hello, I was just using "od" on a Linux/Intel
box with this command:
in.timed | od -l
It occurs to me that the output of in.timed
might be in "network byte order" or "big-endian",
and since the Intel machine is "little-endian",
the output is less than useful.
As far as I know, "od" will interpret byte
order in the byte order of the machine it
was compiled for. This makes the results
platform dependent.
I think "od" could use some options with
handling different byte order on input.
Thanks much,
Stan Tazuma
P.S. If there's nobody available to work
on adding this feature, I could take a
stab at it (if you think it's worth adding).
