linux libio status
Jason Merrill
jason@cygnus.com
Thu Oct 16 01:51:00 GMT 1997
>>>>> Per Bothner <bothner@cygnus.com> writes:
> Currently, __null is mapped into null_node, which (when -ansi is not
> specified) is basically basically (void*)0. I missed the early
> context of this discussion, but I gather this causes some problems,
> some of which are related to overloading.
I'm not aware of any problems with __null. If anyone has any overloading
bugs involving __null, please send them in. There were certainly problems
with making (void*)0 magic in general, which is why I replaced that with
__null.
I believe that NULL should be retrieved from stddef.h, as I outlined
earlier. This will get the __null definition, which should work for
everyone. Does anyone have any practical problems with this?
Jason
More information about the Gcc
mailing list