Re: nullptr vs 0

From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2022-05-29 23:38:58

On 5/30/22 02:22, Gavin Lambert via Boost wrote:
> On 27/05/2022 23:00, Andrey Semashev wrote:
>> It *is* a useless warning. The code with NULL is explicit enough and
>> portable, so what is this warning about? That the code is not
>> C++11-only? I know that, and it's not up to the compiler to tell me that.
> 
> The problem is that NULL is defined as a plain 0...

This is an implementation detail. It could be __builtin_null(), which
would behave equivalent to 0 or (void*)0 but would not emit warnings.