Sender: wgalazka AT chem DOT uw DOT edu DOT pl
Message-ID: <347E76BD.7081@chem.uw.edu.pl>
Date: Fri, 28 Nov 1997 08:46:05 +0100
From: Wojciech Galazka <wgalazka AT chem DOT uw DOT edu DOT pl>
Organization: University of Warsaw
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: errno constants in <errno.h>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

> 
> On Tue, 25 Nov 1997,Eli Zaretskii wrote:
> 
> > And the BSD docs say the following
> >
> > #define ESOCKTNOSUPPORT  44 /* Socket type not supported*/
> 
> 44 is outside the range of errno values defined by DJGPP.  You can just
> add the definition fo ESOCKTNOSUPPORT without changing the existing
> values.

I did so
> If the values that sockets use overlap and conflict with those defined in
> errno.h, I would suggest to write a wrapper around sockets calls that
> would translate the codes into DJGPP's values.

I rechecked the code and found that the 'wrapper solution' is the only
right solution. 

> But I would imagine that most errno codes relevant for sockets aren't
> defined at all by DJGPP, so you could just add them.
 
I also added some descriptive teksct to sys_errlist[] (or how it is
called)

BTW I wonder if DJGPP needs <sys/errno.h> if so what should be put
there.
Or just a dummy <sys/errno.h> file? I prefer having even dummy
(containing nothing)
header file than having to change <sys/errno.h> to <errbo.h> in a bunch
of source codes.


-- 
Wojciech Galazka
Computer Security Advisor