From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Sun, 25 Mar 2001 15:55:06 -0500
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: new pipe patch
Message-ID: <3ABE14DA.13338.10FF953@localhost>
In-reply-to: <2950-Sun25Mar2001211957+0200-eliz@is.elta.co.il>
References: <3ABDF323 DOT 25456 DOT 8C414B AT localhost> (snowball3 AT bigfoot DOT com)
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> I'm not sure; what does the Posix standard say about these
> descriptors?  Is it possible to fseek the FILE object returned by
> popen?

Here's what the Austin draft says about popen:
The popen( ) function shall execute the command specified by the string 
command. It creates a pipe between the calling program and the executed 
command, and returns a pointer to a stream that can be used to either read 
from or write to the pipe.

My interpreation of the paragraph is that seeks aren't allowed just like with 
its unbuffered cousin pipe().

Mark