Labeled Statements

Java does not support arbitrary goto statements. Instead, it provides Labeled Statements, which allow you to attach identifier labels to loops or blocks. You can then reference these labels with break or continue, allowing you to exit or skip iterations of outer loops from deep within nested loops.

Syntax and Execution Mechanics

A label is any valid Java identifier followed by a colon (e.g., outerLoop:), placed immediately before a loop statement or block.

• Labeled Break: Exits the loop or block marked by the specified label. Execution resumes at the first statement after that labeled block.

  outer: for (...) {
      for (...) {
          break outer; // Exits outer loop completely
      }
  }

• Labeled Continue: Jumps to the update expression and condition check of the loop marked by the label, skipping any remaining iterations of both inner and outer loops.

  outer: for (...) {
      for (...) {
          continue outer; // Jumps to outer loop's next iteration check
      }
  }

Common Pitfalls

• Labeling Non-Loop Blocks for Continue: Attempting to use a labeled continue on a standard block that is not a loop causes a compile-time error.
• Spaghetti Code Complexity: Overusing labeled statements can make the execution path hard to follow, similar to the deprecated goto statement. Use them only when they improve readability by replacing complex boolean flags.
• Shadowing labels: Re-declaring a label with the same identifier name in nested scopes can trigger compiler resolution issues.

Best Practices

• Use labeled breaks primarily to exit nested loops when a search criteria is met, which is cleaner than using multiple flag check variables.
• Use descriptive, meaningful names for labels (like searchGrid:) instead of generic names like loop1:.
• Keep nested blocks short so labels are easily visible on the same screen.

Interview-Relevant Information