Published: Feb 01 2014 / 12:18
Weaving has nothing to do with this. It is, as the article correctly points out, often done in JEE environments, but has nothing to do with compilation-vs-interpretation. It's also incorrect to put "compilation" in double quotes just because its end result is not machine code; that is not the definition of compilation, compilation is a translation process - just as the start representation need not be source code, so does the final representation not need to be machine code. Furthermore, JIT compilation does not mean to decide for each JVM instruction whether to interpret it or to translate it to machine code - that is done on a Java method level. And lastly, it needs to be said that JVM does not necessarily compile to machine code at all - the JIT may very well decide to interpret some method always.
Contrary to ordinary compilers, the Java compiler does not produce native executable code for a particular machine. Instead it produce a special format called byte code http://en.wikipedia.org/wiki/Java_compiler
Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.
Advertising - Terms of Service - Privacy - © 1997-2014, DZone, Inc.