Re: Code style guidelines

2013-01-21 Thread Ionuţ Păduraru
Hi, 2013/1/19 Daniel Naber > On 18.01.2013, 17:35:01 Marcin Milkowski wrote: > > > Also, making a variable final should allow JVM to optimize the code > > more, and hence make it slightly faster. Most coding guidelines actually > > (including the one built-in in Eclipse) require to make as much

Re: Code style guidelines

2013-01-19 Thread Marcin Miłkowski
W dniu 2013-01-18 23:56, Daniel Naber pisze: > On 18.01.2013, 17:35:01 Marcin Milkowski wrote: > >> Also, making a variable final should allow JVM to optimize the code >> more, and hence make it slightly faster. Most coding guidelines actually >> (including the one built-in in Eclipse) require to m

Re: Code style guidelines

2013-01-18 Thread Daniel Naber
On 18.01.2013, 17:35:01 Marcin Milkowski wrote: > Also, making a variable final should allow JVM to optimize the code > more, and hence make it slightly faster. Most coding guidelines actually > (including the one built-in in Eclipse) require to make as much > finalization as possible. We should

Re: Code style guidelines

2013-01-18 Thread Marcin Miłkowski
W dniu 2013-01-18 13:49, Richard Eckart de Castilho pisze: >>> Do not use "final" for parameters or local variables, but write your code >>> as if there was a "final", i.e. do not re-assign local variables. Configure >>> your IDE to help you with that. For IntellJ IDEA, the warnings >>> ("inspectio

Re: Code style guidelines

2013-01-18 Thread Richard Eckart de Castilho
>> Do not use "final" for parameters or local variables, but write your code >> as if there was a "final", i.e. do not re-assign local variables. Configure >> your IDE to help you with that. For IntellJ IDEA, the warnings >> ("inspections") to activate are "Reuse of local variable" and "Assignment