Mail Archives: djgpp-workers/2000/12/02/12:12:55
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
- Raw text -