Date: Wed, 7 Jul 1999 15:30:36 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Richard Dawe cc: djgpp-workers AT delorie DOT com Subject: Re: Request: S_IFSOCK & S_ISSOCK in sys/stat.h In-Reply-To: <378249B5.89204688@tudor21.net> Message-ID: 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 Tue, 6 Jul 1999, Richard Dawe wrote: > libsocket is not near that goal yet. No code exists to support S_IFSOCK or > S_ISSOCK(). I hope to add stat() support for sockets sometime. What does `stat' need to do with sockets? > I'm confused what you mean about 'mknode' (mknod() in > libc/compat/sys/stat/mknod.c?). I guess the example with mknod was a bad idea. I think I tried to explain it better with S_ISLNK and the symlink function. The idea is that whatever functionality that is implied by S_ISSOCK should be there, even if the functions that implement that functionality either fail or do nothing. > I agree that just #define'ing S_IFSOCK is too simplistic and will break > things (hence my concern about autoconf scripts). Alain's message seems to indicate that maybe the situation isn't as bad as I thought, because any autoconfigured package will probably test much more than just the existence of S_ISSOCK. So perhaps I should add S_ISSOCK and see if it actually breaks things during v2.03 beta. The important question is: do you think that libsocket will be ready with the necessary features in the next few months? If not, then we can wait until v2.04.