Subject: Re: [boost] The file boost/detail/endian.hpp needs to be set up for your CPU type
From: Adrian_H (adrianh.bsc_at_[hidden])
Date: 2013-05-08 02:38:49
Even if templates or optimizers are not capable of stating this. The
COMPILERS should have something EMBEDDED to state this. It is, after all,
generating the code. And there are constants that are lying about in memory
too that it has to create. So logically, it knows what endianness of the
target binary is going to be, even if it doesn't know what it is outside the
data segment that the constants are stored in. I only know a little about
multi-endian architectures, but IIRC, they have a way to automagicaly
transfer data from different endian segments correctly.
Still, with cloud computing and other interoperable computing models,
COMPILERS need to take responsibility to make it possible for programmers to
make sane code without such clumsy methods as an endian.h header file.
-- View this message in context: http://boost.2283326.n4.nabble.com/boost-The-file-boost-detail-endian-hpp-needs-to-be-set-up-for-your-CPU-type-tp4646941p4646953.html Sent from the Boost - Dev mailing list archive at Nabble.com.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk