public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56373] -Wzero-as-null-pointer-constant: does not catch issues with smart pointers
Date: Mon, 18 Feb 2013 13:21:00 -0000	[thread overview]
Message-ID: <bug-56373-4-pM6uccQ2N3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56373-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2013-02-18 13:20:41 UTC ---
(In reply to comment #2)
> > It's necessary, because otherwise you get bogus warnings from ScopeGuard-style
> > RAII types.
> 
> In which case the constructor and destructor would be meaningful,
> which is not the case here.

~shared_ptr() has non-trivial side-effects, the compiler isn't smart enough to
determine they won't fire when its empty, so it's always meaningful.

If you're smart enough to know the object isn't used then don't create it :)


  parent reply	other threads:[~2013-02-18 13:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 11:35 [Bug c++/56373] New: " akim.demaille at gmail dot com
2013-02-18 12:08 ` [Bug c++/56373] " redi at gcc dot gnu.org
2013-02-18 12:53 ` akim.demaille at gmail dot com
2013-02-18 13:21 ` redi at gcc dot gnu.org [this message]
2013-02-18 13:23 ` akim.demaille at gmail dot com
2013-02-18 16:06 ` paolo.carlini at oracle dot com
2013-02-18 16:07 ` paolo.carlini at oracle dot com
2013-02-20  9:03 ` paolo at gcc dot gnu.org
2013-02-20  9:04 ` paolo.carlini at oracle dot com

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=bug-56373-4-pM6uccQ2N3@http.gcc.gnu.org/bugzilla/ \
    --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).