public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/35669] NULL (__null) not considered different from 0 with C++
Date: Sun, 14 Feb 2010 22:06:00 -0000	[thread overview]
Message-ID: <20100214220629.25866.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35669-14453@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from manu at gcc dot gnu dot org  2010-02-14 22:06 -------
(In reply to comment #18)
> 
> Expected output (like 'gcc -Wall -c a.c' provides):

Since those warnings are already part of Wconversion, what you are asking is to
move them to default or another option enabled by -Wall. Contrary to what I
said above, I don't see any problem if this construct does not have any valid
use. Such option, e.g., -Wconversion-nul could be enabled by -Wall (or by
default) and -Wconversion, independently.

If you get a C++ maintainer to say that they would approve such patch, I will
write it, test it and commit it for you.


-- 

manu at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mark at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35669


  parent reply	other threads:[~2010-02-14 22:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22 20:06 [Bug c++/35669] New: " l dot lunak at suse dot cz
2008-03-22 21:11 ` [Bug c++/35669] " rguenth at gcc dot gnu dot org
2008-03-22 23:16 ` l dot lunak at suse dot cz
2008-03-23 14:08 ` manu at gcc dot gnu dot org
2008-03-23 19:00 ` truedfx at gentoo dot org
2008-03-23 19:44 ` manu at gcc dot gnu dot org
2008-03-23 20:16 ` l dot lunak at suse dot cz
2008-03-23 22:18 ` manu at gcc dot gnu dot org
2009-02-12 17:57 ` peter at cordes dot ca
2009-04-28 20:01 ` mdorey at bluearc dot com
2009-04-29 12:51 ` bangerth at gmail dot com
2009-04-29 13:22 ` l dot lunak at suse dot cz
2009-04-29 16:47 ` mdorey at bluearc dot com
2009-12-08 10:49 ` redi at gcc dot gnu dot org
2009-12-21 20:02 ` mdorey at bluearc dot com
2009-12-22 10:36 ` jwakely dot gcc at gmail dot com
2009-12-22 18:12 ` mdorey at bluearc dot com
2010-02-14 20:19 ` manu at gcc dot gnu dot org
2010-02-14 21:47 ` l dot lunak at suse dot cz
2010-02-14 22:06 ` manu at gcc dot gnu dot org [this message]
2010-02-16 17:11 ` jason at gcc dot gnu dot org
2010-02-16 18:02 ` echristo at apple dot com
2010-02-16 18:06 ` manu at gcc dot gnu dot org
2010-02-16 18:09 ` echristo at apple dot com
2010-02-16 18:27 ` manu at gcc dot gnu dot org
2010-02-16 18:43 ` jason at redhat dot com
2010-02-20 21:32 ` manu at gcc dot gnu dot org
2010-02-20 21:38 ` manu at gcc dot gnu dot org
2010-02-20 23:51 ` jason at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100214220629.25866.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).