Mail Archives: djgpp-workers/2001/07/11/11:38:46
> From: "Laurynas Biveinis" <lauras AT softhome DOT net>
> Date: Wed, 11 Jul 2001 16:36:16 +0200
>
> > Yes, we have lots of Posix _POSIX_* constants, and quite a few others.
> > I'm afraid that without out limits.h being included by the one which
> > comes with GCC, some programs which need those constants might not
> > compile.
>
> Another poor answer, but in this case it would be ``too bad to be true'' -
> too many broken platforms.
Sorry, I don't understand this. What platforms did you have in mind?
> > The problem is, again, with any program which compiled with our
> > stddef.h because it used some data type defined by sys/djtypes.h. It
> > could fail to compile with GCC's stddef.h.
>
> You mean that code like
> #include <stddef.h>
> __dj_blah_t
>
> will stop working?
No, I don't expect any application code to use private defines like
those; they are forbidden from doing that by ANSI.
But look at wchar.h, for example:
#include <stddef.h>
__DJ_wint_t
#undef __DJ_wint_t
#define __DJ_wint_t
This won't work if stddef.h doesn't include sys/djtypes.h. Observe:
#include <wchar.h>
int main (void)
{
return 0;
}
gcc -c twc.c
In file included from twc.c:1:
wchar.h:24: syntax error before "typedef"
(The current CVS version of wchar.h doesn't have that problem, but I'm
thinking about users who install GCC 3.0 now, with stock
djdev203.zip.)
There might be other problems like that, I didn't check.
- Raw text -