Re: [boost] Regression test / compiler status progress

From: Rob Stewart (stewart_at_[hidden])
Date: 2002-07-09 10:38:59

From: "William E. Kempf" <williamkempf_at_[hidden]>
>
> From: "Beman Dawes" <bdawes_at_[hidden]>
>
> > The program which creates the status HTML is available at:
> >
> > The program which creates the log HTML is available at:
> >
> 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:

I second this idea.  XML will make the data far more useful.  The only question
is how to structure the XML.  Perhaps this is a good start:

<platforms>
    <platform>
        <os>
            <name>Solaris</name>
            <version>2.8</version>
        </os>
        <compilers>
            <compiler>
                <name>Sun Workshop</name>
                <version>6u2</version>
                <variant>Patch 111685-05</variant>
                <std-lib>STLport</std-lib>
                <results>
                    <test>
                        <name>libs/config/test/config_info.cpp</name>
                        <type>run</type>
                        <result>pass</result>
                    </test>
                </results>
            </compiler>
        </compilers>
    </platform>
</platforms>

Instead of using only elements as shown above, some values could be put in
attributes:

    <os name="Solaris" version="2.8">

Indeed, <compiler> is a little odd, above, because there are container and
non-container elements within it.  It could be done like this instead:

    <compiler name="Sun Workshop" version="6u2" variant="Patch 111685-05"
        std-lib="STLport">
        <test name="libs/config/test/config_info.cpp" type="run" result="pass"/>
    </compiler>

Optional elements are a little easier to test for than optional attributes, so
we could put optional stuff in child elements, and common stuff in attributes.
There are many alternatives possible.

What do you think?

Rob