Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!pollux.usc.edu!papa From: papa@pollux.usc.edu (Marco Papa) Newsgroups: comp.sys.amiga.tech Subject: Re: Tcl - Tool command language Message-ID: <23205@usc.edu> Date: 3 Mar 90 09:50:40 GMT References: <5213@sugar.hackercorp.com> <5231@sugar.hackercorp.com> Sender: news@usc.edu Organization: Felsina Software, Los Angeles, CA Lines: 15 In article <5231@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: >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. I just got Dr. Ousterhout's paper from Karl and I am very impressed. We are DEFINITELY going to use Tcl for "another" platform that doesn not have AREXX, but are also seriously considering incorporating Tcl into A-Talk III's script language, maintaining the current Arexx compatibility. Thoughts? -- Marco -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "Xerox sues somebody for copying?" -- David Letterman -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=