[ENet-discuss] enet endianess (byte order)
Oles
oles at 4a-games.com
Sat Apr 28 05:56:02 PDT 2012
Hi.
Documentation mentions that “ENet makes no assumptions about the underlying
platform's endianess or word size“.
Does it mean that I can send messages from big-endian CPU to little-endian
and vice-versa?
I mean, internal message data are correctly converted to little-endian on
the app side, but what to do with enet internal headers?
Or everything should work as expected?
If it doesn't work - could you suggest places to modify?
Thanks a lot,
Oles
More information about the ENet-discuss
mailing list