Don't be flippant if your flippant premise is entirely wrong, Robert. What I said boils down to:
1. If your team is making mistakes, findbugs will figure this out even without enforcing final. 2. You'll make mistakes if you are stupid* in either scenario. 3. Don't be afraid of refactoring. (This point wasn't even remotely related to bad/stupid/mistaken code!) Specifically: There is considerable harm in enforcing 'final' usage. The right answer is obviously: Use 'final' where appropriate, and don't where it isn't. Any explicit unbreakable rule is generally a bad thing. What should be the default? non-final wins, because its shorter and does not require your IDE to magic in extra keywords. *) "being stupid" in the sense of programming happens to everybody. Good programmers are stupid less often, but nobody's immune. On Feb 13, 8:59 pm, Robert Fischer <[email protected]> wrote: > Your three counter-arguments boil down to: > > 1. Don't expect your team to be stupid/make mistakes. > 2. Don't be stupid/make mistakes. > 3. Don't write stupid/mistaken code. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
