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 22:03:08 +0300 From: "Eli Zaretskii (eliz AT gnu DOT org)" Subject: Re: DJGPP v2.05: some thoughts In-reply-to: To: djgpp AT delorie DOT com Message-id: <83y4jynfkj.fsf@gnu.org> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-15 X-012-Sender: halo1 AT inter DOT net DOT il 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 delorie DOT com> <5570B1F7 DOT 1070509 AT iki DOT fi> <83pp5aprqw DOT fsf AT gnu DOT org> <834mmmp7f0 DOT fsf AT gnu DOT org> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by delorie.com id t55J3GB2021936 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 > From: Hans-Bernhard Bröker > Date: Fri, 05 Jun 2015 20:08:19 +0200 > > Am 05.06.2015 um 16:16 schrieb Eli Zaretskii (eliz AT gnu DOT org): > >> From: Martin Str|mberg > >> Date: Fri, 5 Jun 2015 12:29:43 +0000 (UTC) > >> > >> But, IIRC, C99 (or even perhaps C89) reserved any symbol starting with E. > > > > Where do you see such language in C99? I don't see it, and neither do > > I see it in C11. But maybe I'm missing something, it's not like I've > > read the entire document top to bottom. > > This passage might be read that way (C99 7.5 , paragraph 4): > > Additional macro definitions, beginning with E and a digit > or E and an uppercase letter, may also be specified by the > implementation. > > This has a footnote pointing to C99 7.26.3 ("Future library directions", > ), which reads: > > Macros that begin with E and a digit or E and an uppercase > letter may be added to the declarations in the > header. > > I.e. the standard reserves other E* macros for itself, to be used in > future versions. AIUI, that doesn't actually reserve them for use by > DJGPP, though. Indeed, it doesn't, IMO. I think we should stick to the old practice of not defining non-standard values when strict standard compliance was requested by the compiler switches.