Boost logo

Boost :

Subject: Re: [boost] License of endian and limits in Boost detail
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2013-03-19 08:01:58

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Rene Rivera
> Sent: Tuesday, March 19, 2013 4:18 AM
> To: boost_at_[hidden]
> Subject: Re: [boost] License of endian and limits in Boost detail
> On Mon, Mar 18, 2013 at 9:59 AM, Rene Rivera <grafikrobot_at_[hidden]> wrote:
> > On Mon, Mar 18, 2013 at 9:10 AM, Paul A. Bristow <pbristow_at_[hidden]>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 <
> Currently only tested on my OSX laptop. Would appreciate others trying it
> out. The info is a combination of the indispensable description from
> (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

- 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 A. Bristow,
Prizet Farmhouse, Kendal LA8 8AB  UK
+44 1539 561830  07714330204

Boost list run by bdawes at, gregod at, cpdaniel at, john at