> The main issue people have with the book is that it uses CLISP-specific code in a few places. CLISP's last release was seven years ago, and because it hasn't

> The main issue people have with the book is that it uses CLISP-specific code in a few places. CLISP's last release was seven years ago, and because it hasn't really been maintained it's beginning to bitrot. Folks in #lisp generally don't recommend using CLISP these days, instead recommending actively-maintained implementations like SBCL, CCL, ECL, ABCL, etc. Note that CLISP is actively maintained; the most recent change was three hours ago: https://sourceforge.net/p/clisp/clisp/ci/63508ea11cf0b2062ca62031ab1edddb5f72e7b0/ https://sourceforge.net/p/clisp/clisp/ci/63508ea11cf0b2062ca... I have no idea why the maintainer hasn't released a new version since 2010. Doesn't make any sense to me. I use SBCL, but CLISP is still alive.