To: "Eli Zaretskii" Date: Mon, 28 Feb 2000 17:24:58 -0800 From: "Ken Yap" Message-ID: Mime-Version: 1.0 Cc: djgpp AT delorie DOT com X-Sent-Mail: off X-Mailer: MailCity Service Subject: Re: why isn't the FSEXT hook implemented for dup in 2.03? X-Sender-Ip: 210.8.224.3 Organization: My Deja Email (http://www.my-deja.com:80) Content-Type: text/plain; charset=us-ascii Content-Language: en Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com >> The problem is the WATT-32 dup needs to be called to do the right thing >> for a socket dup > >What is ``the right thing for a socket dup''? > >I'm asking because I think most (if not all) of what needs to be done >is already done by the existing functionality if you simply call dup. It just doesn't. It just does not work if WATT-32's FSEXT dup is not called. WATT-32 needs to get control to manipulate its internal data structures. Currently it increments a use count on the socket structure so that the last close will really close the socket. Gisle has said it may need to do more, but the point is DJGPP never hooks into WATT-32's dup for network sockets so WATT-32 never gets a chance to do its thing. Is there a good reason why DJGPP will call a FSEXT read or write but not a dup? --== Sent via Deja.com http://www.deja.com/ ==-- Share what you know. Learn what you don't.