News for hackers. Stuff that matters.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by kazinator on Sunday November 13, 2022 @12:47PM (#33585346)
I've been working with Lisp for over twenty-two years and still got tripped up recently by something that was

  (if (condition)  ;; <- must be when, not if!
    (do-this)
    (do-that))
Phony complaints about problems with editing parentheses and getting them to match are just trolling nonsense, but Lispers should acknowledge this kind of problem: when your editor has already helped you ensure that the code has valid syntax, everything is beautifully indented and compiles without diagnostics, but you have a mistake like this: parentheses being closed in the wrong place, not including something, or the wrong operator like the above.

There are similar problems in other languages; no notation is perfect, and attempted cures for some of these problems can be worse than the diseases.

GCC's relatively recent "misleading indentation" warning is a good example of a cure that has no downside (that I can quickly think of). It can catch code like:

  if (condition)
    do_this();
    do_that();  // not part of the if statement, but indented deceptively
No language save you from writing a program similar to the one you should be writing, but which is correct for a different set of requirements relative to what you want. Just verification and testing.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman by jlokier on Sunday November 13, 2022 @03:08PM (#33586806)

  (if (condition)  ;; <- must be when, not if!
    (do-this)
    (do-that))
I didn't find that to be a common problem when writing Emacs Lisp at least. The "misleading indentation" warning is relevant thre. If you enter the above code into Emacs, auto-indenting as you go, it will indent like this, making it obvious you meant `when`:

  (if (condition)
      (do-this)
    (do-that))