if-else Statements

In Java, conditional execution is governed by if, else-if, and else blocks. Unlike C/C++ which permit integers to serve as truthy/falsy markers, Java enforces strict type safety: the condition expression inside an if statement must evaluate to a primitive boolean or its wrapper Boolean.

Boolean Condition Constraints

Java requires conditions to be strictly boolean. Writing if (x = 5) where x is an integer will result in a compile-time error because an assignment evaluates to the assigned value (an integer), not a boolean. However, if x is a boolean variable, writing if (x = true) is valid Java syntax but represents a logic trap since it assigns true and evaluates to true.

The Dangling-Else Problem

When if statements are nested without curly braces, an ambiguity arises as to which if block a trailing else belongs to. Java resolves this by pairing the else with the nearest preceding un-paired if in the same block.

if (a > 0)
    if (b > 0)
        System.out.println("Both positive");
else
    System.out.println("a is negative?"); // WRONG: paired with if (b > 0)!

Common Pitfalls

• Omitting curly braces: Writing if (cond) statement1; statement2; leaves statement2 outside the conditional scope. It will execute unconditionally, regardless of the condition value.
• Variable Initialization Check: Declaring a local variable inside an if block without an else block, and then referencing it later, causes compiler errors. The compiler detects that the variable might not have been initialized if the condition is false.
• Confusing comparison (==) with assignment (=): Writing if (flag = false) on a boolean changes the variable state instead of validating it.

Best Practices

• Always use explicit braces {} for all branches to make block structures visually distinct.
• Use Guard Clauses (early exits) to handle validation rules, reducing nested conditional indentations.
• Compare boolean variables directly, e.g., use if (isActive) instead of if (isActive == true).

Interview-Relevant Information