From: David Abrahams (dave_at_[hidden])
Date: 2003-02-19 03:02:11
"Gennadiy E. Rozental <rogeeff_at_[hidden]>" <rogeeff_at_[hidden]> writes:
>> > Any way to implement this in bounds of Boost.Build?
>> Yes, it's doable, but no, I want to try to do it.
> This statement confuses me o bit. Couldn't you rephrase it?
It means that it's possible to implement it, but I don't want to try
to do it.
>> It would be a lot of work for me.
> In fact I meant "implement in Jamfile in bounds of existent
Oh, well in that case, I guess "not too easily." I mean, the stuff
that goes in your Jamfile is the same stuff that goes in Boost.Build,
so in that sense anything you can do in Boost.Build can be done in
>> Why not just always run with --save_pattern=yes?
> --save_pattern is the switch between match and save mode. In match
> mode it perform matching vs. file content (i.e. real testing). While
> in save mode it store strings into file for further use for
> matching. This way I may check that output is the same as it was
> before (i.e. correct)
> However, if test is failing I would like to know what output was
> produced in fact. It would help me to find the source of error.
In that case, what about implementing a new test mode which both saves
-- Dave Abrahams Boost Consulting www.boost-consulting.com
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