Breaking Out of Loops: Using break and continue

Why Loops Keep Running

An infinite loop never terminates because its condition never becomes false. The important question is therefore not simply whether a loop contains repeated work. The important question is whether the condition controlling the loop can eventually become false.

Following Control Flow

Use the diagram as a tracing model. A normal iteration returns to the loop condition after the loop body completes. A break provides an exit from a loop before the condition becomes false. The source pack identifies break as a possible event that intentionally ends a while True loop. The source pack does not provide a detailed definition of continue, so the key diagnostic lesson here is to trace every control-flow path and ask whether it can reach a terminating condition or an intentional exit.

Finite Progression

A terminating loop has three connected features: a finite starting value, a condition that checks that value, and code inside the loop that moves the value toward a stopping point. If the condition eventually becomes false, the loop terminates. The body can perform many different tasks, but those tasks matter for termination only when they affect the values used by the condition.

The while True Pattern

The constant True in a while condition creates an infinite loop because the condition itself never becomes false. Each time the condition is checked, it produces the same true result, so the loop keeps returning to its body unless another intentional exit is provided.

Runaway Loop Diagnosis

1. Start with the loop condition. Write down exactly what must become false for normal termination.
2. Identify every variable or value used by that condition.
3. Trace whether the loop body changes those values.
4. Check whether each control-flow path reaches a condition-changing update or an intentional break.
5. If the condition is while True or there is no iteration variable, locate the specific event that is supposed to end the loop.
6. If no terminating path is clear, treat the loop as a likely bug and stop examining the repeated path until its exit logic is understood.

• Assuming that work inside the loop automatically makes the loop terminate.

  The loop body does not control termination by itself. The condition must eventually become false, or an intentional exit must be reached.

  Fix: Trace the values used by the condition and verify that the body moves them toward a stopping point.

• Treating the presence of a variable as proof that the loop is finite.

  A terminating loop needs a finite starting value, a condition that checks it, and code that moves it toward the end.

  Fix: Check the complete relationship among the starting value, condition, and update.

• Reading while True without asking how it exits.

  True never becomes false, so the condition cannot provide normal termination.

  Fix: Locate the intended event or break statement. If no exit is clear, investigate the loop as a likely bug.

• Assuming every infinite loop is accidental.

  Infinite loops can be deliberate when a specific event controls their exit.

  Fix: Distinguish an intentional event-controlled loop from a loop whose exit path is missing or unclear.

Practice the Trace

Key Takeaways

1. An infinite loop never terminates because its condition never becomes false.
2. A terminating loop has a finite starting value, a condition that checks it, and an update that moves it toward a stopping point.
3. A loop with no iteration variable or with a condition that is always true can run indefinitely.
4. while True is intentional only when a clear event or exit mechanism, such as break, ends the loop.
5. To diagnose a runaway loop, inspect the condition, the values it depends on, and every control-flow path that repeats.