I must say that I have never understood the "final" on method arguments. It doesn't bring any value. If the method argument is a native type, I can change it as much as I want as it doesn't modify the caller's value. If the argument is a mutable object, "final" doesn't stop me from modifying the object, only the reference which in turn doesn't affect the caller. Similar for local variables. And IMHO, "final" adds a lot of clutter everywhere. I like using "final" where it makes a difference, not out of principle. -- Cheers, Niclas.
On 5/24/08, Michael Hunger <[EMAIL PROTECTED]> wrote: > IntelliJ - switch on intentin "local variable can be final", go to any > highlight of this occurrence. Alt-Return -> Popup-Menu to the right - > use "Fix All" for current file or Run On ... to run it on the whole > module or even project. By now I had never an issue with these IDEA > finalized stuff (no false positives). So go ahead :) > > If the intention is switched on, your files all get quite yellow. Thats > easy to keep your eyes on. > > Michael > > Rickard Öberg schrieb: >> David Leangen wrote: >>> Hey, >>> >>> Just going through the code again a bit today. I noticed that there isn't >>> much use of "final" for classes, methods, or fields. >>> >>> What's the policy on that? >> >> In general, final is good. I'm just sloppy in applying it most of the >> time. My forte is not details, but rather the "big picture" :-) I would >> really appreciate havingh more eyes on the code to fix things like that. >> >> /Rickard >> >> _______________________________________________ >> qi4j-dev mailing list >> [email protected] >> http://lists.ops4j.org/mailman/listinfo/qi4j-dev > > > _______________________________________________ > qi4j-dev mailing list > [email protected] > http://lists.ops4j.org/mailman/listinfo/qi4j-dev > -- Sent from Gmail for mobile | mobile.google.com _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
