From:	Alain Magloire <alainm AT rcsm DOT ece DOT mcgill DOT ca>
Message-Id:	<199907090448.AAA06854@mccoy2.ECE.McGill.CA>
Subject:	Re: Request: S_IFSOCK & S_ISSOCK in sys/stat.h
To:	djgpp-workers AT delorie DOT com
Date:	Fri, 9 Jul 1999 00:48:30 -0400 (EDT)
In-Reply-To:	<Pine.SUN.3.91.990708095131.21287H-100000@is> from "Eli Zaretskii" at Jul 8, 99 09:51:54 am
X-Mailer:	ELM [version 2.4 PL25]
MIME-Version:	1.0
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

Bonjour M. Eli Zaretskii

> On Wed, 7 Jul 1999, Alain Magloire wrote:
> 
> > So programmers
> > usually use fstat(socketfd, &buf_stat) and passing the result of
> > st_mode from the struct stat to S_ISSOCK().
> 
> 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.

[...]

Richard will have a better understanding, but your reasonning
seems right. Thanks for the clarifications.

> 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...
> 

[ laughs ] 8-)
In my professional and free software work, I have never met a single
date or deadline as predicated.
Hmm that's not really true, I did a couple of times under heavy
maketting/managers pressure.. bitter taste.

My, devaluated canadian, 0.02$, you(and all) are doing allright.
So take a virtual beer for the fine work done, this time
you can put it on my tab.

Cheers !


-- 
au revoir, alain
----
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!

- Raw text -