Re: [boost] Regression test / compiler status progress

From: William E. Kempf (williamkempf_at_[hidden])
Date: 2002-07-08 17:24:48

----- Original Message -----
From: "Beman Dawes" <bdawes_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Monday, July 08, 2002 3:56 PM
Subject: [boost] Regression test / compiler status progress

> The program which creates the status HTML is available at:
>
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost-sandbox/boost-sandbox/l
ibs/filesystem/example/compiler_status.cpp?rev=1.2&content-type=text/vnd.vie
wcvs-markup
>
> The program which creates the log HTML is available at:
>
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/boost-sandbox/boost-sandbox/l
ibs/filesystem/example/compiler_status_log.cpp?rev=1.1&content-type=text/vnd
.viewcvs-markup

A suggestion... instead of generating HTML I'd generate XML.  You can then
generate HTML from the XML using XSLT.  The reasons for doing this:

* The resulting XML file can be used for a lot more then just giving a
pretty report on the web.  For instance, it could be used by a script that
creates an installation package for a given platform which would exclude
libraries that are not supported by that platform (just an example off the
top of my head).

* It's fairly easy to tweak the XSLT file for specific formatting
requirements.  For example, you could use different XSLT files to generate
HTML pages both for what libraries a specific compiler supports and what
compilers a specific library supports in addition to the normal matrix used
for status information today.  This could be useful for compiler vendors
(among others), as they could generate reports tailored to their business
needs with little effort.

Bill Kempf