When in doubt, parenthesize. At the very least it will let some poor schmuck bounce on the % key in vi.
About this quote
- What does it mean?
- When unsure, add parentheses; it prevents errors and helps editors like vi.
- In plain terms
- Parenthesize to avoid mistakes.
- What can you take from it?
- Use parentheses to clarify precedence.
Where it applies
Putting it to work
Questions to consider
- When does extra parentheses hurt more than help?
Another view
Over‑parenthesizing can clutter code.
More from Larry Wall
*** The previous line contains the naughty word '$&'. if /(ibm|apple|awk)/; # :-)
Permalink to quote #275 But I'm not here to talk about postmodernism. I tried to do that last spring, and afterwards I was thoroughly deconstructed by the deconstructionists for attem…
Permalink to quote #277 The autodecrement is not magical.
Permalink to quote #274
Related quotes
And don't tell me there isn't one bit of difference between null and space, because that's exactly how much difference there is. :-)
Larry WallLarry Wall quote #2 > (It's sorta like sed, but not. It's sorta like awk, but not. etc.) Guilty as charged. Perl is happily ugly, and happily derivative.
Larry WallLarry Wall quote #51 We toast the Lisp programmer who pens his thoughts within nests of parentheses.
Alan PerlisAlan Perlis quote #2