When a file format stores data in little-endian order, they should say that in the spec....

[notfred]

"16 bit unsigned" is not a good enough description of a value when someone thinks that it's going to be in big-endian order. They should tell you that so you don't spend hours wondering why it's not decoding right... :|

 

[notfred]

and you claim to be computer geeks....

 

[Zebo]

High order low order big small....?

 

[RSMemphis]

Have not ever looked at a file in my life in big endian. Most personal computer type thingies use little endian. Learnt that on my Amiga 500 already. 🙂

Kids today don't hack games anymore... 😉

 

[notfred]

Originally posted by: RSMemphis
Have not ever looked at a file in my life in big endian. Most personal computer type thingies use little endian. Learnt that on my Amiga 500 already. 🙂

Kids today don't hack games anymore... 😉

Network byte order is big endian....

 

[ProviaFan]

I read my first introduction to big / little endian stuff in an SGI / IRIX thread around here somewhere.

<-- needs to go read a tutorial so he'll know what you're talking about. 😱

 

[RSMemphis]

Originally posted by: notfred

Originally posted by: RSMemphis
Have not ever looked at a file in my life in big endian. Most personal computer type thingies use little endian.

Network byte order is big endian....

Yes, it is, but I don't do network programming. Not yet anyway.

 

[Shockwave]

So, how bout some links so us less uber types can follow along?
Pwease?

 

[Descartes]

It seems quite obvious that they left the endianess to the implementing platform. As you can't deterministically discern endianess in code (ok, you can, but shouldn't), one should know which order their platform uses (x86 vs. sparc, etc.).

I don't know of any non-programmer geeks know the difference between big/little endian, host/network byte order, signed/unsigned, one's/two's compliment, ad nauseum. You need to get over this "I know this, so everyone else should too!" hubris.