3 ms·
There's always Common Lisp. Still portable 35 years on. I recall once, not quite 20 years ago, porting a large CL program from a 32-bit implementation to one
by ScottBurson 7y ago
There's always Common Lisp. Still portable 35 years on.
I recall once, not quite 20 years ago, porting a large CL program from a 32-bit implementation to one of the then-new 64-bit Lisps. Someone who didn't know CL thought that would be a hellish job, but it turned out to be quite straightforward.
- justinjlynn 7y agoWith the new research being done in macro-level type systems there's a lot of great reasons to check out lisp again (as a person who loves strongly typed languages)! Type Systems as Macros - https://www.ccs.neu.edu/home/stchang/pubs/ckg-popl2017.pdf https://www.ccs.neu.edu/home/stchang/pubs/ckg-popl2017.pdf Dependent Type Systems as Macros - https://www.ccs.neu.edu/home/stchang/pubs/cbtb-popl2020.pdf https://www.ccs.neu.edu/home/stchang/pubs/cbtb-popl2020.pdf It's so cool - especially the bits where they reconstruct each part of the type system and show how each feature they add contributes to the power/capability of it. :D
- ScottBurson 7y agoI used macro expansion for type checking in Zeta-C [0], the first C compiler for Lisp Machines, in 1983. Didn't write a paper about it, though. Dependent types are certainly interesting -- I'll give this a read. Thanks! [0] http://bitsavers.trailing-edge.com/bits/TI/Explorer/zeta-c/ http://bitsavers.trailing-edge.com/bits/TI/Explorer/zeta-c/
- justinjlynn 7y agoAwesome! I'm really enjoying reading your source code. Cool stuff; would definitely be interested in hearing your opinion of the papers.