From: Douglas Gregor (gregod_at_[hidden])
Date: 2001-09-03 21:50:35
On Sunday 02 September 2001 12:12, you wrote:
> ----- Original Message -----
> From: "Douglas Gregor" <gregod_at_[hidden]>
> > Resolution: if the macro BOOST_STRICT is defined, all workarounds will be
> > disabled. If BOOST_STRICT is not defined (the default), the Config system
> > will be pessimistic about new compiler versions. Running regression tests
> > with this macro defined will exercise new compiler versions so that the
> > Config system can be updated without requiring users to deal with the
> > system.
> Will there be some way to have all workarounds disabled only on compiler
> versions unknown to the config system?
I didn't think that we have reached a concensus on that, but I think it would
be useful. John Maddock suggested a #error if a developer/regression tester
(signaled by BOOST_DEVELOPER/BOOST_REGRESSION_TEST) is heading into uncharted
waters. Then the brave soul can use BOOST_STRICT to commence configuration.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk