Re: What next after 'Practical' ??

On 29 Apr 2005 13:44:01 -0700, <lavigne.eric@xxxxxxxxx> wrote:
>
> I've been going back and forth between Practical Common Lisp and ANSI
> Common Lisp (with Common Lisp the Language, 2nd ed as a reference). I
> find that PCL and ACL complement eachother fairly well.

I decided that picking up Winston & Horn (3rd ed) from Ebay would help
referee the above.

> By the way, I set up a signature with my webpage, but I don't see it at
> the end of my posts. Can anyone else see it? I'm wondering if google
> groups hides it from me or if I messed up the setup.

I have never seen it actually work, just your occaisonal manual
additions. You might want to consider using Free Agent, or perhaps
there is a usenet reader on Lisp-In-A-Box.


--
Everyman has three hearts;
one to show the world, one to show friends, and one only he knows.
.

Relevant Pages

  • Re: Common Lisp is not a language
    ... | a) we do ANSI Common Lisp ... | b) here are some places where we don't do ANSI CL ... Required Language Features ... PURPORTS TO CONFORM v. makes a good-faith claim of conformance. ...
    (comp.lang.lisp)
  • Re: finding the position of an element in a "list of strings"
    ... As a newbie, you can learn more reading a tutorial or a ... book about Common Lisp than the Reference. ... NEW GRAND UNIFIED THEORY DISCLAIMER: ...
    (comp.lang.lisp)
  • Re: The Amazon PCL tide may be heading back out to sea
    ... > said ANSI-CL was a good reference, but I thought it was a regular intro ... reasonable CL environment, there's no reason to use any other source ... Lisp is an excellent exposition of /all/ features of Common Lisp. ...
    (comp.lang.lisp)
  • Re: which lisp book ?
    ... Common Lisp: The Reference, which was published by Franz, is a now ... horribly out-of-date referece which corresponds only to the 1984 first ...
    (comp.lang.lisp)
  • Re: Common Lisp book still apropos?
    ... of course---just don't use it as a reference for ANSI ... Common Lisp. ... The truly good code is the obviously correct code. ...
    (comp.lang.lisp)