Xref: utzoo comp.lang.c:26575 comp.sys.ibm.pc.programmer:246
Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!psuvax1!psuvm!cmh117
From: CMH117@psuvm.psu.edu (Charles Hannum)
Newsgroups: comp.lang.c,comp.sys.ibm.pc.programmer
Subject: Re: popen()
Message-ID: <90063.133857CMH117@psuvm.psu.edu>
Date: 4 Mar 90 18:38:57 GMT
References: <1503@loria.crin.fr> <25F00B67.17161@maccs.dcss.mcmaster.ca>
 <21231@netnews.upenn.edu>
Organization: Penn State University
Lines: 23


In article <21231@netnews.upenn.edu>, dowding@linc.cis.upenn.edu (John Dowding)
says:
>
>If you write write the temp file to a ram disk, won't this give you
>nearly the same effect as the UNIX pipe?

Close, but *ix pipes are fixed in size.  (The size probably varies from system
to system; I don't know what it is.)  When the pipe is full, the process that
is writing to it is suspended; when it is empty, the process reading from it is
suspended.  This allows a virtually infinite amount of data to pass over the
pipe.  (Just think about "ls -R | find ..." from the root!!)  Writing to a RAM
disk (or *any* disk) under DOS limits the amount of information that can pass
over the pipe.

A side note:  A variant of *ix piping is implemented in OS/2.


Virtually,
- Charles Martin Hannum II       "Klein bottle for sale ... inquire within."
    (That's Charles to you!)     "To life immortal!"
  cmh117@psuvm.{bitnet,psu.edu}  "No noozzzz izzz netzzzsnoozzzzz..."
  c9h@psuecl.{bitnet,psu.edu}    "Mem'ry, all alone in the moonlight ..."