27 May
2022
27 May
'22
1:18 p.m.
On Fri, 27 May 2022 at 13:01, Andrey Semashev via Boost wrote:
On 5/27/22 05:14, Emil Dotchevski via Boost wrote:
On Sun, May 22, 2022 at 3:35 AM Andrey Semashev via Boost wrote:
I'd replace 0 with NULL. If the compiler keeps complaining report a compiler bug and suppress the warning with a pragma.
I'm all for disabling useless warnings, but then you can leave 0 in the code and not bother with NULL. What are you, a C programmer? :)
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.
Even if you compile with -std=c++11 ? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net