[Mono-list] ECMA compliance

[Miguel de Icaza]

> This is pretty much what I was assuming.  I have a vague memory of looking
> at this a couple months ago, though, and thinking that one could not
> generate useful user-readable docs for a library unless one used both the
> generated XML *and* the assembly to create it.

You are correct.  I just went to look this up.

The ECMA `All.xml' file has one file format, while the documentation
generated by the compiler while passing the /doc option has a different
one.

The ECMA XML file seems better suited for describing every component of
the library, while the output generated from the compiler only seems to
document the `members'  (and you are right, you are supposed to have
some kind of assembly side-by-side). 

In any case, it seems like we will have to cope at least with two file
formats ;-(

Miguel.