On 2005-05-16, Tom Payne <[EMAIL PROTECTED]> wrote:
> gcc is being very strict, but correct. -pedantic-errors makes it throw an
> error instead of just a warning in this case.
Then remove that parameter.
The use of void* in that particular case can be tracked all the way down to
dlsym(), btw, so such a recent gcc can't be used to compile any code that
uses it with warnings on... seems like a very stupid thing to complain
of when it is standard to use void* for arbitrary pointers.
> There are a few little historic artifacts in C, and some weird
> architectures. On some systems a byte is not 8 bits, and NULL != (void*)0
> (i.e. code like x=malloc(...); if(!x) { ... } breaks).
Actually, IIRC if(!x) is quaranteed to work, while if(x!=(void*)0)
is not.
--
Tuomo
