On 6/8/05, Caleb Epstein <caleb.epstein@gmail.com> wrote:
On 6/8/05, Caleb Epstein <caleb.epstein@gmail.com> wrote:
I've commited fixes for these to CVS just now, but I'm *not* sure how to best address the BOOST_BIG_ENDIAN issue. Any suggestions there?
I think perhaps a new header file, <boost/endian.hpp> makes the most sense here.
I don't think the definition of BOOST_BIG_ENDIAN / BOOST_LITTLE_ENDIAN belong in <boost/detail/limits.hpp> This header is not included unless BOOST_NO_LIMITS is defined, which I assume is only for non-standards-conforming implementations.
Does anyone have an opinion on this? Should there be a <boost/endian.hpp> that defines e.g. BOOST_{BIG,LITTLE,PDP?}_ENDIAN? There are two failing tests in Boost.Serialization that need to know if we are on a BOOST_BIG_ENDIAN platform. -- Caleb Epstein caleb dot epstein at gmail dot com