pb-207 / aemconvertor Goto Github PK

struct operations can be given a byte order - it'd be really nice if we could specify this explicitly

this is mostly just for clarity, but it's also because by default, struct will use the byte order of your CPU. We shouldn't run into any issues with this given the userbase.

By default, C types are represented in the machine’s native format and byte order, and properly aligned by skipping pad bytes if necessary (according to the rules used by the C compiler). This behavior is chosen so that the bytes of a packed struct correspond exactly to the memory layout of the corresponding C struct. Whether to use native byte ordering and padding or standard formats depends on the application.

Native byte order is big-endian or little-endian, depending on the host system. For example, Intel x86, AMD64 (x86-64), and Apple M1 are little-endian; IBM z and many legacy architectures are big-endian

https://docs.python.org/3/library/struct.html