user55340
user55340
Below is the code:
package annotationtype;
import java.lang.reflect.Method;
class Super{
static{
System.out.println("Super");
}
public void superMethod(){
}
}
class Sub extends Super{
static{
System.out.println("Sub");
}
public void subMethod(){
...user15026
user114359
user114359
-1
user55340
user55340
When reviewing code, I prefer to read if statements that explicitly demonstrate that a fork in code execution may occur:
if ( isFoo(baz) ) {
runBar();
}
When scanning hundreds of lines of the nonindented version, it is not obvious that a conditional may or may not occur:
boom += 1;
baz = ...user55340
user55340
user55340
user55340
I always prefer the version with braces.
If I don't always use the braces, then I may forget to put them when there is more than one statement in the block.
IDEs used by other team members can reformat the code automatically to move the statement to the new line, thus making it much more error ...user55340
user55340
user55340
user55340
The core question to the problem is one that needs work. I see it has been reopened, but the issue of it being primarily opinion has not been addressed or resolved.
Are there any other "good" uses for single-line if statements? How strictly should the practice be avoided? Note that I am expl...
user55340
user55340
Transcript for
Jul3
Jul '154
Jul5
The Whiteboard
General Discussion for softwareengineering.stackexchange.com P...
