On 01.10.2012 17:08, Henrik Sperre Johansen wrote:
IMHO, it really is most optimal approach when platform endianness
changes are rare, and the penalty can easily be avoided by simply
saving the image on the platform it is intended to be used.
Cheers,
Henry
In other words; it's not really something you usually need to think
about unless you are developing closed applications shipping with a
fixed image.
Obviously, one such case is phone applications, John mentioned its
impact on iPhone apps here;
http://forum.world.st/Where-is-the-heap-tp2195336p2195639.html
Interestingly, (at least the way I read it) the real cost was memory
access, and endianness swap was really just one of multiple items that
fell under the category "Accesses the entire object memory at startup".
Cheers,
Henry
