X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
From: =?windows-1252?Q?Hans-Bernhard_Br=F6ker?= <HBBroeker AT t-online DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: DJGPP v2.05: some thoughts
Date: Sat, 06 Jun 2015 17:14:07 +0200
Lines: 18
Message-ID: <ctgh1rFhv2nU1@mid.dfncis.de>
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> <mks4nl$1o8$1 AT speranza DOT aioe DOT org> <834mmmp7f0 DOT fsf AT gnu DOT org> <cte6sgFak6U1 AT mid DOT dfncis DOT de> <83y4jynfkj DOT fsf AT gnu DOT org> <mku86p$vaq$1 AT speranza DOT aioe DOT org>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
X-Trace: news.dfncis.de wxe+fI8wCDjhGRUYGFQgngtQJ9wA+395fn52TNoMRQutARQq95zOmK/l4y
Cancel-Lock: sha1:cUt9TtVYK0XoRu4tJxYMr4u97iU=
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
In-Reply-To: <mku86p$vaq$1@speranza.aioe.org>
Bytes: 2129
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
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

Am 06.06.2015 um 09:41 schrieb Martin Str|mberg:
> "Eli Zaretskii (eliz AT gnu DOT org)" <djgpp AT delorie DOT com> wrote:
>>> From: Hans-Bernhard Bröker <HBBroeker AT t-online DOT de>
>>> Date: Fri, 05 Jun 2015 20:08:19 +0200
>>> 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.

> Eeerm... I'm confused, DJGPP _is_ the implementation (of C) IMO.

It is not _the_ implementation, it is _one_ implementation.  And it's an 
implementation of about two existing versions of the standard, but not 
all future ones included.

As such, not all future library directions are allowed to be exploited 
by DJGPP, just like that, particularly not in strict compatibility mode.