Huh. You know I had never considered why we have htobe32 and be32toh which do exactly the same thing. Maybe because of oddball architectures which are neither big nor little endian?
For instance... /usr/include/x86_64-linux-gnu/bits/endian.h has:
Apparently this is called 'middle-endian'... yikes!
On the other hand I sort of like having one function that's clearly used for importing values to the host's byte order, and another for exporting values from the host's byte order. But maybe that's just because I'm used to having them...
For instance... /usr/include/x86_64-linux-gnu/bits/endian.h has:
#define __LITTLE_ENDIAN 1234 #define __BIG_ENDIAN 4321 #define __PDP_ENDIAN 3412
Apparently this is called 'middle-endian'... yikes!
On the other hand I sort of like having one function that's clearly used for importing values to the host's byte order, and another for exporting values from the host's byte order. But maybe that's just because I'm used to having them...