Date:	Tue, 29 Feb 2000 11:12:09 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Ken Yap <ken_yap AT my-deja DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: why isn't the FSEXT hook implemented for dup in 2.03?
In-Reply-To:	<POOIBIBBAEMGBCAA@my-deja.com>
Message-ID:	<Pine.SUN.3.91.1000229111129.22619M@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	dj-admin AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 28 Feb 2000, Ken Yap wrote:

> Is there a good reason why DJGPP will call a FSEXT read or write but
> not a dup?

IMHO, there are several possible uses of a dup hook in an FSEXT, and
it is not quite clear to me how they could be reconciled (I'm not
saying it's impossible, I'm saying it's not clear).

We need to figure out how to do that because dup is used inside FSEXT,
and because typically a hook for dup will want to do something *after*
the normal dup returns a new handle.  So you cannot simply call the
hook and forget about it.  How to do this correctly, depends on the
typical uses, which is why we need to figure this out.

Feel free to suggest an implementation.  Be sure to read the related
discussion on djgpp-workers several months ago, where Mark Elbrecht
sent some patches to implement this functionality.  IIRC, we never
finished discussing that.

- Raw text -