I think
a) that all instance fields that *can* be immutable *should* be immutable
(helps a lot in making sure the code is thread-safe)
b) that all instance fields that are supposed to be immutable should be
declared as final, IMO it makes the code *more* readable
I usually don't declare local
Hi!
Sorry, can't resist to respond on this, since i'm paranoid at programming ;-)
Emmanuel Lécharny [mailto:elecha...@gmail.com] wrote
there are a lot of methods which have parameters with a 'final'
keyword.
It's most certaibly a IDE configuration, but it's really annoying.
It looks ugly,
Le 1/30/13 10:29 AM, Steve Ulrich a écrit :
Hi!
Sorry, can't resist to respond on this, since i'm paranoid at programming ;-)
Emmanuel Lécharny [mailto:elecha...@gmail.com] wrote
there are a lot of methods which have parameters with a 'final'
keyword.
It's most certaibly a IDE
Hi guys,
there are a lot of methods which have parameters with a 'final' keyword.
It's most certaibly a IDE configuration, but it's really annoying.
Can those who have this configuration set in their IDE change it so that
the committed code does not anymore contain the final keyword everywhere ?
I think final keyword on class attributes that need to be setted on
construction (immutable state) is a good practice.
I agree on local bloc code variable it's useless.
On Tue, Jan 29, 2013 at 1:04 PM, Emmanuel Lécharny elecha...@gmail.comwrote:
Hi guys,
there are a lot of methods which
Le 1/29/13 1:48 PM, Julien Vermillard a écrit :
I think final keyword on class attributes that need to be setted on
construction (immutable state) is a good practice.
yes, this is a third case where it's usefull : to guarantee that the
field *is* initialized.
--
Regards,
Cordialement,
