> I think the xslt road is the best bet. A c++ code solution > would result in a > much higher complexity and most likely to a much higher > memory footprint. > > The xslt processor can be treated similar to the other tools > like cvs and svn, > which gives ctest the chance to do some error checking. +1 Reinhold