Sender: richdawe AT bigfoot DOT com Message-ID: <3788B1F8.A5B3779D@tudor21.net> Date: Sun, 11 Jul 1999 15:02:16 +0000 From: Richard Dawe X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.10 i586) X-Accept-Language: de,fr MIME-Version: 1.0 To: djgpp-workers AT delorie DOT com Subject: Re: Request: S_IFSOCK & S_ISSOCK in sys/stat.h References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp-workers AT delorie DOT com Hello. Eli Zaretskii wrote: > Where does the handle for sockets come from? Is it created using > FSEXT? If so, the current `fstat' is okay as long as libsocket isn't > linked in, since `fstat' will never set the S_IFSOCK bits on any > handle. We only need to update `fstat' when libsocket is linked into > a program. The handle is created by libsocket's socket() call by calling libc's __FSEXT_alloc_fd(). This is the only way. So the S_IFSOCK bits will not be set. > Yes, __FSEXT_fstat was introduced in v2.02. But I don't see a problem > here, since libsocket can require v2.02 or later. I wasn't planning to add S_IFSOCK, isfdtype(), etc. support until I've finished a new stable version of libsocket & upgraded to DJGPP 2.02 (or 2.03). Estimated time: month? ;) > Anyway, the original intent was to get v2.03 out the door quickly > enough to eliminate the need for branching. Obviously, I failed in > making that happen... I think that S_IFSOCK, etc. can wait until DJGPP 2.04 goes into development. If this kind of functionality is needed _now_, people just can use libsocket's isfdtype() support. BTW when is 2.03 due to enter beta testing? Bye bye, -- --------------+----------------------+------------------------------------ Richard Dawe | richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ --------------+----------------------+------------------------------------