on Tue Feb 28 2012, Rene Rivera <grafikrobot-AT-gmail.com> wrote:
On 2/27/2012 1:20 PM, Dave Abrahams wrote:
One thing I don't see is any distinction between the target being compiled for and the host on which the compilation is happening. You could make an argument that no such distinction is needed, but in the absence of such an argument I suggest changes like BOOST_ARCHITECTURE_XXX => BOOST_TARGET_ARCHITECTURE_XXX
I don't think I made such an argument :-) The argument is way simpler than that. None of the compilers I'm aware of tell you *directly* what host architecture they are running if it happens to be different from the target architecture. The best you can do is some user defined predef, or something derived from running something like uname.
As for the name.. I'm open to suggestions. But as was mentioned ealier the name is rather long already. Which many people already object to.
Also, when BOOST_TARGET_ARCHITECTURE_XXX is 1, shouldn't we also have
#define BOOST_TARGET_ARCHITECTURE XXX
?
What would the "XXX" be in the define? ..The only option I can see is defining a string literal. Which is only useful for informational debugging uses. And not the more general decision testing.
Good points. I don't think I was thinking very clearly :-) -- Dave Abrahams BoostPro Computing http://www.boostpro.com