Date:	Thu, 24 Feb 2000 12:25:20 +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:	<890rpg$sf6$1@nnrp1.deja.com>
Message-ID:	<Pine.SUN.3.91.1000224122458.13848R-100000@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 Wed, 23 Feb 2000, Ken Yap wrote:

> I found that there is no hook from dup to FSEXT, so I can't dup network
> sockets in WATT-32. Why isn't the dup hook to FSEXT implemented yet?

Two reasons:

  - It's tricky, since FSEXT itself calls dup internally (to produce a
    valid file handle that __FSEXT_alloc_fd returns).

  - When this was discussed, it seemed to be rather unnecessary to
    hook dup.  Can you explain under what circumstances do you need
    this, and why?

- Raw text -