From: Kbwms AT aol DOT com
Message-ID: <f55af92.36c6ea6b@aol.com>
Date: Sun, 14 Feb 1999 10:23:23 EST
To: eliz AT is DOT elta DOT co DOT il
Cc: djgpp-workers AT delorie DOT com
Mime-Version: 1.0
Subject: Re: socket.h
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Mailer: AOL 3.0 16-bit for Windows sub 38
Reply-To: djgpp-workers AT delorie DOT com

Subj:	 Re: socket.h
To:	eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
CC:	djgpp-workers AT delorie DOT com

Dear Eli Zaretskii,

On 02-14-99 at 06:01:57 EST you wrote:
>
>
> On Fri, 12 Feb 1999 Kbwms AT aol DOT com wrote:
>
> > Unfortunately, my query was not all that bright.  One might
> > even say "stupid."  I'm trying to make groff from source and
> > not doing very well.
>
> If building some package (Groff) reveals a bug in another package (the
> C++ libraries and headers), then IMHO the correct solution is to fix
> the bug in the other package (and report it).
>

Good point.  The difficulties are determining 1) where the fault lies,
and 2) how to fix the fault.  How does one fix a bug that seemingly has
no observable beginning?  I, for one, am not as well equipped as you to
determine the genesis of such remote bugs.  I might get close someday;
only time, and experience with inscrutable bugs, will tell.

> No header, either C++ or otherwise, should include sys/socket.h in
> DJGPP, since sys/socket.h doesn't exist in DJGPP.

Hmmm.  Perhaps we ought to toss in a #ifdef __GNUG__ or some such in
strategic locations to ward off socket.h monsters.

K.B. Williams