17 ms·
Practical Common Lisp is intro + recipes. I think Paul Grahams ANSI Common Lisp is the best if you are learning Common Lisp and Lisp. The language reference in
by nabla9 10y ago
Practical Common Lisp is intro + recipes.
I think Paul Grahams ANSI Common Lisp is the best if you are learning Common Lisp and Lisp. The language reference in the end is the extremely handy compact reference for CL. http://www.paulgraham.com/acl.html http://www.paulgraham.com/acl.html
Common Lisp Recipes is better as a pure recipe book. http://weitz.de/cl-recipes/ http://weitz.de/cl-recipes/
- hylisper 10y agoSlightly disagree with this....pg's work is the manual, though peter's examples and explanation of the concepts in lisp are practical to the core. To the point that you re-use your own code developed in the earlier chapters into the later chapters. That was the deal breaker, at least for me. Learning a new programming language is often bland, though engaging the reader practically isn't actually easy as it may seem.
- throwanem 10y agoAnother, more easily accessible, quick reference: http://clqr.boundp.org http://clqr.boundp.org I made a paper copy a while back, as is recommended by the authors. It's come in a lot of handy.
- harperlee 10y agoFor me, during the university ANSI Common Lisp was the Kernighan & Ritchie of Lisp - a standalone physical source of everything that I needed to start doing interesting things. Since then I haven't found another "canonical book" for another language that I jumped on, instead relying basically on internet. On that line, I loved "The haskell school of expression", though!
- bsder 10y ago> I think Paul Grahams ANSI Common Lisp is the best if you are learning Common Lisp and Lisp. I disagree, and here's why: Practical Common Lisp is the SINGLE Lisp reference I have ever found that talks about how to use real data structures instead of stupid cons pairs. That's really, really huge. And it's probably why so many people actively dislike Lisp. And it's probably why Clojure achieved such popularity.
- nocman 10y agoWhile I understand the need to use other data structures (and even in Lisp, I would not use cons pairs for everything), I think "stupid cons pairs" is pretty extreme. If you don't understand why cons is important, and the appropriate places to use it, then you really don't understand Lisp.
- wtbob 10y ago> If you don't understand why cons is important, and the appropriate places to use it, then you really don't understand Lisp. Lisp-the-mathematical-model, perhaps, but not Lisp-the-programming-language. Conses are definitely a fundamental idea, and they're obviously how source code is written, and it's nice that they're around — but honestly for real work it's unlikely that most data will live in cons structures (unless of course the higher-level data structures actually are built from conses, which of course they could be).
- deleted 10y ago[deleted]
- nocman 10y agoAt what point did I say "most data will live in cons structures"? And I explicitly said I would not use them for everything. And no, it isn't just "Lisp-the-mathematical-model", cons cells have real-world implications to the language. I was going to suggest watching the video presentation "The Swine Before Perl", by Shriram Krishnamurthi, but alas I can't find a link to the video (which is sad, because it is a very entertaining and informative video). The slides are here: ( http://ll1.ai.mit.edu/shriram-talk.pdf http://ll1.ai.mit.edu/shriram-talk.pdf ), but without the talk they may do you no good. Hopefully someone will see this and add a link to the video ( it should be made available again, even after all of this time, it is still great -- I believe I saw it as recently as 2 years ago).
- nabla9 10y ago>SINGLE Lisp reference I have ever found Then you haven't read many Lisp books, including Common Lisp Recipes and ANSI Common Lisp. There are so many of good ones.