Link Details

Link 1104121 thumbnail
User 694429 avatar

By cristian.chiovari
Published: Feb 01 2014 / 12:18

A short answer for a quite disputed question.
  • 8
  • 3
  • 475
  • 2368


Add your comment
User 776377 avatar

lburnham123 replied ago:

1 votes Vote down Vote up Reply

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.

User 694429 avatar

cristian.chiovari replied ago:

0 votes Vote down Vote up Reply

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

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Voters For This Link (8)

Voters Against This Link (3)

Java EE7
Written by: Andrew Lee Rubinger
Featured Refcardz: Top Refcardz:
  1. Design Patterns
  2. OO JS
  3. Cont. Delivery
  4. CI Patterns
  5. CI Tools
  1. Spring Integration
  2. Git
  3. Regex
  4. Java
  5. REST