Date: Thu, 20 Jul 2000 13:15:06 +0200
Message-Id: <200007201115.NAA14806@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: mrs AT windriver DOT com, djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org
In-reply-to: <200007200644.CAA09337@indy.delorie.com> (message from Eli
	Zaretskii on Thu, 20 Jul 2000 02:44:16 -0400 (EDT))
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>
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

> In any case, the following headers out of the above list seem
> especially dangerous:
> 
>   - 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.
PLEASE identify real problems caused by the actual contents of these
files, instead of merely reporting your imagination that there could
be problems.

Regards,
Martin