Skip to content
quotesby

About this quote

What does it mean?
The comment advises postponing magical operations until later, attached to a break statement.
In plain terms
Don't do magic yet; break first.
What can you take from it?
Separate simple control flow from complex operations.

Where it applies

  • debugging
  • feature implementation

Putting it to work

  • use break to isolate sections
  • add complex code later

Questions to consider

  • When should you defer complexity?
  • How to ensure later addition doesn't break flow?

Another view

Delaying needed logic may cause later integration issues.

More from Larry Wall

  1. /* And you'll never guess what the dog had */ /* in its mouth... */

    Permalink to quote #241
  2. str->str_pok |= SP_FBM; /* deep magic */ s = (unsigned char*)(str->str_ptr); /* deeper magic */

    Permalink to quote #246
  3. double value; /* or your money back! */ short changed; /* so triple your money back! */

    Permalink to quote #236

Related quotes

  1. If you try to solve a hard problem, the question is not whether you will use a powerful enough language, but whether you will (a) use a powerful language, (b) …

    Paul GrahamPaul Graham quote #5
  2. A programming language is for thinking of programs, not for expressing programs you've already thought of.

    Paul GrahamPaul Graham quote #10
  3. Portability is for people who cannot write new programs.

    Linus TorvaldsLinus Torvalds quote #16