You say you've read all of "Practical Common Lisp".  That's great!  I
don't know of any book that's a sequel, or generally about "advanced
Lisp".  If you want to learn about some specific area, post here about
it and maybe some of us might know a good place for you to look.

It depends first of all on whether your goal is to write practical
programs
in Common Lisp, or to learn about programming languages.  If the
latter,
I recommend "Structure and Interpretation of Computer Programs, 2nd
ed",
by Abelson, Sussman, and Sussman.

- Dan

Re: Further reading Tamas K Papp
- Re: Further reading Daniel Weinreb

From: Tamas K Papp
Subject: Re: Further reading
Date: Mon, 19 Jan 2009 22:14:49 +0000
Message-ID: <6tkcapFbc6v0U1@mid.individual.net>

On Mon, 19 Jan 2009 13:14:05 -0800, Dan Weinreb wrote:

> You say you've read all of "Practical Common Lisp".  That's great!  I
> don't know of any book that's a sequel, or generally about "advanced
> Lisp".  If you want to learn about some specific area, post here about
> it and maybe some of us might know a good place for you to look.

I don't see the original question, but I have just finished reading
Let Over Lambda, it is simply amazing, a real eye-opener.  PG's On
Lisp is a good book too.

Tamas

From: Daniel Weinreb
Subject: Re: Further reading
Date: Mon, 19 Jan 2009 23:40:11 +0000
Message-ID: <vb8dl.696$Aw2.133@nwrddc02.gnilink.net>

Tamas K Papp wrote:
> On Mon, 19 Jan 2009 13:14:05 -0800, Dan Weinreb wrote:
> 
>> You say you've read all of "Practical Common Lisp".  That's great!  I
>> don't know of any book that's a sequel, or generally about "advanced
>> Lisp".  If you want to learn about some specific area, post here about
>> it and maybe some of us might know a good place for you to look.
> 
> I don't see the original question, but I have just finished reading
> Let Over Lambda, it is simply amazing, a real eye-opener.  PG's On
> Lisp is a good book too.
> 
> Tamas

Sorry, I posted this with the wrong subject line.

I have a copy of Let Over Lambda and I read about
two thirds of it.  The author's approach to writing
macros is different from the tradition that I'm
accustomed to, so some of it looks pretty peculiar
to me.  In particular, he makes heavy use of macros
that generate symbol names, so that the body of
your macro uses variable names that were never
"introduced" anywhere explicitly (e.g. an argument
list or a let or something).  I had always thought
that was a bad practice.

If anyone at work were doing this, I'd suggest finding
another way.

However, I don't want to be doctrinaire when it comes
to books (or research).  You sure do learn a lot about
writing macros from reading Let Over Lambda.

-- Dan