[Mono-list] Will the compiler be ever more than 50% .net compatible?
Guenther Roith
groith@tcrz.net
Sun, 10 Mar 2002 19:52:43 +0100
This is a multi-part message in MIME format.
------=_NextPart_000_00A2_01C1C86D.2484D4C0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I tried to compile a small application (Digger) on windows with msc and =
it failed because of many errors. But go-mono.com says the compiler is =
nearly ready. So will it ever be .net compatible (on windows) with the =
.net framework ?
------=_NextPart_000_00A2_01C1C86D.2484D4C0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I tried to compile a small application =
(Digger) on=20
windows with msc and it failed because of many errors. But go-mono.com =
says the=20
compiler is nearly ready. So will it ever be .net compatible (on =
windows) with=20
the .net framework ?</FONT></DIV></BODY></HTML>
------=_NextPart_000_00A2_01C1C86D.2484D4C0--