
28 Jun
2005
28 Jun
'05
9:09 p.m.
David Abrahams <dave@boost-consulting.com> writes:
Our standard practice is to keep the workaround in place for future versions using BOOST_TESTED_AT(), which tends to ensure that library code doesn't break when a user gets a new compiler and also gives us a way to locate all workarounds that can be limited to earlier versions when a later version comes out.
That makes a lot more sense than testing that we're under some non-existant compiler version. Thanks. -- Chris