Re: Interpreter design

ian@jawssystems.com (Ian Kemmish)
18 Jan 2001 01:05:35 -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)
[4 later articles]
| List of all articles for this month |
From: ian@jawssystems.com (Ian Kemmish)
Newsgroups: comp.compilers
Date: 18 Jan 2001 01:05:35 -0500
Organization: At home with Ian
References: 01-01-059
Keywords: interpreter, design
Posted-Date: 18 Jan 2001 01:05:35 EST

jcgil@gmv.es says...
>What is the best strategy to implement an interpreter for a custom
>language?. I've done compilers and translators, but the mechanics of
>an interpreter (storing the interpreter state, in particular) puzzles
>me.
>
>Thanks for any suggestion, URL, book or whatever!


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.


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Ian Kemmish 18 Durham Close, Biggleswade, Beds SG18 8HZ, UK
ian@jawssytems.com Tel: +44 1767 601 361

Post a followup to this message

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