Re: [boost] License of endian and limits in Boost detail

-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Rene Rivera Sent: Tuesday, March 19, 2013 4:18 AM To: boost@lists.boost.org Subject: Re: [boost] License of endian and limits in Boost detail

On Mon, Mar 18, 2013 at 9:59 AM, Rene Rivera wrote:

...

On Mon, Mar 18, 2013 at 9:10 AM, Paul A. Bristow wrote:

...

John's proposal and then add to the proposed Predef library sounds a good way forward.

Actually I suspect that there is really only one way to do this task - whatever the actual macro variable names used in the code.

Probably.. FYI.. I worked up an initial implementation in the Predef library over the weekend from the information I could find on-line. Which I suspect is less than what the current endian header has. I'll check it in tonight and ask for feedback as to what's missing and style.

First pass at the Predef header for this at < https://raw.github.com/grafikrobot/boost-predef/master/include/boost/predef/endian.h>. Currently only tested on my OSX laptop. Would appreciate others trying it out. The info is a combination of the indispensable description from predef.sf.net (Bjorn Reese et al), known endian specifications I could find on the architectures I currently detect, and a small amount of general web searching.

Looks a good start. Typo in /* GNU libc provides a header defining __BYT_ORDER. */ I think it should contain this reference http://sourceforge.net/p/predef/wiki/Endianness/ - and others to ensure that we can show it is written using publically available info, not the original SGI version - and not reverse-engineered either - the EU caved in to pressure from IBM et al to ban that! Paul --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow@hetp.u-net.com