public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61951] -Wextra switch produce warning: parameter 'ptr' set but not used [-Wunused-but-set-parameter]
Date: Wed, 17 Sep 2014 16:56:00 -0000	[thread overview]
Message-ID: <bug-61951-4-NJE1so8F4Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61951-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61951

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Is there anything wrong on the warning though?

[](Base* ptr){ ptr = new Deliv(); }

I think ptr here is lambda parameter, does it behave any different from
parameter to any other function?
void foo (Base* ptr) { ptr = new Deliv(); }
warns about parameter 'ptr' set but not used intentionally, so why shouldn't it
we warn about it in the lambda?  Doesn't the lambda just leak memory and not
actually store the pointer anywhere (it stores it into the parameter which is
never used)?


  parent reply	other threads:[~2014-09-17 16:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 15:13 [Bug c++/61951] New: -wExtra " moblaza at gmail dot com
2014-09-17 16:42 ` [Bug c++/61951] -Wextra " paolo.carlini at oracle dot com
2014-09-17 16:56 ` jakub at gcc dot gnu.org [this message]
2014-09-19  9:43 ` 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-61951-4-NJE1so8F4Z@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).