Date: Tue, 6 Jun 2000 23:13:46 +0200
Message-Id: <200006062113.XAA01561@loewis.home.cs.tu-berlin.de>
From: "Martin v. Loewis" <martin AT loewis DOT home DOT cs DOT tu-berlin DOT de>
To: lauras AT softhome DOT net
CC: gcc AT gcc DOT gnu DOT org, djgpp-workers AT delorie DOT com
In-reply-to: <393D3934.8AB76C44@softhome.net> (message from Laurynas Biveinis
	on Tue, 06 Jun 2000 20:47:32 +0300)
Subject: Re: GCC and system headers
References:  <393D3934 DOT 8AB76C44 AT softhome DOT net>
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

> could somebody explain what are the technical reasons for
> not allowing ports to choose if they want to use standard
> headers provided by GCC? Many times I've seen on this
> mailing list that 'overriding USER_H is a brain-damaged 
> feature' without explanation *how* it is brain-damaged.

Please elaborate; I'm not aware of any prior discussion of this topic.
What exactly is user.h, and what does it have to do with ports? And
who said that they must not choose whether they want to use standard
headers?

Regards,
Martin