https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571
--- Comment #3 from Pierre Ossman ---
And another odd case; gcc 5 complains about this:
> const char *a;
> a = NULL;
but not:
> const char *a = NULL;
gcc 13 complains about neither, and clang about both.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571
--- Comment #2 from Pierre Ossman ---
Found another case that neither gcc 5, gcc 13, nor clang complain about for
some odd reason:
> assert(thing == NULL);
All three complain about:
> assert(thing == 0);
Not sure what's going on here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114571
--- Comment #1 from Pierre Ossman ---
Hmm.. I found bug 77513, and r9-873. So I guess this is intentional?
This makes the warning somewhat pointless. We want to make sure developers
standardise on nullptr, both for style and since the
