Related articles |
---|
[9 earlier articles] |
Re: Techniques for writing an interpreter dent@cs.tu-berlin.de (Pierre Mai) (1998-03-18) |
Re: Techniques for writing an interpreter markh@usai.asiainfo.com (Mark Harrison) (1998-03-20) |
Re: Techniques for writing an interpreter a010111t@bc.seflin.org (Orlando Llanes) (1998-03-20) |
Re: Techniques for writing an interpreter simon@magnorth.nildram.co.uk (Simon Chapman) (1998-03-22) |
Re: Techniques for writing an interpreter shutkoa@ugsolutions.com (alan shutko) (1998-03-24) |
Re: Techniques for writing an interpreter mikee@cetasoft.cog (1998-03-24) |
Re: Techniques for writing an interpreter nnylfv@ny.ubs.com (Olivier Lefevre) (1998-03-24) |
From: | Olivier Lefevre <nnylfv@ny.ubs.com> |
Newsgroups: | comp.compilers |
Date: | 24 Mar 1998 22:45:47 -0500 |
Organization: | Union Bank of Switzerland, New York site |
References: | 98-03-032 98-03-098 98-03-141 98-03-147 98-03-153 |
Keywords: | interpreter, APL |
Peter Su wrote:
> That said, good ext. languages have been done before, and are widely
> available. There is no reason to reinvent the wheel here.
I can't resist pointing out that APL can make a perfectly good
scripting language and that the source for, e.g., an early version
of J, is available.
-- O.L.
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.