Related articles |
---|
run parse tree efficiently weltraum@astrocat.de (2004-01-02) |
Re: run parse tree efficiently joachim.durchholz@web.de (Joachim Durchholz) (2004-01-07) |
Re: run parse tree efficiently tmk@netvision.net.il (2004-01-07) |
Re: run parse tree efficiently Jeffrey.Kenton@comcast.net (Jeff Kenton) (2004-01-09) |
From: | Jeff Kenton <Jeffrey.Kenton@comcast.net> |
Newsgroups: | comp.compilers |
Date: | 9 Jan 2004 23:36:09 -0500 |
Organization: | Comcast Online |
References: | 04-01-018 04-01-024 |
Keywords: | interpreter |
Posted-Date: | 09 Jan 2004 23:36:09 EST |
Michael Tiomkin wrote:
> Besides the rarely used feature of evaluating a character string as
> a part of your program, there is no difference between interpreted and
> compiled languages.
You can also do this in compiled languages, as long as the compiler is part of
the run-time system. JIT compilers could do this (the XSLT language often has
an "evaluate()" extension function), as could some of the old compile-and-go
student compilers.
--
-------------------------------------------------------------------------
= Jeff Kenton Consulting and software development =
= http://home.comcast.net/~jeffrey.kenton =
-------------------------------------------------------------------------
Return to the
comp.compilers page.
Search the
comp.compilers archives again.