On Tue, Mar 12, 2013 at 4:31 AM, John Maddock
Are there any news on what might be done regarding this? I looked a little
more into it today, and it appears as though something as trivial as boost/circular_buffer.hpp pulls in the whole config folder with endian.hpp and limits.hpp so I am avoiding using them altogether for now in this project.
I've just removed detail/limits.hpp and edited boost/limits.hpp to not refer to it.
We'll see if anyone complains I guess.
endian.hpp is harder to know what to do with: there's no actual code in there, it's more like the accumulated wisdom of multiple Boosters plus bug reports etc. I'm actually not sure why SGI's copyright ended up in there: looks like when Caleb Epstein originally wrote that header he borrowed the "wisdom" from limits.hpp and so put SGI's copyright on it. Any ideas on how we would go about creating a clean version? If someone described the logic in words, and someone else wrote a new header from the description would that do it - or am I deceiving myself?
If someone describes the general aspects of the detection I can see about adding it to my Predef library. With the eventual expectation that the library is going to make it into Boost soon obviously. But if it doesn't it would be then OK to steal the code into Boost without the library.. I could also do some research into doing the detection entirely on my own. But that would take more time. PS. The Predef library has almost all the changes from the review in it by now (documentation being the largest change left). -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo