From: "Mark E." <snowball3 AT bigfoot DOT com>
To: djgpp-workers AT delorie DOT com
Date: Tue, 30 May 2000 09:40:16 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: tmpfile in DJGPP
Message-ID: <39338C80.9048.8606D@localhost>
References: <39330F8E DOT 32385 DOT 4BB8B1 AT localhost>
In-reply-to: <Pine.SUN.3.91.1000530110856.905T-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.12c)
Reply-To: djgpp-workers AT delorie DOT com

> 
> On Tue, 30 May 2000, Mark E. wrote:
> 
> > I came up with a way, and I use it with Bash 2.04 to provide a function that 
> > essentially marks a file handle as 'remove-on-close'. I then use this 
> > function to implement a pipe() replacement. This all works, but it also 
> > requires changes to dup and dup2 to handle FSEXTs.
> 
> Using FSEXT is a possibility, but I'm not sure it's a good way for a 
> library feature (as opposed to an application-level code).  As discussed
> here on several opportunities, FSEXT needs some work to make it suitable 
> for internal use by libc itself.
> 

An FSEXT is just the way I chose to go implement it. If it were internal and 
integrated into libc, I wouldn't need to use an FSEXT.