On Lisp
paulgraham.com
On Lisp
1–10 of 107 posts
Re: On Lisp
#2Instructions for printing it with lulu: http://www.lurklurk.org/onlisp/onlisp.html . I did this about a month ago and the copy I received was great.
Re: On Lisp
#3Cheers to PG for making this available.
Re: On Lisp
#4I've been meaning to read this for quite some time, but I've been told that the idioms and coding style is outdated, or not very good. This isn't going to stop me, but I'd like to know from some experienced lispers what problems I might encounter. Especially as I'm pretty inexperienced myself. I definitely won't know what to look for.
Re: On Lisp
#5Instructions for printing it with lulu: http://www.lurklurk.org/onlisp/onlisp.html . I did this about a month ago and the copy I received was great.
The link to the lulu's book is not working for me... Can you please share it?
Re: On Lisp
#6I've been meaning to read this for quite some time, but I've been told that the idioms and coding style is outdated, or not very good. This isn't going to stop me, but I'd like to know from some experienced lispers what problems I might encounter. Especially as I'm pretty inexperienced myself. I definitely won't know what to look for.
The book uses common lisp, so you'll need to know how to read that. Otherwise I think you should be fine. It's not a book about idioms or coding styles, but about thinking in lisp. If the code examples are confusing, it'll be because you're not sure what something means in common lisp or because you're learning new ideas, not because the code is poorly written. So, if you treat it as a book of ideas as opposed to "teach yourself x language in 24 hours", you should be OK :)
Re: On Lisp
#7I've been meaning to read this for quite some time, but I've been told that the idioms and coding style is outdated, or not very good. This isn't going to stop me, but I'd like to know from some experienced lispers what problems I might encounter. Especially as I'm pretty inexperienced myself. I definitely won't know what to look for.
I'm not an experienced lisper, but onlisp lacks what sicp describe when talking about abstraction barriers/layers. Also too much mutation. There's good content (macro, logic programming, patterns) but you need to detach from low-level lisp hackery.
Re: On Lisp
#8I've been meaning to read this for quite some time, but I've been told that the idioms and coding style is outdated, or not very good. This isn't going to stop me, but I'd like to know from some experienced lispers what problems I might encounter. Especially as I'm pretty inexperienced myself. I definitely won't know what to look for.
I'm not an experienced lisper, but onlisp lacks what sicp describe when talking about abstraction barriers/layers. Also too much mutation. There's good content (macro, logic programming, patterns) but you need to detach from low-level lisp hackery.
Tain't Scheme---err Racket, 'tis Common Lisp, warts and all...
Re: On Lisp
#9I look forward to reading this, however I object to the first reviewer comment: "The first book that really explains what Lisp is all about."
No, I think the first book to explain that was Godel, Escher, Bach.
Re: On Lisp
#10I've been meaning to read this for quite some time, but I've been told that the idioms and coding style is outdated, or not very good. This isn't going to stop me, but I'd like to know from some experienced lispers what problems I might encounter. Especially as I'm pretty inexperienced myself. I definitely won't know what to look for.
It is written to a prior version of the Common Lisp standard, and with a very old-fashioned style. You'll see calls like (REPLACA pair val) instead of (SETF (CAR pair) val) and so on. That will irk you if you are a Common Lisp hacker already. If you're not, just keep in mind that good CL style results in somewhat prettier code than that in On Lisp.