4 ms·
I was obsessed with this for a little while several years ago and ended up making my own version based on the same paper: https://github.com/breckinloggins/vau/
by breckinloggins 6y ago
I was obsessed with this for a little while several years ago and ended up making my own version based on the same paper: https://github.com/breckinloggins/vau/blob/master/README.md https://github.com/breckinloggins/vau/blob/master/README.md
It was my second try at a lisp, the first being erlisp (https://github.com/breckinloggins/erlisp https://github.com/breckinloggins/erlisp).
Neither of these projects really went anywhere, but they really scratched an itch I had and I learned so much about programming language implementation while working on them.
If you haven't tried yet I highly recommend writing a little lisp of your own. It doesn't need to take over the world to be a meaningful project in your life.
- JoelMcCracken 6y agoIndeed, Kernel is to Scheme as Scheme is to Common lisp. Kernel really is a truly beautiful little idea.
- ungamedplayer 6y agoI played around with erlisp and lfe for a little while. I didnt write anything substantial but it got me interested in common lisp.
- xianwen 6y agoWould you recommend Common Lisp as the lisp dialect for a new beginner and for an eventual hobby project? Do you recommend SBCL over other Common Lisp implementations?
- varjag 6y ago(not the parent poster) Depending on the nature of your project. If it's some purely academic CS exploration, Scheme sometimes (but not always) allows you to express the concepts more eloquently. If it has to deal with practicalities of the broader world however, CL quickly takes over. The development experience is generally smoother in CL too. If you run your things on a major architecture (x86 or aarch64) SBCL is a great starting point. However on certain platforms other compilers are more feature complete.
- ungamedplayer 6y agoHowever most if what you write in one lisp can be ported over to another lisp without too much hassle.