Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!sun-barr!lll-winken!unixhub!shelby!agate!violet.berkeley.edu!pete
From: pete@violet.berkeley.edu (Pete Goodeve)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Message-ID: <1990Nov8.085522.25068@agate.berkeley.edu>
Date: 8 Nov 90 08:55:22 GMT
References: <53407.657565922@atronx.UUCP> <1990Nov3.073201.8227@agate.berkeley.edu> <15682@cbmvax.commodore.com>
Sender: usenet@agate.berkeley.edu (USENET Administrator)
Organization: University of California, Berkeley
Lines: 23


In  <15682@cbmvax.commodore.com> (7 Nov),
Dave Haynie (daveh@cbmvax.commodore.com) writes:
> In article <1990Nov3.073201.8227@agate.berkeley.edu> pete@violet.berkeley.edu (Pete Goodeve) writes:
>
|>     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.
>
Yeah, fer shure.  In my zeal for generality, I made things more complicated
than I need have.  The moment I posted it I realized that I should have
used hex.

The important point though is that, even if you do use the full ID, it is
STILL only an "initial stab".  A single parent process may want to open
several pipes, and will have to generate a new name for each.  As Process
structures are necessarily spaced fairly well apart, the simplest scheme
is probably to start with the address, increment it by 1 for each new pipe,
and generate the hex string from that.

                                            -- Pete --