Re: Interpreter design

18 Jan 2001 00:52:19 -0500

          From comp.compilers

Related articles
Interpreter design (Juan Carlos Gil Montoro) (2001-01-11)
Re: Interpreter design (Basile STARYNKEVITCH) (2001-01-18)
Re: Interpreter design (2001-01-18)
Re: Interpreter design (Kevin Szabo) (2001-01-18)
Re: Interpreter design (2001-01-18)
Re: Interpreter design (Sean Case) (2001-01-19)
Re: Interpreter design (Venkatesha Murthy) (2001-01-19)
Re: Interpreter design (Juan Carlos Gil Montoro) (2001-01-19)
[5 later articles]
| List of all articles for this month |

Newsgroups: comp.compilers
Date: 18 Jan 2001 00:52:19 -0500
Organization: - Les Ours
References: 01-01-059
Keywords: interpreter
Posted-Date: 18 Jan 2001 00:52:18 EST

>>>>> "Juan" == Juan Carlos Gil Montoro <> writes:

        Juan> What is the best strategy to implement an interpreter for a
        Juan> custom language?. I've done compilers and translators [...]

First of all, unless you want to do research in programming languages
(in which case you'll already know the answer to the question), *DO
NOT* design yet another language from scratch.... But try to use an
existing language design (perhaps enhancing it).

If you do want to make a new langage, first study lots of existing
languages and existing implementations....

In short, the best strategy to implement an interpreter is to not do

Perhaps you could use or extend an existing implementation... Why not
use Ocaml, Scheme, Tcl, Python, Perl, Ruby, etc....?

Do you need to embed an interpreter inside an application (or do the
reverse: embed your application inside an interpreter).

Perhaps you could translate your language to an existing bytecode
interpeter (such as Ocaml's, or JVM, or VSCM, ....).


email: basile dot starynkevitch at wanadoo dot fr (France)
alias: basile at tunes dot org host:
8, rue de la Fa´encerie, 92340 Bourg La Reine, phone:

Post a followup to this message

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