[Mono-list] ECMA compliance

[John Barnette]

> It would be great if you could identify which classes are available in
> OCXT and have not been placed in Mono.   Also, it would be nice to
> extract the documentation in the ECMA spec and stick that into the class
> libraries.

Yeah, this is where I was planning on starting.  While identifying possible
coverage holes will be pretty trivial, I'm open to any suggestions on an
efficient way to insert the ECMA API docs into existing files.

> We also need to identify if there are differences between ECMA and
> .NET.  If they differ, I would like to give preference to .NET as that
> is more likely going to be useful to people.

Absolutely.  I think it's probably going to be easier to document MS.NET as
a delta from the ECMA stuff, though.

> If there is an interest in having *both* (and this is dependant upon us
> finding whether they differ or not, at this point I dont know)
> libraries: one ECMA compliant and one .NET compliant, we could do that
> by adding a separate target to our Nant build.

See comment above.  I have little doubt that the Microsoft versions will
change faster than the ECMA specs, and this seems like it might be a pretty
good idea.


~ j.