X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Recipient: djgpp AT delorie DOT com Date: Fri, 05 Jun 2015 10:00:34 +0300 From: "Eli Zaretskii (eliz AT gnu DOT org)" Subject: Re: DJGPP v2.05: some thoughts In-reply-to: X-012-Sender: halo1 AT inter DOT net DOT il To: djgpp AT delorie DOT com Message-id: <83mw0eprl9.fsf@gnu.org> References: <55673F0B DOT 1090103 AT iki DOT fi> <83twuwwshg DOT fsf AT gnu DOT org> <55675040 DOT 9030008 AT iki DOT fi> <556F6E49 DOT 8010006 AT gmx DOT de> <556FCCDF DOT 7080005 AT iki DOT fi> <83bngvr0ef DOT fsf AT gnu DOT org> <557078B1 DOT 9040004 AT iki DOT fi> <201506041613 DOT t54GDT8m014488 AT envy DOT delorie DOT com> <5570B1F7 DOT 1070509 AT iki DOT fi> Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > Date: Thu, 4 Jun 2015 23:26:57 +0300 > From: "Ozkan Sezer (sezeroz AT gmail DOT com)" > > > --- errno.h.orig 2015-06-04 23:12:46.745892048 +0300 > > +++ errno.h 2015-06-04 23:13:13.382210708 +0300 > > @@ -25,7 +25,7 @@ > > > > #endif /* (__STDC_VERSION__ >= 199901L) || !__STRICT_ANSI__ */ > > > > -#ifndef __STRICT_ANSI__ > > +#if !defined(__STRICT_ANSI__) || defined(__cplusplus) > > > > #define E2BIG 3 > > #define EACCES 4 > > > > Do we really have to confine those errnos to !__STRICT_ANSI__ ? We want to _exclude_ them when __STRICT_ANSI__ is defined, since that definition means the library should keep the namespace free of symbols that the standard does not define. The reason is to let applications use those symbols in ways that are incompatible with their non-standard usage.