Le samedi 24 mai 2014 11:10:04 William Ferguson a écrit : > > parameters and local variables are not considered final: there is nothing > > wrong > > with modifying their value, and nothing good to get by forcing them to be > > > final > > But there *is* value is defining them to be final. > > If you as the programmer know that a value should never change, then by > denoting it as final you can enforce that it is not inadvertently modified > by someone else. If they deem that the restriction needs to be loosened > because requirements have changed then they can do so. > > It is just like specifying an assertion. It is about code correctness and > less failures. I understand your point, I know the value of giving as much value as possible to static checks done by compiler
but if you don't have big ultra-complex methods, this final keyword adds unnecessary clutter that's my opinion, and that was the opinion of the team a few years ago, the last time this was discussed Regards, Hervé --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
