Sender: richdawe AT bigfoot DOT com
Message-ID: <36ED932F.A7F21B8E@meridian22.net>
Date: Mon, 15 Mar 1999 23:09:35 +0000
From: Richard Dawe <richdawe AT bigfoot DOT com>
X-Mailer: Mozilla 4.08 [en] (X11; I; Linux 2.2.1 i586)
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: diffs for socket error codes and messages
References: <199903151815 DOT NAA06375 AT mccoy2 DOT ECE DOT McGill DOT CA>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Alain Magloire wrote:
> I tend to agree with you to keep most of libsocket separated
> but it would probably make it easier for Richard D. to have some
> hooks in the C lib.

	To be honest, I don't mind too much. libsocket comes with a libc patch that
adds the error codes. Given the fact that libsocket doesn't work under DOS, it
is probably best that libsocket isn't integrated into DJGPP.

	After I asked what people thought about integrating libsocket into DJGPP, I
got the impression that it would be OK. Maybe I'm just confused.

	BTW are error codes like ENOBUFS really networking-only errors? I've found
several occasions on which I wanted to use this error in my code in a
non-networking context. Is this wrong?