Re: PR c++/35669 NULL (__null) not considered different from 0 with C++

[Manuel López-Ibáñez <lopezibanez at gmail dot com>]

On 24 April 2010 20:14, Gerald Pfeifer <gerald@pfeifer.com> wrote:
> Hi Manu,
>
> On Sat, 20 Feb 2010, Manuel López-Ibáñez wrote:
>> 2010-02-20 ?Manuel López-Ibáñez ?<manu@gcc.gnu.org>
>>
>> ? ? ? PR c++/35669
>> ? ? ? * c.opt (Wconversion-null): New option.
>> ? ? ? * doc/invoke.texi (Wconversion-null): Document.
>
> are you planning to submit an update for gcc-4.6/changes.html
> covering this, too? ?Actually, that's new on 4.5, right, so it
> should go into gcc-4.5/changes.html?

I thought it was generally acknowledged that not every new option
needs to be documented in changes.html. This was the answer I got not
so long ago when I asked to document a new option. Since I disagree
with that policy. How about this?

Index: htdocs/gcc-4.5/changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.5/changes.html,v
retrieving revision 1.87
diff -r1.87 changes.html
354c354,362
<       <code>-Wabi</code> will now warn about code that uses the old
mangling.</li>
---
>       <code>-Wabi</code> will now warn about code that uses the old
>       mangling.</li>
>
>       <li>Conversions between <code>NULL</code> and non-pointer types
>       are now warned by default. The new option
>       <code>-Wno-conversion-null</code> disables these warnings.
>       Previously these warnings were only available when using
>       <code>-Wconversion</code> explicitly.</li>
>