Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!netnews.upenn.edu!grad1.cis.upenn.edu!ranjit
From: ranjit@grad1.cis.upenn.edu (Ranjit Bhatnagar)
Newsgroups: comp.sys.amiga.tech
Subject: Re: links - forget UNIX; what about AMIGA?
Message-ID: <14382@netnews.upenn.edu>
Date: 14 Sep 89 02:46:05 GMT
References: <14187@netnews.upenn.edu> <1410031@hpcvca.CV.HP.COM> <1989Sep13.022711.7311@agate.berkeley.edu> <1251@quintus.UUCP>
Sender: news@netnews.upenn.edu
Reply-To: ranjit@grad1.cis.upenn.edu.UUCP (Ranjit Bhatnagar)
Organization: University of Pennsylvania
Lines: 25

In article <1251@quintus.UUCP> pds@quintus.UUCP (Peter Schachte) writes:
>It would be great if all this could be done with just an AREXX: device,
>with scripts that invoke compress or zoo, but I don't see how the AREXX:
>device would tell the script it started whether it wanted to read,
>write, examine, exnext, delete a file, or whatever.  But then, I don't
>know AREXX.  Is this possible?

Two possibilities (there are probably other better ideas that I didn't
think of):

1- if you open AREXX: for writing, then the script gets your process as
	standard input.  If you open it for reading, it gets you as
	standard output.  If you do file functions like examine, delete,
	etc., you get OPERATION NOT SUPPORTED, just like if you tried
	to do it do SER: or PRT:.

2- the AREXX: handler creates a logical file for input or output
	before invoking the script, and the script can choose to use
	the AREXX: files or the ordinary input/output.
		
		call open rxinput "pipe:rx001742" "read"

	
"Trespassers w"   ranjit@eniac.seas.upenn.edu	mailrus!eecae!netnews!eniac!...
	   "Such a brute that even his shadow breaks things." (Lorca)