From: Hubert HOLIN (Hubert.Holin_at_[hidden])
Date: 2002-11-15 10:06:21
Somewhere in the E.U., le 15/11/2002
David Abrahams wrote:
> Hubert HOLIN <Hubert.Holin_at_[hidden]> writes:
> > Somewhere in the E.U., le 15/11/2002
> > Bonjour
> > Something odd is going on... My code does include
> > <boost/config.hpp> (on line 16 for both quaternion_test.cpp and
> > octonion_test.cpp, on line 13 for quaternion_mi_test.cpp, though
> > admitedly not yet for quaternion_mi1.cpp, quaternion_mi2.cpp and
> > HSO3SO4.cpp... I'll fix that right now). I checked both my local
> > copy and the (browser-visible) CVS copy.
> That's a very strange approach. Usually these config headers must be
> #included in boost headers, not source files... (?)
Well, it was intentional, if not very smart.
The idea was that the config files essentially allowed workarounds for
platform deficiencies, so if your platform was conformant, you did not
need them. Including the config from the headers hides from the user his
platform's deficiencies, whereas he should be (painfully) aware of them
so as to complain to his vendor. Having to include the config files in
user code was supposed to raise awareness of the problem. Of course, for
the test files, they must be present.
If this is found to be confusing or unwieldly, I can change.
> David Abrahams
> dave_at_[hidden] * http://www.boost-consulting.com
> Boost support, enhancements, training, and commercial distribution
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk