"Peter Dimov" <[EMAIL PROTECTED]> writes: > From: "David Abrahams" <[EMAIL PROTECTED]> >> > I like it. >> >> I don't (yet). Why do we need yet another macro which means "turn off >> the workarounds?" Would BOOST_STRICT_CONFIG then be obsolete? > > I think that the idea is that BOOST_STRICT_CONFIG applies only to unknown > compiler versions, and BOOST_DISABLE_WORKAROUNDS (do we need separate > compiler/library macros?) would be applied unconditionally, regardless of > whether the compiler has known defects.
What's the use of distinguishing those? Surely the person who's doing the testing doesn't care about whether we think we "know" that particular compiler version? -- David Abrahams [EMAIL PROTECTED] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost