Re: Pocket Reference for Common Lisp

dfeustel@xxxxxxxxxxxxxx writes:

I'm reading and getting a lot out of _Practical Common Lisp_.
I'd like to get a pocket book documenting all the common lisp
functions, macros, etc for use when writing lisp code.
O'Reilly doesn't seem to do Lisp.
Is there such from another source?

Install a local copy of the Common Lisp HyperSpec. That's the most
physical space- and time-efficient solution.
.

Relevant Pages

  • Re: ILC2005: McCarthy denounces Common Lisp, "Lisp", XML, and Rahul
    ... The examples I'm thinking of were DW to CLIM, ... > code) to Common Lisp in about 3 months. ... > function call parts, not the macros. ... > if it's part of the design strategy. ...
    (comp.lang.lisp)
  • Re: ILC2005: McCarthy denounces Common Lisp, "Lisp", XML, and Rahul
    ... code) to Common Lisp in about 3 months. ... few months at symbolics, I managed to use macrology to hide ... And at every step where it was tried, macrology hid the porting issues ... function call parts, not the macros. ...
    (comp.lang.lisp)
  • Re: Wondering if you guys would like to comment on this
    ... > in Java 1.5, as part of JSR-201. ... > annoyance that Common Lisp programmers can resolve for themselves ... > within five minutes plagues Java programmers for years. ... Macros are generally meant to make your program clearer. ...
    (comp.lang.lisp)
  • Re: LET improved, time wasted
    ... the syntax to his needs he is told that reader macros are ugly. ... Common Lisp provides you all the necessary tools to shoot yourself into your ... live with the basics of the language and try to write some more useful code. ... That you can change Common Lisp does NOT mean you should start with it. ...
    (comp.lang.lisp)
  • Re: Sacla loop: a new loop implementation
    ... >> use it to do type inference before macro expansion in order to supply ... > portably in common lisp, because the facilities just aren't there. ... useful type information at compile time, then you are working with a ... if you say that you are willing to accept that your macros ...
    (comp.lang.lisp)