Date:	Tue, 10 Jul 2001 22:23:30 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	lauras AT softhome DOT net
Message-Id:	<1438-Tue10Jul2001222330+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<20010710181253.A472@lauras.lt>
Subject:	Re: Comments on GCC 3.0 distribution
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010708110538 DOT 24414F-100000 AT is> <20010710181253 DOT A472 AT lauras DOT lt>
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

> From: "Laurynas Biveinis" <lauras AT softhome DOT net>
> Date: Tue, 10 Jul 2001 18:12:53 +0200
> 
> Does our limits.h have non-standard symbols, so that's the problem?

Yes, we have lots of Posix _POSIX_* constants, and quite a few others.
I'm afraid that without out limits.h being included by the one which
comes with GCC, some programs which need those constants might not
compile.

> > Our stddef.h includes sys/djtypes.h, which could mean it defines more
> > types than stddef.h which comes with GCC (but I didn't actually
> > compare them type by type, partially because the GCC version of that
> > header is a terrible hodgepodge of ifdef's).
> 
> I don't understand. If stddef.h includes sys/djtypes.h but references
> only few particular types found in GCC's stddef.h, then where's the problem?

The problem is, again, with any program which compiled with our
stddef.h because it used some data type defined by sys/djtypes.h.  It
could fail to compile with GCC's stddef.h.

- Raw text -