Related articles |
---|
Q: Intermediate code for interpreting & compiling? davis@wln.com (1995-02-10) |
Re: Q: Intermediate code for interpreting & compiling? torbenm@diku.dk (1995-02-14) |
Re: Q: Intermediate code for interpreting & compiling? cef@geodesic.com (Charles Fiterman) (1995-02-14) |
Re: Q: Intermediate code for interpreting & compiling? danhicks@aol.com (1995-02-22) |
Re: Q: Intermediate code for interpreting & compiling? Dave@occl-cam.demon.co.uk (Dave Lloyd) (1995-02-24) |
Re: Q: Intermediate code for interpreting & compiling? zmola@cicero.spc.uchicago.edu (1995-02-24) |
Re: Q: Intermediate code for interpreting & compiling? davidm@Rational.COM (1995-02-28) |
Re: Q: Intermediate code for interpreting & compiling? anton@mips.complang.tuwien.ac.at (1995-03-01) |
Newsgroups: | comp.compilers |
From: | zmola@cicero.spc.uchicago.edu (Carl Zmola) |
Keywords: | interpreter, code |
Organization: | Compilers Central |
References: | 95-02-103 95-02-170 |
Date: | Fri, 24 Feb 1995 19:45:43 GMT |
>I am programming a language that will act much like smalltalk,
>namely, that it will be incrementally compiled into some form of
>intermediate code that will later be compiled OR interpreted.
>[so what should I use for an intermediate language?]
If you want to get it up and going fast, I would suggest using a subset
of an existing language. For the stack based system you could use Forth
( now that there is an ANS standard, it should be quite portable) and for
a lisp like notation I would use Scheme or a subset of Scheme.
While I like forth, scheme might be a better choice since there is a lot of
literature on how to optimize it. If you want a typed notation, you could
use ml, but I don't know of any truely small implementations.
By choosing an existing language, you can work more on your front end, and
then if you wish, optimize the code generator/interpreter, or wait for
some one to do it for you.
--
Carl
zmola@cicero.spc.uchicago.edu
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.