Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!njin!limonce From: limonce@pilot.njin.net (Tom Limoncelli) Newsgroups: comp.sys.amiga.tech Subject: Re: Tcl - Tool command language Message-ID: Date: 4 Mar 90 05:37:36 GMT References: <5213@sugar.hackercorp.com> <5231@sugar.hackercorp.com> <48f6cbee.db93@edsel.engin.umich.edu> Organization: Drew University/NJIN Lines: 16 In article <48f6cbee.db93@edsel.engin.umich.edu> chrisl@caen.engin.umich.edu (Chris Lang) writes: > I'm not sure what that means. True, with ARexx the developer needs to write > code to handle all the commands the application can receive from an ARexx > script/program, but this hardly the same as writing an entire scripting > language, is it? How will Tcl change this...won't one still need to write ^^^^^^^^^^^^^^^^^^^^^^^^^ > the code to handle any commands it can receive? (True, you won't need to No, you tell Tcl what the token is, where the code for it's handler starts, and it does everything. -- Tom Limoncelli The computer industry should spend more time in front of tlimonce@drew.uucp their computers. Remember when "Look & Feel" tlimonce@drew.Bitnet was what you tried to do on a date? limonce@pilot.njin.net