Date: Fri, 21 Jul 2000 17:30:51 +0200
Message-Id: <200007211530.RAA01907@loewis.home.cs.tu-berlin.de>
From: "Martin v. Loewis" <martin AT loewis DOT home DOT cs DOT tu-berlin DOT de>
To: eliz AT is DOT elta DOT co DOT il
CC: lauras AT softhome DOT net, mrs AT windriver DOT com, gcc AT gcc DOT gnu DOT org,
        djgpp-workers AT delorie DOT com
In-reply-to: <200007210749.DAA10672@indy.delorie.com> (message from Eli
	Zaretskii on Fri, 21 Jul 2000 03:49:43 -0400 (EDT))
Subject: Re: GCC headers and DJGPP port
References: <200007180918 DOT FAA06988 AT indy DOT delorie DOT com> <200007181913 DOT VAA01170 AT loewis DOT home DOT cs DOT tu-berlin DOT de> <200007191826 DOT OAA08693 AT indy DOT delorie DOT com> <200007200729 DOT JAA01060 AT loewis DOT home DOT cs DOT tu-berlin DOT de> <200007201024 DOT GAA09536 AT indy DOT delorie DOT com> <200007201205 DOT OAA15361 AT loewis DOT home DOT cs DOT tu-berlin DOT de> <200007210749 DOT DAA10672 AT indy DOT delorie DOT com>
User-Agent: SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) Emacs/20.4 (i586-pc-linux-gnu) MULE/4.0 (HANANOEN)
MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko")
Content-Type: text/plain; charset=US-ASCII
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

> For example, the headers installed by GCC use various macros to avoid
> redefinitions and multiple typedefs.  Using these headers means that
> the library developers need to know about all of these special macros,
> lest some change in the library breaks them.  Likewise, the GCC port
> maintainers need to know about all the subtleties of the library
> internals, to prevent changes in GCC headers from breaking the
> library.

There is a technical need that the compiler proper and its header
files agree on certain things, so there will be some overlap. It's not
the overlap that hurts, but the fact that there is disagreement what
each header must provide and what it must not provide. If we can agree
on an interface, danger of breaking things between releases will be
smaller.

Regards,
Martin