Interpreting LISP
by Gary D. D. Knott · first published 2017
5mentions
1recommended by
3HN commenters
2015–2025first – last mentioned
33% recommend67% critical
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
for what it is worth, here is a version of a lisp interpreter I wrote in python: https://github.com/keithgabryelski/plisp I used _Interpreting_LISP_ by Gary D. Knott as a guide.
on “Lisp as the Maxwell Equations of Software (2012)” ↗Here is my version of a lisp interpreter in python: https://github.com/keithgabryelski/plisp it's not meant to be pythonic -- it's meant to readable and organized my inspiration was Interpreting LISP by Gary D. Knott written in 1997 (the pdf of it is included in the repository)
on “How to Write a Lisp Interpreter in Python (2010)” ↗It is called Interpreting Lisp by G. Knott. Reddit discussion: https://www.reddit.com/r/lisp/comments/6qc61v/second_edition... Not to be confused with other books from the 1980s about doing Lisp in C, like Lisp: A Portable Implementation…
on “Land of Lisp (2010)” ↗The 900-something lines of C code documented by the book Interpreting Lisp, which can now be found on Github, is not something I would recommend for teaching C beginners. From a best practices point of view, it is pretty awful. https://github.com/Apress/interpreting-lisp
on “Land of Lisp (2010)” ↗…confusing. Anecdata: as glad as I am for Apress for working with me and releasing my own book about a part of Common Lisp (which is, technically, non-fiction!), I still cannot fathom their re-release of "Interpreting LISP" [1] - a book that I hated to give a zero-star rating on Reddit [2] but that I can only warn people about, if I am to be acting in good faith. [1] https://link.springer.com/book/10.1007/978-1-4842-2707-7…
on “Mass market non-fiction has bad incentives” ↗