From: Darin Adler (darin_at_[hidden])
Date: 2001-11-29 11:43:45
On 11/29/01 6:47 AM, "Peter Dimov" <pdimov_at_[hidden]> wrote:
>> ** Metrowerks CodeWarrior
>> mwcc -o boosttmp.exe -maxerrors 10 -cwd source -I- -Ic:/boost/site
>> ### mwcc Compiler:
>> # File: ..\site\libs\bind\bind_test.cpp
>> # ----------------------------------------
>> # 193: bind<void>(Y(), i, _1, 9, 4)(k);
>> # Error: ^
>> # illegal use of 'void'
> This particular test case never worked with MW. Dave originally had it
> #ifdef-ed out but this is cheating, isn't it? ;-)
> How should we proceed in cases like this? #ifdef the test case just to see a
> 'pass'? Or keep the test as-is and be honest with users?
The downside of leaving the test as-is is that this single problem causes
the entire bind_test to fail. This means that when we make other changes to
bind, the regression test doesn't catch the problems.
Because of this, I think it's reasonable to turn off parts of the tests even
if that's misleading. I especially like Beman's suggestion of using
Boost.Config to remind ourselves of the particular shortcoming of the
compiler that requires turning off part of the test. Adding things to
Boost.Config does require a bit of work, though. And we don't have a
particular BOOST_NO_XXX for this particular problem, do we?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk