Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!ctrsol!lll-winken!ubvax!ardent!peck!rap
From: rap@peck.ardent.com (Rob Peck)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Dealing with multiple scripting languages (was: Elinating the 'rx' from AREXX)
Message-ID: <8043@ardent.UUCP>
Date: 31 Aug 89 16:47:12 GMT
References: <721@lpami.wimsey.bc.ca> <1989Aug29.031707.9022@agate.uucp> <7782@cbmvax.UUCP> <1989Aug31.004647.12718@agate.uucp>
Reply-To: rap@peck.ardent.com (Rob Peck)
Organization: Ardent Computer Corp., Sunnyvale, CA
Lines: 22

In article <1989Aug31.004647.12718@agate.uucp> mwm@eris.berkeley.edu (Mike (I'll think of something yet) Meyer) writes:
>Did anyone consider the advisability of using a character that has
>different graphics representations in different countries (#) as one
>of the magic characters?
> ...
> ...
>I assumes this code is going into Execute(), as it needs to read the
>first part of the binary in any case. That is the case, isn't it? It's
>not going into the shell, is it?
>
I would certainly hope that some of this special code would go into the
Shell as well as into Execute() ... I would certainly like to have the
basic environment do as WShell does now, meaning "if the command name
is not in the search path, is it in the REXX: directory with an appended
.rexx at the end... in that case I have to "rx" it.

It's in there?????  Or, as Mike says, does everyone still have to buy
WShell to get this capability.  Good for Bill Hawes, but seems to defeat
the purpose of building in AREXX if the Amiga Shell (and Execute) cannot
be made to recognize AREXX scripts and execute-scripts interchangeably. 

Rob Peck