Article View: comp.sys.amiga.tech
Article #14163Re: TCL questions
From: Peter da Silva
Date: Sat, 10 Mar 1990 13:36
Date: Sat, 10 Mar 1990 13:36
48 lines
2870 bytes
2870 bytes
In article <1585@jimi.cs.unlv.edu> maniac@cleanhead.cs.unlv.edu (Eric J. Schwertfeger) writes:
> I have a few questions to ask about TCL, and a few possibly
> invalid observations to make. First of all, is there any way to get
> a copy of the paper that describes TCL? I'd like to see it to get
> a better idea of what it is cabable of.
It's in the package at "sprite.berkeley.edu:ftp/tcl.tar.Z". The only problem
is that when I got it through BITFTP it got messed up somewhere around that
part of the tarchive. If you get a good copy of the file "usenet.ps", perhaps
you could post it to alt.sources.
The rest of the documentation (what I could get) I recently posted to
alt.sources, along with the System V version of TCL.
> Second, it is my impression that programs with TCL interfaces
> talk directly to each other, rather than through an intermediate, as with
> ARexx. While this is good as far as speed goes, I do see one limitation
> to this. I'm currently working on a mini-database with an ARexx interface,
> and my script interpreter will pass any unknown functions to ARexx, much
> like DME does. Now, I don't have to know which host or library defined
> the function, so long as the library or host has been identified to ARexx
> as such. Can this be done with TCL?
Not currently. Of course you can always pass it through a TCL/REXX gateway.
We're working on a resource manager for TCL that may serve the same purpose.
In fact a bare TCL interpreter can serve the purpose, now that I think of it:
send resource-manager proc whatever {args} [concat send $myname {$args}]
So you can now send undefined commands to resource-manager. Or just leave the
script interpreter out of your program altogether and let the user put this
together.
> Finally, I don't see why somebody couldn't write a set of
> library functions to implement a command interpreter similar to that
> of TCL.
Sure. That's exactly what TCL is. A set of library functions that implements
a command interpreter similar to (in fact identical to) that of TCL. Why do
it again?
> I am interested in TCL, but for now I think I'll stick with ARexx.
--
_--_|\ 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?" `-_-'
Technical Details
Message-ID:
<5373@sugar.hackercorp.com>Path:
arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!wuarchive!texbell!sugar!peterReferences:
<1778@crash.cts.com> <1585@jimi.cs.unlv.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!attcan!uunet!munnari.oz.au!uhccux!ames!uakari.primate.wisc.edu!brutus.cs.uiuc.edu!wuarchive!texbell!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: TCL questions Keywords: TCL AREXX Message-ID: <5373@sugar.hackercorp.com> Date: 10 Mar 90 13:36:25 GMT References: <1778@crash.cts.com> <1585@jimi.cs.unlv.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 48