Path: utzoo!censor!geac!torsqnt!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucsd!ames!sun-barr!newstop!texsun!texbell!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Tcl - Tool command language
Message-ID: <5231@sugar.hackercorp.com>
Date: 2 Mar 90 12:53:54 GMT
References: <5213@sugar.hackercorp.com> <Mar.1.16.12.03.1990.15155@pilot.njin.net>
Reply-To: peter@sugar.hackercorp.com (Peter da Silva)
Organization: Sugar Land Unix - Houston
Lines: 15

In article <Mar.1.16.12.03.1990.15155@pilot.njin.net> limonce@pilot.njin.net (Tom Limoncelli) writes:
> Basically, I see it as a parser
> that programs can "plug-and-chug" to get a script language, a parser,
> and a gateway to AREXX.  If I can make it a .library, it would make
> adding an internal scripting language w/AREXX port easier for developers.

Basically, that fits in well with our view. The big problem I see with
REXX is that it needs each application to implement their own scripting
language anyway, which is an uncool duplication of effort. This fills
that gap nicely.
-- 
 _--_|\  Peter da Silva <peter@sugar.hackercorp.com>.
/      \
\_.--._/ I haven't lost my mind, it's backed up on tape somewhere!
      v  "Have you hugged your wolf today?" `-_-'