4 ms·
I absolutely love developing in Common Lisp, and I agree with you. Some suggestions: - Get rid of upcasing; 21st-century languages should be case-sensitive an
by rauhl 7y ago
I absolutely love developing in Common Lisp, and I agree with you.
Some suggestions:
- Get rid of upcasing; 21st-century languages should be case-sensitive and case-preserving. Allegro’s modern mode is the Right Thing™ here IMHO.
- Fix things like order-of-argument inconsistencies in the standard library.
- Consider adding type to streams to indicate whether they are input, output or both and character, byte or both.
- Base the package system off of Go’s.
- More fully specify pathnames.
- Specify a standard library roughly equivalent to Go’s. At this point I think it’s the gold standard (Python’s used to be, but no longer).
- vindarel 7y agoOn upcasing: (setf *print-case* :downcase)
- rauhl 7y agoOh definitely — that is a must! But it doesn’t do you any good if e.g. you want to turn read symbols into shell commands. You can play some games with :invert, but at the end of the day it’s a hack. I don’t blame them for upcasing back in the 90s, but … it’s not the 90s anymore.
- rurban 7y agoNot downcase, modern. I.e case-preserving and case-sensitive. E.g. to be able to define native ffi calls into CamelCase functions. Downcasing is destroying information, Modern is keeping the original symbol names