Date: Sun, 25 Apr 1999 12:38:04 -0400
Message-Id: <199904251638.MAA09874@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.990425190529.7199G-100000@is> (message from Eli
	Zaretskii on Sun, 25 Apr 1999 19:09:59 +0300 (IDT))
Subject: Re: fsext patches for dup and dup2
References:  <Pine DOT SUN DOT 3 DOT 91 DOT 990425190529 DOT 7199G-100000 AT is>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> DJ, do you remember the difficulties that we bumped upon when
> discussing this?  I guess searching the mail archives of
> djgpp-workers

There is an fsext function specifically for allocating a dos handle.
It used to open nul, but now it dups a previously opened nul.  I don't
recall any other problems with dup and dup2.  There was a bit of
discussion about a fsext-specific "copy this file to that" function,
of which I disapprove for technical reasons.

The only problem I can think of off-hand is that dup/dup2 are usually
used just before running a child program, to set up stdin/stdout, and
that just won't work for fsext handles.