This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Warning for unadorned 0 in varargs lists?
"Kaveh R. Ghazi" <ghazi@unknown> writes:
> GCC's copy of stddef.h always defines NULL to (void*)0 in C and to
> __null in g++. In each C dialect, we would accept the respective
> value. We would warn about unadorned zero.
Are there really any targets where passing an unadorned zero doesn't
work? If there aren't, it seems somewhat inconsistent not to warn
about NULL, which is just as unportable as 0 here.
--
Falk