From: David Abrahams (dave_at_[hidden])
Date: 2003-01-05 10:53:19
David Abrahams <dave_at_[hidden]> writes:
> David Abrahams <dave_at_[hidden]> writes:
>> 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.
> I guess I can answer my own question by looking at status/Jamfile.
> The answer appears to be yes, since only one test needs to do this.
> For now, I'll implement this approach because it's easy to implement.
> If we find ourselves needing to do it a lot, we can come up with
> something easier for users.
Done. Turns out the approach above wouldn't have worked well with our
test-suite idiom. To get more information from --dump-tests output,
add <test-info>whatever to the target requirements, as many times as
you like. If you do this, after the test name, a square-bracketed
list of the "whatever" strings will appear in the --dump-tests output.
-- 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