4 Jun
2010
4 Jun
'10
12:11 p.m.
On 4 June 2010 08:04, vicente.botet <vicente.botet@wanadoo.fr> wrote:
I was wondering if instead of defining a separated class we can not define endianness::native depending on the ENDIAN of the host and remove the explicit definition.
I would have expected that the other way around would be better. The native endian would be implemented with memcpy, the big and little portably, and as an optimization big or little would be = native, based on the defines.