Re: Interpreter design

Sean Case <gsc@zip.com.au>
19 Jan 2001 23:15:25 -0500

          From comp.compilers
Related articles
Interpreter design jcgil@gmv.es (Juan Carlos Gil Montoro) (2001-01-11)
Re: Interpreter design basile.starynkevitch@wanadoo.fr (Basile STARYNKEVITCH) (2001-01-18)
Re: Interpreter design ian@jawssystems.com (2001-01-18)
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)
[1 later articles]
| List of all articles for this month |
From: Sean Case <gsc@zip.com.au>
Newsgroups: comp.compilers
Date: 19 Jan 2001 23:15:25 -0500
Organization: Marginal
References: 01-01-059 01-01-084
Keywords: interpreter, books
Posted-Date: 19 Jan 2001 23:15:25 EST

In article 01-01-084, ian@jawssystems.com (Ian
Kemmish) wrote:


> jcgil@gmv.es says...
> >What is the best strategy to implement an interpreter for a custom
> >language?.


> John Allen's `Anatomy of Lisp' is probably a good start, if it's still in
> print.


According to Amazon, it isn't. Note that it is one of the worst
typeset books I have ever seen -- it was entirely set on a computer in
1978 with output at what looks like 150dpi.


It is also a little old fashioned, in that it puts a lot of effort
into correctly implementing dynamic scope, which is pretty much a dead
issue for everyone except hardcore Emacs users.


It's still an excellent book, just very much of its time.
--
Sean Case gsc@zipworld.com.au


Code is an illusion. Only assertions are real.

Post a followup to this message

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