Re: Interpreter design

neelk@alum.mit.edu (Neelakantan Krishnaswami)
19 Jan 2001 23:26:16 -0500

          From comp.compilers
Related articles
[3 earlier articles]
Re: Interpreter design kszabo@nortelnetworks.com (Kevin Szabo) (2001-01-18)
Re: Interpreter design steck@rice.edu (2001-01-18)
Re: Interpreter design gsc@zip.com.au (Sean Case) (2001-01-19)
Re: Interpreter design gvmt@localhost.vsnl.net.in (Venkatesha Murthy) (2001-01-19)
Re: Interpreter design jcgil@gmv.es (Juan Carlos Gil Montoro) (2001-01-19)
Re: Interpreter design guerby@acm.org (Laurent Guerby) (2001-01-19)
Re: Interpreter design neelk@alum.mit.edu (2001-01-19)
Re: Interpreter design anton@mips.complang.tuwien.ac.at (2001-01-20)
Re: Interpreter design nr@labrador.eecs.harvard.edu (2001-01-26)
Re: Interpreter design sdm7g@minsky.med.virginia.edu (Steven D. Majewski) (2001-02-01)
| List of all articles for this month |
From: neelk@alum.mit.edu (Neelakantan Krishnaswami)
Newsgroups: comp.compilers
Date: 19 Jan 2001 23:26:16 -0500
Organization: Compilers Central
References: 01-01-059 01-01-084
Keywords: books, interpreter
Posted-Date: 19 Jan 2001 23:26:15 EST

On 18 Jan 2001 01:05:35 -0500, Ian Kemmish <ian@jawssystems.com> wrote:
>
> John Allen's `Anatomy of Lisp' is probably a good start, if it's
> still in print. It also demonstrates how some issues (name binding
> etc) can be tackled by more than one strategy, and the various
> tradeoffs involved, so that it ends up being more than just a
> cookbook.


_Anatomy of Lisp_ is really old. You might want to try Christian
Queinnec's _Lisp in Small Pieces_ instead. It does a wonderful job of
showing the relationship between an interpreter and a compiler, in
particular.




Neel

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.