|
Boost : |
From: David Abrahams (dave_at_[hidden])
Date: 2005-07-11 07:53:57
Tobias Schwinger <tschwinger_at_[hidden]> writes:
>>>And while we're at it -- I'ld like a variant of BOOST_TESTED_AT, "BOOST_TESTED"
>>>that also takes the comparison operator:
>>>
>>> BOOST_WORKAROUND(BOOST_MSVC,BOOST_TESTED(> 1200))
>>
>>
>> And what do you think that is supposed to do?
>
> Evaluate to true if we use MSVC and the compiler version is above
> 1200.
Ooo kaaay...
> That is, with the ability to detect incomplete workarounds (like
> BOOST_TESTED_AT).
So, can you spell out what that means? When I define
BOOST_DETECT_OUTDATED_WORKAROUNDS, what would the behavior be?
> It further allows us more flexibility to express
> what was tested and what wasn't when submitting patches.
That's what BOOST_WORKAROUND does already. I don't see what new
information you get from wrapping BOOST_TESTED around the test.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk