Message-ID:	<39420DBD.BC932134@softhome.net>
Date:	Sat, 10 Jun 2000 12:43:25 +0300
From:	Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer:	Mozilla 4.72 [en] (Win98; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	djgpp-workers AT delorie DOT com
Subject:	Re: [Fwd: Re: GCC and system headers]
References:	<393E4161 DOT 50C3D500 AT softhome DOT net>
Reply-To:	djgpp-workers AT delorie DOT com

From: Marc Espie <espie AT quatramaran DOT ens DOT fr>
> It's standard policy from the gcc development team. Using USER_H means
> not using gcc headers, and overriding them with the system headers.
[snip]
> I would say that it's unlikely either camp is going to budge, since both
> are utterly convinced they're doing the right thing.

This is more political than technical issue. So it is even harder to
make gcc maintainers change their minds. I think we won't get more replies
from them, unless Jeff Law won't skip my mail when he returns.

I think I will make a patch for DJGPP which replaces __dj_include_foo_h_
sentinels with _ANSI_FOO_H_ and will change
__DJ_foo_t
#undef __DJ_foo_t
#define __DJ_foo_t

to

#ifndef _FOO_T_DEFINED_
__DJ_foo_t
#define _FOO_T_DEFINED_
#endif

I suggest leaving politics aside for a while and fix technical
issues at first.

Laurynas

- Raw text -