Date: Mon, 26 Apr 1999 11:14:41 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: DJ Delorie <dj AT delorie DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: fsext patches for dup and dup2
In-Reply-To: <199904251638.MAA09874@envy.delorie.com>
Message-ID: <Pine.SUN.3.91.990426111422.15084B-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Sun, 25 Apr 1999, DJ Delorie wrote:

> 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.

Sorry, I'm slow today ;-)  Why won't this work for fsext handles?
Because DOS handle inheritance doesn't know about fsext?  Or are there
any other reasons?

If the inheritance is the only problem, shouldn't we expect that the
fsext does The Right Thing (like opening a real handle to a real file
or device and returning it, possibly after calling the real dup2)?