Message-Id: <199904260416.EAA103692@out2.ibm.net>
From: "Mark E." <snowball3 AT usa DOT net>
To: djgpp-workers AT delorie DOT com
Date: Mon, 26 Apr 1999 00:16:56 -0400
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: fsext patches for dup and dup2
References: <199904231752 DOT RAA64682 AT out5 DOT ibm DOT net>
In-reply-to: <Pine.SUN.3.91.990425190529.7199G-100000@is>
X-mailer: Pegasus Mail for Win32 (v3.01d)
Reply-To: djgpp-workers AT delorie DOT com

> 
> On Fri, 23 Apr 1999, Mark E. wrote:
> 
> I don't remember all the details after all this time (this was discussed a
> year ago!), but in general hooking dup and dup2 with and fsext could be
> mighty dangerous.  

I went through the archives searching about this subject. The first 
time was before I posted the first rev. of the patch. Now I've just 
searched the archives with the keyword 'dup2' and came up with 
this thread:
http://www.delorie.com/djgpp/mail-
archives/thread.cgi?msg=djgpp-workers/1998/01/07/14:29:55

From reading this thread, I see much of the same evolution in 
Randy's proposal as in mine. From DJ's comments in the thread, I 
would expect that code to have been in djdev 202. Perhaps some 
more searching will turn up why it didn't happen.