Gentlebeings, may I very-cautiously advance the notion that, by now, "anyone who seriously expects to encounter any 'present objections' to their 'present plans' fully expects to be able to access a GPS database of ... 'our gravestones!'

"Bah!" "Humbug!!" "These kids(!) today!"

- - -

Seriously... "Big-endian vs. Little-endian" actually never mattered, any more than the sequence of bits within a <byte|X-word> within a serial transmission sequence. As long as "all of you somehow agreed," the technical particulars of your actual technical agreement never actually mattered – or needed to matter – to anyone at all. "You wrote some source-code to encode it and to send it, and then I wrote corresponding source-code to receive it and decode it, and ... 'lo and behold!!'" (Problem. Solved. "Gasp!!")

Actually I think I came into some endianness problems today, I was doing a for() loop over a variable I was referring to as hexadecimal and adding 0x01 instead of 0x1. That seemed to be the problem, and I think it was due to endianness.

Did you mean 0x10 instead of 0x1? Usually endianness doesn't affect ordering within bytes, because you can't address individual bits.

No, but it seemed to add 0x10 instead of 0x01.

Actually, "endian-ness" can refer both to the ordering of bits within a byte (e.g. on a serial data-transmission stream), and/or to the ordering of those bytes. I have seen all four possible combinations in actual use.

1 members found this post helpful.