Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!rpi!batcomputer!cornell!calvin.spp.cornell.edu!richard
From: richard@calvin.spp.cornell.edu (Richard Brittain)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: popen()
Message-ID: <1990Mar8.191931.15274@calvin.spp.cornell.edu>
Date: 8 Mar 90 19:19:31 GMT
References: <1503@loria.crin.fr> <25F00B67.17161@maccs.dcss.mcmaster.ca> <21231@netnews.upenn.edu> <348@comcon.UUCP> <1990Mar7.002520.10365@calvin.spp.cornell.edu> <25F5D03C.5473@maccs.dcss.mcmaster.ca>
Reply-To: richard@calvin.spp.cornell.edu (Richard Brittain)
Organization: Cornell Space Plasma Physics Group
Lines: 19

In article <25F5D03C.5473@maccs.dcss.mcmaster.ca> cs4g6ag@maccs.dcss.mcmaster.ca (Stephen M. Dunn) writes:
>In article <1990Mar7.002520.10365@calvin.spp.cornell.edu> richard@calvin.spp.cornell.edu (Richard Brittain) writes:
>$...............  It is amazing how few programs check status on writes though
>$- very few report errors when the ramdisk fills up during a pipe operation.
>
>..............................  However, for pipes implemented by DOS
>by playing with the file handle for STDOUT, I thought that there was no
>way to detect that the disk was full (I could be wrong, though).  I'd
>check it in Duncan, but I'm not near my bookshelf right now.

This is what I thought at first until I wrote a test program, explicitly
checking all writes, and used it in a pipe with large files.  At least with
DOS 4.01 and 4DOS 2.2, the program does get a write error.  I used 
ferror(stdout) if it matters.

Richard Brittain,                   School of Elect. Eng.,  Upson Hall   
                                    Cornell University, Ithaca, NY 14853
ARPA: richard@calvin.spp.cornell.edu	
UUCP: {uunet,uw-beaver,rochester,cmcl2}!cornell!calvin!richard