On Tue, Oct 14, 2008 at 2:41 PM, Jerome Louvel <[EMAIL PROTECTED]>wrote:
> For the 'final' keyword usage, it might save a bit of memory at most. No
> big gain here I suspect.
How would memory be saved? Are there really compilers that generate
different bytecode depending on the presence of the final keyword in this
case?
try {
...
} catch (/*final*/ Exception e) {
return null;
}
The only reason I know to use final in the catch argument declaration is if
you need to refer to the exception from an inner class in the catch clause.
--tim
