I'm curious about this in my java book (translation) :
"With its perfectly defined nature, a final method permit for the compiler :
- to optimise some parts of the code: faster calls because independent from the execution, to put 'online' the code of some methods..."
I tried a little efficiency test over a small method call inside a java loop, with or without final, but it's the same. True that my test might be too simple.
Can really "final" classes/methods be sometimes more efficient?
But even without knowing about the amount of speed gain, we should anyway set all our mxj objects to "final", no ?