🚀 go-pugleaf

In article <18757@cornell.UUCP> blandy@cs.cornell.edu (Jim Blandy) writes:
|I thought one of the main purposes of ARexx was to provide a command
|language that ANY application could use.  For example:  right now,
|DME, UEdit, and everybody else in the free world has their own little
|scripting language;  if they all had ARexx ports, you could program
|them all in ARexx;  ARexx would take care of parsing, and make the
|interpreter code shared among clients.
|
|???  Is that right ???

Yes.  That is easy for a package that already has a built-in script
language, like A-Talk III (not released yet).  Having an ATK ARexx
port allows me to use the full power of ARexx to evaluate each
and every parameter of A-Talk's script language commands.  They can
be evaluated as functions or entered interactively through ARexx
consoles.  Basically each parameter in A-Talk's script language
is now a variable that can be evaluated with an ARexx script.

The simplest thing looks like this:

....
no = some number evaluated or interactively entered
ADDRESS ATK
DIAL no
....

I have basically added the entire power of ARExx's expression
evaluation to each and every parameters of A-Talk's Script
language.  If the package does NOT provide a buil-in script 
language, one has to be created.  Microfiche Filer did just
that.

-- Marco Papa 'Doc'
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
uucp:...!pollux!papa       BIX:papa       ARPAnet:pollux!papa@oberon.usc.edu
 "There's Alpha, Beta, Gamma and Diga!" -- Leo Schwab [quoting Rick Unland]
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=