Java bytecode: Difference between revisions

Content deleted Content added
@modi (talk | contribs)
Make clearer
Line 3:
A [[Java (programming language)|Java]] programmer does not need to be aware of or understand Java bytecode at all. However, as suggested in the [[IBM]] developerWorks journal, "Understanding bytecode and what bytecode is likely to be generated by a Java compiler helps the Java programmer in the same way that knowledge of assembler helps the [[C (programming language)|C]] or [[C++]] programmer."<ref>[http://www-128.ibm.com/developerworks/ibm/library/it-haggar_bytecode/ Understanding bytecode makes you a better programmer]</ref>
 
It is possible to write Java bytecode by hand, however this method is almost never used in real life because nowadays the [[compiler]]s are able to compile well performing code and nearly no person is able to comprehend a piece of Java bytecode of considerable size. Originally only one compiler existed, the [[javac]] compiler from Sun Microsystems, which compiles [[Java source code]] to Java bytecode. But because all the specifications for Java bytecode are available, other parties have supplied compilers that produce Java bytecode. E.g.:
* [[Jikes]], compiles from the Java programming language to Java bytecode
* [[JGNAT]], compiles from the [[Ada programming language]] to Java bytecode