[Mono-list] On porting to C#
Mon, 9 Jul 2001 15:52:48 -0700
Hmm, I'd probably emphasize Java *language* compatibility as opposed to
byte code compatibility. I've not looked at Java's byte codes in quite
some time, but I believe that MS had a fundamentally different mindset
when developing MSIL, which was that MSIL was never to be interpreted,
only JITed. This might make compatibility on the MSIL/Byte Code level a
bit tricky due to the philosophical differences.
Besides, it's probably much easier just to throw together a Java
compiler that uses the CodeDOM and Reflection.Emit stuff as an MSIL
puker than it is to write a Byte code converter, which, IMHO, misses the
point of the CLR.
On Monday, July 9, 2001, at 03:37 PM, Miguel de Icaza wrote:
> Hello guys,
> Sam brings up an interesting point: why port existing software from
> Java to C#? Given that the CLR is supposed to be language neutral, it
> makes sense to make sure that Java byte codes can be executed in the
> The only issue I see is that Java programs will expect a set of
> class libraries to be available for them to use, and this might not be
> the case for the CLR. What approach do you suggest we should use Sam?
> Mono-list maillist - Monofirstname.lastname@example.org