On Friday, September 20, 2002, at 10:46 , Joe Eugene wrote: > True, *similar*(concept) emphasized, then the CLR plays a big role in code > execution.. translating MSIL into native code.. *AS Needed*..
C# -> compiles to MSIL -> loaded into CLR -> interprets & validates code then uses JIT compiler to create native code. Java -> compiles to Java ByteCode -> loaded into JVM -> interprets some, uses JIT compiler to create native code for some. The main difference is that Java ByteCode was designed as the *portable* target for Java whereas MSIL was designed as a (fairly) proprietary target for multiple languages. The other important difference - as I understand it - is that MSIL is compiled on demand before execution whereas Java ByteCode can be interpreted or compiled, in other words, the difference is in how aggressive the Java JIT compiler is (does it compile everything or only 'critical' / oft-used pieces?). Should MSIL/CLR be inherently more efficient than Java ByteCode/JVM? Maybe. The former was designed to target one runtime architecture (although it is fairly abstract). The latter was designed to target multiple architectures. The JIT compilation - in both cases - to the target architecture's machine code should generally level out that playing field. "If you're not annoying somebody, you're not really alive." -- Margaret Atwood ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
