[
Lists Home |
Date Index |
Thread Index
]
Dare wrote :
>>Why not hear it from the horse's mouth (so to speak),
>>
>>
>http://msdn.microsoft.com/library/en-us/Dndotnet/html/deicazainterview.asp
>
>As for me, there are indeed technical merits to the CLI over the JVM
>especially w.r.t versioning, cross-language support and loading multiple
>versions of the same class at runtime (Assembies vs. class files)[0]. As
for
>superiority between the languages I think C# adds features that I'd like to
>see in Java but the lack of one or two Java characteristics makes me
pensive
>about embracing it completely. Of course, I've already written copious
>amounts about my feelings about both languages[1]
WRT to cross-language support, please don't forget that the JVM is different
from the Java language. Granted, the CLR can handle more native data types
than the JVM, and has facility that make the porting of some language to the
CLR easier than to the JVM, but the JVM is in no way limited to the Java
language. Here is a non-exhaustive list of language for which an interpreter
or compiler exists for the JVM :
http://flp.cs.tu-berlin.de/~tolk/vmlanguages.html
Note the existence of PerCOBOL, a compiler (generating JVM bytecode) for the
COBOL language, the arch-example used by Microsoft for language independance
of the CLR.
There is also a very interesting book on the JVM demonstrating the
implementation of Prolog and Scheme for the JVM :
http://cseng.aw.com/book/0,3828,0201309726,00.html
Regards,
Nicolas Lehuen
|
