[Mono-list] ECMA compliance
Barnette, John
JBarne3@citgo.com
Fri, 30 Nov 2001 14:26:10 -0600
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C179DD.3F8CF420
Content-Type: text/plain;
charset="ISO-8859-1"
> 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
Monkeys,
Sorry about the (possibly) nasty state of this email; I'm on a client site,
and they're running a rather draconian install of Microsoft Exchange.
I'm certainly up for taking this on, and have been considering a process
something like this:
(I haven't unpacked and looked at OCL yet, although I shall
this evening)
1. If necessary, merge the OCL files into Mono's directory
structure (mcs/class/<assembly>/<namespace>) with added
extensions (probably Foo.cs.ocl)
2. Add OCL classes that are missing from Mono by simply
renaming and checking in.
3. Merge other classes (for the sake of documentation and
exact signature conformance).
I was thinking that checking in the OCL classes with a different extension
in the correct directory and then asking maintainers to do a manual merge
might be a good way to go about this.
Thoughts?
~ j.
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you received
this in error, please contact the sender and delete the material from any
computer.
------_=_NextPart_001_01C179DD.3F8CF420
Content-Type: text/html;
charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Mono-list] ECMA compliance</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>> OCL 0.2.0 is generated from the final draft ECMA =
XML library </FONT>
<BR><FONT SIZE=3D2>> definition</FONT>
<BR><FONT SIZE=3D2>> file, so it is completely up to date. =
Given this, another </FONT>
<BR><FONT SIZE=3D2>> option is to</FONT>
<BR><FONT SIZE=3D2>> directly use source from OCL to fill in the =
gaps.</FONT>
<BR><FONT SIZE=3D2>> (<A =
HREF=3D"http://sourceforge.net/projects/ocl" =
TARGET=3D"_blank">http://sourceforge.net/projects/ocl</A>)</FONT>
<BR><FONT SIZE=3D2>> </FONT>
<BR><FONT SIZE=3D2>> Scott</FONT>
</P>
<P><FONT SIZE=3D2>Monkeys,</FONT>
</P>
<P><FONT SIZE=3D2>Sorry about the (possibly) nasty state of this email; =
I'm on a client site, and they're running a rather draconian install of =
Microsoft Exchange.</FONT></P>
<P><FONT SIZE=3D2>I'm certainly up for taking this on, and have been =
considering a process something like this:</FONT>
</P>
<P> <FONT SIZE=3D2>(I haven't =
unpacked and looked at OCL yet, although I shall</FONT>
<BR> <FONT SIZE=3D2> =
this evening)</FONT>
</P>
<P> <FONT SIZE=3D2>1. If =
necessary, merge the OCL files into Mono's directory</FONT>
<BR><FONT SIZE=3D2> =
structure (mcs/class/<assembly>/<namespace>) with =
added</FONT>
<BR><FONT SIZE=3D2> =
extensions (probably Foo.cs.ocl)</FONT>
</P>
<P> <FONT SIZE=3D2>2. Add OCL =
classes that are missing from Mono by simply</FONT>
<BR><FONT SIZE=3D2> =
renaming and checking in.</FONT>
</P>
<P> <FONT SIZE=3D2>3. Merge =
other classes (for the sake of documentation and</FONT>
<BR><FONT SIZE=3D2> =
exact signature conformance).</FONT>
</P>
<P><FONT SIZE=3D2>I was thinking that checking in the OCL classes with =
a different extension in the correct directory and then asking =
maintainers to do a manual merge might be a good way to go about =
this.</FONT></P>
<P><FONT SIZE=3D2>Thoughts?</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>~ j.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>The information transmitted is intended only for the =
person or entity to which it is addressed and may contain confidential =
and/or privileged material. Any review, retransmission, dissemination =
or other use of, or taking of any action in reliance upon, this =
information by persons or entities other than the intended recipient is =
prohibited. If you received this in error, please contact the sender =
and delete the material from any computer.</FONT></P>
</BODY>
</HTML>
------_=_NextPart_001_01C179DD.3F8CF420--