Related articles |
---|
[7 earlier articles] |
Scripting Languages (was Re: Techniques for writing an interpreter) creedy@mitretek.org (Chris Reedy) (1998-03-24) |
Re: Scripting Languages (was Re: Techniques for writing an interpreter markh@usai.asiainfo.com (Mark Harrison) (1998-03-30) |
Re: Scripting Languages (was Re: Techniques for writing an interpreter tiggr@ics.ele.tue.nl (1998-03-30) |
Scripting Languages (was Re: Techniques for writing an interpreter) jhonan@mpx.com.au (1998-03-30) |
Re: Scripting Languages (was Re: Techniques for writing an interpreter hgg9140@heckle.ca.boeing.com (1998-03-30) |
Re: Scripting Languages (was Re: Techniques for writing an interpreter bmcsweeney@bigfoot.com (1998-03-30) |
Re: Scripting Languages (was Re: Techniques for writing an interpreter cgregg@dsp.sps.mot.com (Chris Gregg) (1998-03-30) |
From: | Chris Gregg <cgregg@dsp.sps.mot.com> |
Newsgroups: | comp.compilers |
Date: | 30 Mar 1998 21:42:54 -0500 |
Organization: | Motorola, Inc. Austin, TX |
References: | 98-03-032 98-03-098 98-03-141 98-03-147 98-03-159 98-03-186 98-03-201 98-03-233 |
Keywords: | interpreter |
Our moderator wrote:
> it right away. But I realize that people have put together fairly
> large applications in TCL, even though TCL doesn't offer the name
> spaces and data structuring that you'd usually want for a large
> program. -John]
Fear of getting to far away from compilers, but...
TCL actually does provide namespaces as of 8.0. Data structuring
on the other hand isn't very well supported, though it is possible.
(ObCompiler reference) And TCL's new bytecode compiler does make it
run considerably faster.
Regards,
--
| Chris Gregg cgregg@dsp.sps.mot.com |
| Motorola Wireless Development Tools |
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.