Stewart, Robert wrote:
Zachary Turner wrote On Tuesday, June 09, 2009 2:30 PM
And perhaps the best approach is what I mentioned in a previous post, to force the programmer to explicitly define BOOST_USE_PRAGMA_ONCE before including a boost header file. This would solve the problem of having to modify every header when new compilers were released.
I agree that a single manifest constant to control using #pragma once is the right thing to do. However, the scheme you describe here puts too much onus on the Boost user. Why not define that manifest constant on the compiler command line using Boost.Build? You can define that for each compiler, unless I'm much mistaken.
That will not help somebody who includes boost headers in his project, I think. - Volodya