It's not a huge deal, but superfluous final keywords are clutter that distract from the places where final is being used meaningfully. I think it's worth cleaning this up incrementally in Restlet.
--tim On Tue, Oct 14, 2008 at 4:28 PM, Rob Heittman <[EMAIL PROTECTED]>wrote: > A bit of troglodytic practicality: I can easily tell Eclipse to stick > "final" wherever it possibly can, but not (to my knowledge) selectively omit > cases like catch blocks. So it makes code that looks like this. I agree > it's kind of dumb here, specifically, but the general practice of allowing > Eclipse to do this has kept me from many dumb mistakes in general, so I like > to leave this code cleanup option on. > > This is an oldie, but a goodie: > http://renaud.waldura.com/doc/java/final-keyword.shtml > > > On Tue, Oct 14, 2008 at 4:03 PM, Richard Hoberman < > [EMAIL PROTECTED]> wrote: > >> I'm doing some reading and have found the following links useful: >> >> 1. Link to a free chapter on the final keyword in Robert Simmons >> 'Hardcore Java' (O'Reilly) together with a useful summary. >> >> http://hoskinator.blogspot.com/2006/04/hardcore-java-final-story.html >> >> 2. Brian Goetz comments on the 'final' performance myths: >> >> http://www.ibm.com/developerworks/java/library/j-jtp1029.html >> >> >> >
