Date: Fri, 21 Jul 2000 03:48:45 -0400 (EDT)
Message-Id: <200007210748.DAA10668@indy.delorie.com>
From: Eli Zaretskii <eliz AT delorie DOT com>
To: martin AT loewis DOT home DOT cs DOT tu-berlin DOT de
CC: mrs AT windriver DOT com, djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org
In-reply-to: <200007201115.NAA14806@loewis.home.cs.tu-berlin.de>
	(martin AT loewis DOT home DOT cs DOT tu-berlin DOT de)
Subject: Re: GCC headers and DJGPP port
References: <200007192144 DOT OAA01294 AT kankakee DOT wrs DOT com> <200007200644 DOT CAA09337 AT indy DOT delorie DOT com> <200007201115 DOT NAA14806 AT loewis DOT home DOT cs DOT tu-berlin DOT de>
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

> Date: Thu, 20 Jul 2000 13:15:06 +0200
> From: "Martin v. Loewis" <martin AT loewis DOT home DOT cs DOT tu-berlin DOT de>
> 
> >   - errno.h
> >   - limits.h
> >   - assert.h
> >   - math.h
> >   - stddef.h
> > 
> > These all include definitions and declarations that are intimately
> > related to the libc internals.
> 
> I still can't understand why you feel threatened by a file name.

Not by a file name, by its contents.

> PLEASE identify real problems caused by the actual contents of these
> files, instead of merely reporting your imagination that there could
> be problems.

Some of the definitions on these headers are private to the library.
For example, math.h defines HUGE_VAL to a runtime constant
__dj_huge_val.  limits.h defines several constants such as
_POSIX_PATH_MAX that are specific to the library implementation.
These are just a few examples.

Of course, with suitable #ifdef'ing, it's possible to prevent each
conflict as it happens.  But we would like to avoid the need for this
additional maintenance effort where we can.  DJGPP is maintained by a
small group of volunteers; we cannot afford frequent releases.  So
we must try to minimize the problems in released versions, including
problems that can happen when a new version of GCC is released which
wasn't available at the time the library was developed and tested.