J
James Kanze
[...]
Reread that, and please explain why it is more reasonable to
define a "null POINTER constant" as an int than as a pointer
(regardless of type). Implicit conversion (other than the null
pointer conversion) are irrelevant, because we're talking about
a special case, where compiler magic is involved.
The only thing one can really conclude is that none of this is
reasonable, and that we really need a real null pointer type
(for which there is a proposal, so we might actually get it in
the next version of the standard).
The reason I say the implicit conversion is arguably more important is
because it's what makes it reasonable to define NULL as a pointer to
void rather than an int. IOW, the one is more or less a consequence of
the other.
Reread that, and please explain why it is more reasonable to
define a "null POINTER constant" as an int than as a pointer
(regardless of type). Implicit conversion (other than the null
pointer conversion) are irrelevant, because we're talking about
a special case, where compiler magic is involved.
The only thing one can really conclude is that none of this is
reasonable, and that we really need a real null pointer type
(for which there is a proposal, so we might actually get it in
the next version of the standard).