Where i work, we dont use final on arguments but have checkstyle rules against reassigning method arguments On Jun 13, 2011 5:57 PM, "Josh Berry" <tae...@gmail.com> wrote: > 2011/6/13 Cédric Beust ♔ <ced...@beust.com>: >> My argument is that I can hardly remember last time I was bitten by a bug >> because I reassigned a variable wrongly (or even, I reassigned a variable, >> period). In contrast, the noise introduced by using `final` everywhere is as >> annoying to me as Python saying `self` every other word, so overall, the >> trade-off is not worth it. > > I've had this argument at work several times. We have a style guide > saying that you must make all parameters final. I'm not against it, > per se, but I do think it is silly to think that it prevents mistakes > in most places. (Now, fields, I'm all for making final and curse gwt > whenever I realize I have to stop doing so.) > > -- > You received this message because you are subscribed to the Google Groups "The Java Posse" group. > To post to this group, send email to javaposse@googlegroups.com. > To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/javaposse?hl=en. >
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javaposse@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
