[Mono-devel-list] Re: CodeDom in Compiler.cs

Eyal Alaluf eyala at mainsoft.com
Thu Mar 31 13:05:16 EST 2005


Hi, Atsushi.

Regarding CodeDom support - we could support the code generation of C# code
without any big porting problems. Where we are currently limited is in
on-the-fly compilation of the C# code to Java byte-code. Our tool for
converting from .Net assemblies to Java byte code is written in C++ and we need
to be as portable in our runtime environment as Java, so we do not support
compilation on the fly until we will rewrite the converter in Java (or C# :-).

Eyal.

On Fri, 1 Apr 2005, Atsushi Eno wrote:

> Date: Fri, 01 Apr 2005 02:52:16 +0900
> From: Atsushi Eno <atsushi at ximian.com>
> To: Andrew Skiba <andrews at mainsoft.com>
> Cc: mono-devel mailing list <mono-devel-list at lists.ximian.com>
> Subject: [Mono-devel-list] Re: CodeDom in Compiler.cs
>
> Hi Andrew,
>
> Andrew Skiba wrote:
> > Hello, Eno.
> >
> > Is there ary need for using System.CodeDom in Mono.Xml.Xsl/Compiler.cs?
> > If not, let's remove this line, otherwise I'll make an ifdef patch for
> > TARGET_JVM, as we don't support CodeDom.
> >
> > Thank you,
> > Andrew Skiba.
> >
>
> Just a curious, was CodeDom support impossible?
>
> Anyways if you mean Compiler.cs, it looked unnecessary so I just
> removed it. If you mean ScriptCompilerInfo.cs, we can't remove
> the line (it is in use for msxsl:script support), so please post
> a patch for the Java switch you guys want to add.
>
> Cheers,
> Atsushi Eno
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
>




More information about the Mono-devel-list mailing list