Date: Sun, 23 Jul 2000 07:05:59 -0400 (EDT)
Message-Id: <200007231105.HAA13296@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: mrs AT windriver DOT com
CC: zack AT wolery DOT cumb DOT org, djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org,
        martin AT loewis DOT home DOT cs DOT tu-berlin DOT de
In-reply-to: <200007230023.RAA01633@kankakee.wrs.com> (message from Mike Stump
	on Sat, 22 Jul 2000 17:23:25 -0700 (PDT))
Subject: Re: GCC headers and DJGPP port
References:  <200007230023 DOT RAA01633 AT kankakee DOT wrs DOT com>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: Mike Stump <mrs AT windriver DOT com>
> Date: Sat, 22 Jul 2000 17:23:25 -0700 (PDT)
> 
> > A similar argument can be made for assert.h, stddef.h, and possibly
> > float.h, but these headers do not cause nearly as much trouble as
> > limits.h.  Limits.h must die.
> 
> If we do this, we should do them all enmass, and then be willing to
> seek out and test on lots of platforms to make sure we don't introduce
> new bugs.

Such a change doesn't have to affect all platforms, and doesn't need
to happen in one go.  It could be conditioned on some sommand-line
option to `configure', or be the default on only some platforms, at
least initially.