Revision as of 11:19, 1 March 2008 edit Aitias (talk \| contribs) Rollbackers 50,076 edits m Reverted edits by 82.22.71.88 (talk) to last version by Abdull ← Previous edit		Revision as of 12:59, 6 May 2008 edit undo SAE1962 (talk \| contribs) 514 edits m →Final methods: Link stated more precisely. Small corrections done. Next edit →
Line 23: </source> A common misconception is that declaring a class or method final improves efficiency by allowing the compiler to directly insert the method inline ~~where ever~~wherever it is called. This is not completely true; the compiler is unable to do this because the classes loaded at runtime might not be the same versions of the ones that were just compiled. Further, the runtime environment and [[Just-in-time compilation\|JIT]] compiler have the information about exactly what classes have been loaded, and are able to make better decisions about when to inline, whether or not the method is final.[http://www.ibm.com/developerworks/java/library/j-jtp1029.html]. = Final variables =

Final (Java): Difference between revisions