Date: Mon, 24 Jul 2000 01:48:43 -0400 (EDT)
Message-Id: <200007240548.BAA14208@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: law AT cygnus DOT com
CC: mrs AT windriver DOT com, 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: <12279.964366753@upchuck> (message from Jeffrey A Law on Sun, 23
	Jul 2000 09:39:13 -0600)
Subject: Re: GCC headers and DJGPP port
References:  <12279 DOT 964366753 AT upchuck>
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.
>   >
>   > 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.
> No, that's a hack, plain and simple.

I believe it's no more hackyish than --disable-nls or --without-x.