3 ms·
Originally Lisp was all upper case. The line of languages is six decades old, after all. The first Lisp program I ever wrote was on punch cards on an IBM 70
by pfdietz 6y ago
Originally Lisp was all upper case. The line of languages is six decades old, after all. The first Lisp program I ever wrote was on punch cards on an IBM 7094.
The evolution of to Common Lisp had to deal with this. The solution (which works well) is that the default mode of the Lisp reader converts symbol names to upper case, unless they are escaped. So, the common case is that symbols are lower case in source files, but are upper case internally, and typically are printed in upper case (that can be tweaked if desired.)
- galaxyLogic 6y agoSo we have Lisp where case does not (mostly) matter and Python where even whitespace matters. We have APL famil;y of languages which invented their own alphabet. In hindsight I wonder if there is any consensus or studies on which approach is the best?
- rurban 6y agoIn hindsight we know now what was problematic about the lisp reader conventions. The default should have been lowercase case-sensitive, esp. for the ffi. But we've only got uppercase case-insensitive, with flags for inverse (an ugly hack) and case-sensitive. This way you can call C or Java functions, but internally it's all case inversed. And still broken in some lisps