LISP in small pieces Christian Queinnec, Kathleen Callaway
Publisher: Cambridge University Press

Writing a recursive function to perform that calculation is pretty straight forward, and once we put all of these pieces together in our create-world routine, we have a working proof of concept. The great idea of quotation at least traces back to Lisp, where program is also a kind of data – the execution behavior of a piece of program is completely controllable by the user, just treat it as input data and write a custom evaluator for it. It was written by someone who knows his stuff and knows how to teach it. Get Queinnec's "Lisp in Small Pieces". The book is just under 500 pages of bootstrap. McCarthy He does a great job in Lisp in Small Pieces, but it's building on the foundation that McCarthy layed down. Lisp in Small Pieces is like that; it's more about a cute way to teach things that bends the mind than having fun in exploring design trade-offs. In other words, it is not really about truly building models. I bought Lisp In Small Pieces, read 19 pages, then struck out on my own, writing a headcase macro to factor out the repetition from the SICP code, and an interpreter. Easy to compile (most implementations of Lisp are written almost or entirely in Lisp, and the “reference” implementations usually include a compiler – see Sussmann's Scheme book or 'LiSP in Small Pieces' for examples). The following code snipped from the REPL prompt We're glossing over a few details here, but if you have a little experience working with Lisp then you should have a pretty good idea of how to implement the above. But one, day I found a nice small piece of lisp which allow me simplify the process. Otherwise I would be hard pressed to choose something like The Art of the Metaobject Protocol, The wizard book, or maybe Lisp In Small Pieces. Queineec, C., Lisp in small pieces, Cambridge University press, Cambridge, 1996. The default Lisp evaluator is eval, we can easily write a Remember F# has a rich set of syntax while a domain language takes a small subset of it is usually enough expressive. I'm actually not that fond of TAOCP. See Lisp in Small Pieces by Christian Queinnec. While I have started reading Lisp in Small Pieces, it hasn't had quite the impact on me. If you are writing code that needs to live and is critical to the organization, hire literate programmers and an English major as an editor-in-chief. €�It is widely held among members of the MIT Lisp community that FEXPR, NLAMBDA, and related concepts could be omitted from the Lisp language with no loss of generality and little loss of expressive power, and that doing so would make a general improvement in the quality and reliability of program-manipulating programs.” .