Message-ID: <3A293B7A.CD576D53@softhome.net>
Date: Sat, 02 Dec 2000 19:12:10 +0100
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: Mozilla 4.76 [en] (Win98; U)
X-Accept-Language: lt,en
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: djgpp-workers AT delorie DOT com
Subject: Re: Patch: make GCC & DJGPP headers compatible
References: <3A290D90 DOT C424D8F4 AT softhome DOT net> <4634-Sat02Dec2000185639+0200-eliz AT is DOT elta DOT co DOT il>
Content-Type: text/plain; charset=iso-8859-4
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> > The major obstacle about header compatibility has vanished - we
> > can be sure that GCC headers define size_t etc. in the right way.
> 
> What/who exactly made this miracle possible?

It was here all the time - but nobody told us to RTFM. At 
very cores of GCC headers, those typedefs look like

typedef __SIZE_TYPE__ size_t;

Now __SIZE_TYPE__ is a predefined preprocessor macro, which contents are
set for each port separately. And now djgpp.h in GCC sources has macros 
defining size_t and few other types. So GCC headers have *our*
definitions, after all. That's the point.

> Could you please repeat, for this old man's sake, what do these
> _SIZE_T symbols do?

Typedefs in GCC headers are surrounded by them. So this way we avoid
errors, although both typedefs now define exactly the same thing.

Laurynas