From: David Abrahams (dave_at_[hidden])
Date: 2003-01-04 20:39:30
Beman Dawes <bdawes_at_[hidden]> writes:
> At 12:16 PM 1/4/2003, David Abrahams wrote:
> >Tell me precisely what you need dumped and I'll add it to the testing
> >rules when --dump-tests is used.
> The current output looks like:
> (boost-test "foo_test" : "libs/foo/test\foo_test.cpp" )
> If you could add the test type ("run", "compile-fail", etc.) that would
> cover the only killer requirement.
> So the above sample might become:
> (boost-test "run" "foo_test" : "libs/foo/test\foo_test.cpp" )
> That's the only "must have".
> Nice to have, but not essential, would be a way to pass a string from the
> Jamfile to the "boost-test" output line.
It's not a problem, but I guess that the interface for the testing
rules is getting a bit heavy. I probably ought to implement named
parameters so that you don't have to remember to add exactly ten
colons between the test name and that string.
Do the tests which need that extra info occur in groups, and are they
relatively rare? We could do it with something like:
local .dump-test-note = always_show_run_output ;
# test declarations
compile-fail whatever ... ;
Jam's dynamic scoping comes in handy sometimes. That "local" variable
overrides any global definition until the scope exits.
> Right now "always_show_run_output" is the only string recognized, but I
> want to implement several other features that need a way to pass a string.
> This would be nice, but isn't a showstopper.
The above interface works just fine, if it isn't too cumbersome in
-- David Abrahams dave_at_[hidden] * http://www.boost-consulting.com Boost support, enhancements, training, and commercial distribution
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk