Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!cbmvax!jesup
From: jesup@cbmvax.commodore.com (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Message-ID: <15706@cbmvax.commodore.com>
Date: 8 Nov 90 06:00:48 GMT
References: <53407.657565922@atronx.UUCP>
Reply-To: jesup@cbmvax.commodore.com (Randell Jesup)
Organization: Commodore, West Chester, PA
Lines: 27

In article <53407.657565922@atronx.UUCP> rwm@atronx.UUCP (Russell McOrmond) writes:
>Here's WHY you wish them to be un-named this way you KNOW that the names are
>unique:  I now do some convaluted task+timer thing to try to make sure I have
>a unique name.  With the number of times I use it, it's inevidable that the same
>name gets used twice.

	No, unique names are trivial (I used to think we should add a "unique
filename" call until this was pointed out to me:  Use the current system time
(Note: I mean CurrentTime(), not DateStamp().)  This is guaranteed to be an
increasing number and never return the same exact number.  Just convert it to
ascii and use it.

>PG>make the Shell suitably smart -- AND design a suitable syntax. (Avoid "|"
>PG>please!)
>
>What's wrong with that notation?  If you don't like that, what do YOU suggest.

	It conflicts with existing command-line usage - the | is used to
separate alternates in pattern-matching.  The problem is suddenly a script
(let's say an installation script, or a command submitted by Execute() or
System()), will suddenly do something unexpected.  That doesn't mean 3rd-
party shells can't use it for piping.

-- 
Randell Jesup, Keeper of AmigaDos, Commodore Engineering.
{uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.cbm.commodore.com  BIX: rjesup  
Common phrase heard at Amiga Devcon '89: "It's in there!"