From: Douglas Gregor (gregod_at_[hidden])
Date: 2003-01-04 18:04:02
On Saturday 04 January 2003 12:02 pm, Beman Dawes wrote:
> Currently, such schemes break the status table generation because
> compiler_status.cpp actually scans status/Jamfile looking for test-type and
> some other more minor information. If we could figure a way to
> echo that information into the output (either to std::cout or in one
> of the residue files), it would make include schemes and
> compiler_status.cpp less fragile.
I've recently added support into the Boost documentation format for expressing
testsuites directly. From the XML representation of the testsuite, I have
written an XSL stylesheet that generates a Jamfile for boost/status (the new
file boost/status/testsuites.jam is generated this way), and I could easily
dump the information in another format (e.g., a simplified XML format for
compiler_status.cpp to read).
The advantage of using the XML testsuite representation within the modified
DocBook format is that we get testsuite documentation (like Ron Garcia did in
the Multi Array library), autogeneration of Jamfiles (less likely to break
things), and the ability to generate testcases from code snippets in the
documentation (if you look at the set of "function" testcases for today,
you'll see that there are lots of failures because my tutorial examples are
riddled with typos).
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