Message-Id:	<m0yBzZT-000S2iC@inti.gov.ar>
Comments:	Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization:	INTI
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Mon, 9 Mar 1998 13:15:35 +0000
MIME-Version:	1.0
Subject:	Re: errno constants in <errno.h>
References:	<3503BEB1 DOT 6745 AT rug DOT ac DOT be>
In-reply-to:	<Pine.SUN.3.91.980309165634.26620B-100000@is>

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:

> On Mon, 9 Mar 1998, Vik Heyndrickx wrote:
> 
> > The real problem start when DOS functions are called in the libc
> > routines. DOS extended error codes are in many cases precise enough to
> > decide what EXACTLY went wrong, but the way it is current implemented (D
> > ->U translated error codes) often make loose a lot of this information.
> 
> Other DOS compilers have a global variable called `_dos_errno' or some 
> such, which just holds the value of the last DOS error returned.
> 
> How about adding this to DJGPP?

It sounds better than having an errno too different than the UNIX one. And 
perhaps (if no so much overhead is involved) we can even have both errno styles 
selectable through some variable. I mean a variable to select if we will use 
translated or not values of errno. What about that?

SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013

- Raw text -