27 May
2022
27 May
'22
2:14 a.m.
On Sun, May 22, 2022 at 3:35 AM Andrey Semashev via Boost < boost@lists.boost.org> 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? :) The whole point of BOOST_NULLPTR is to not have to deal with the useless warning. Under that assumption, I don't see an alternative.