[Mono-list] HTML Mockup for Class Lib Todo's

[John Barnette]

At 10:53 PM 2/11/2002, you wrote:
>Now I see what CorCompare is up to I'm beginning to see the tricky parts! I
>agree we need a tool that will build a composite XML file from an enhanced
>CorCompare that would determine what is missing (and what is extra?) in the
>Mono Corlib and merge that with more detailed class status information from
>the todo generator and with some supplemental data about the maintainer etc.
>
>Thinking about the todo generator - it must be possible to organise the
>directory structure and naming conventions of the tests so that we can
>automagically determine whether or not there are at least _some_ tests for a
>given class. Could we go (or have we already gone) further and arrange that
>the tests deposit some kind of standardised pass/fail mark file so that we
>can figure out whether the implementation has passed the tests? Is this
>similar to what Duncan's up to?

Guys,

Apologies for the tardy response (and any bounced mail); I've been fighting 
an epic DNS battle for about the last 72 hours.

Might want to check out the mcs/doctools directory, as there's a tool in 
there that does a lot of this (percentages, etc) already.  Improve away. ;-)


~ j.