Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!DUCVAX.AUBURN.EDU!FVEST
From: FVEST@DUCVAX.AUBURN.EDU (Floyd Vest)
Newsgroups: comp.sys.amiga
Subject: ARP 1.3 Bug or Feature?
Message-ID: <8906160323.AA21605@ucbvax.Berkeley.EDU>
Date: 16 Jun 89 04:32:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 28


I have a script that I execute via a runback in my startup-sequence
that contains code on the order of:

     list > ram:foo #? lformat "bar %s"
     execute ram:foo
     delete ram:foo

I decided I would "clean" things up by using the ARP 1.3 form:

     list #? lformat "bar %s" | execute

It stopped working.  When I executed the script via execute, it
worked; when I executed via run it worked; when I executed via
arun >nil: <nil: it failed.

On further investigation I discovered the list/execute statement
alone, it would not be accepted by run, runback or arun.

Am I trying to do something the pipe was not meant to do, or is
this a bug?


Floyd Vest
Auburn University
FVEST@AUDUCVAX.bitnet  
{...!psuvax1!ducvax.auburn.edu!fvest} 
fvest@ducvax.auburn.edu