Blake McBride
2020-09-21 22:08:18 UTC
Greetings,
Common Lisp is getting old. Technology marches on. I think a
significant upgrade to CLtl2 is in order. Here are some ideas I have:
Leave Common Lisp as it is except:
1. Functions and variables share the same namespace
2. Remove all of the Common Lisp function-specific functions that end
up as duplicates because of #1.
3. Change to a mixed-case language. The base language is lower-case.
4. Support real / native threads
5. Properly handle tail recursion
6. Improve on the ability to interact with the OS (sockets, etc.) -
perhaps as an extension.
These are just a few ideas. I think others can come up with more.
Although some of Common Lisp's functions are ugly with awkward
parameters, I think they're good enough for the most part and should be
left as-is so as not to change the language anymore than is necessary.
Blake McBride
Common Lisp is getting old. Technology marches on. I think a
significant upgrade to CLtl2 is in order. Here are some ideas I have:
Leave Common Lisp as it is except:
1. Functions and variables share the same namespace
2. Remove all of the Common Lisp function-specific functions that end
up as duplicates because of #1.
3. Change to a mixed-case language. The base language is lower-case.
4. Support real / native threads
5. Properly handle tail recursion
6. Improve on the ability to interact with the OS (sockets, etc.) -
perhaps as an extension.
These are just a few ideas. I think others can come up with more.
Although some of Common Lisp's functions are ugly with awkward
parameters, I think they're good enough for the most part and should be
left as-is so as not to change the language anymore than is necessary.
Blake McBride