From: Chris Uzdavinis (chris_at_[hidden])
Date: 2005-06-28 16:09:08
David Abrahams <dave_at_[hidden]> 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.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk