Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!cbmvax!daveh
From: daveh@cbmvax.commodore.com (Dave Haynie)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Message-ID: <15682@cbmvax.commodore.com>
Date: 7 Nov 90 19:12:03 GMT
References: <53407.657565922@atronx.UUCP> <1990Nov3.073201.8227@agate.berkeley.edu>
Reply-To: daveh@cbmvax.commodore.com (Dave Haynie)
Organization: Commodore, West Chester, PA
Lines: 33

In article <1990Nov3.073201.8227@agate.berkeley.edu> pete@violet.berkeley.edu (Pete Goodeve) writes:

>In  <53407.657565922@atronx.UUCP>, Russell McOrmond (rwm@atronx.UUCP) writes:
>> In a message posted on 2 Nov 90 09:15:42 GMT,
>> pete@violet.berkeley.edu (Pete Goodeve) wrote:

>    Make an initial stab at a name, perhaps using the middle bits
>    of the current process address as a basis -- getting 'P!4283' say.

Your whole process address, in hex, fits quite easily in a file name, with
many more characters left over for additional stuff.

>> PG>make the Shell suitably smart -- AND design a suitable syntax. (Avoid "|"
>> PG>please!)

>> What's wrong with that notation?

>Just that the "|" character is significant in AmigaDos pattern matching.
>I'm not quite sure how you'd be certain of distinguishing its use there from
>a pipe request.

WShell handles this situation quite easily.  If there is whitespace around
the "|" character, and it's not quoted, it's a pipe, otherwise it's a file
pattern character.  I use this alot, and have never found a situation in 
which it would fail.

>                                            -- Pete --


-- 
Dave Haynie Commodore-Amiga (Amiga 3000) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: hazy     BIX: hazy
	Standing on the shoulders of giants leaves me cold	-REM