[Mono-list] ECMA compliance

Smith, Scott D scott.d.smith@intel.com
Fri, 30 Nov 2001 12:08:49 -0800


Hi John,

> I think the first couple of steps would include using Intel's OCXT to
> generate stubs for classes we haven't hit yet, and writing tools to check
> the compliance of classes that we've already written.  Assuming this is a
> good idea, maybe a specific mailing list?

OCL 0.2.0 is generated from the final draft ECMA XML library definition
file, so it is completely up to date.  Given this, another option is to
directly use source from OCL to fill in the gaps.
(http://sourceforge.net/projects/ocl)

Scott

-----Original Message-----
From: Miguel de Icaza [mailto:miguel@ximian.com]
Sent: Wednesday, November 21, 2001 11:01 PM
To: John Barnette
Cc: mono-list@ximian.com
Subject: Re: [Mono-list] ECMA compliance


> Seeing as Intel's done some awfully nice stuff with their OCXT efforts
(and
> since, I believe, we've satisfied ourselves as to the legitimacy of using
> the EXMA specs and XML definition to generate/validate code), I'd like to
> get a few of us together to track and actively manage Mono's ECMA
> compliance.

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.

> I think the first couple of steps would include using Intel's OCXT to
> generate stubs for classes we haven't hit yet, and writing tools to check
> the compliance of classes that we've already written.  Assuming this is a
> good idea, maybe a specific mailing list?

Yeah, we should write tools to make sure that our API matches the one
from ECMA.

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. 

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.

Miguel.

_______________________________________________
Mono-list maillist  -  Mono-list@ximian.com
http://lists.ximian.com/mailman/listinfo/mono-list