Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman
by Oreb on Sunday November 13, 2022 @07:42AM
(#33582525)
Source code is indeed meant to be read, and at least to me, low information density seriously hurts readability. I prefer both Python-style indentation based syntax and multiple parens at the end of the line over C-style syntax with closing braces alone on a line. If I write code in a language with curly brace syntax and I don’t have to share the code with others, I prefer to use multiple closing braces on the same line – like Lisp parens – because of improved readability.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman
by pfdietz on Sunday November 13, 2022 @08:27AM
(#33582828)
Parens allow an editor to create the proper indentation.
You can think of Lisp's paren syntax as the syntactic analogue of Lisp's very simple static type system. To get macros to work with a conventional grammar's complexity is much more annoyingly complex.
Because the human brain is a pattern-matching organ and sometimes redundancy in a signal is useful. I've never understood the lispers' insistence that saving "screen real estate" is a primary concern. Source code is meant to be read, and the more easily code is read, the more utility is has.