This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC headers and DJGPP port
- To: Eli Zaretskii <eliz at is dot elta dot co dot il>
- Subject: Re: GCC headers and DJGPP port
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sun, 23 Jul 2000 09:39:13 -0600
- 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
- Reply-To: law at cygnus dot com
In message <200007231105.HAA13296@indy.delorie.com>you write:
> > From: Mike Stump <mrs@windriver.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.
No, that's a hack, plain and simple. And it fails to address the issues I
pointed out in my previous messages.
jeff