public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "anthony.foiani at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/50477] -Wunused-parameter should not warn about virtual method declarations with bodies Date: Wed, 15 May 2013 05:54:00 -0000 [thread overview] Message-ID: <bug-50477-4-yfEusxZAbf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50477-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50477 Anthony Foiani <anthony.foiani at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |anthony.foiani at gmail dot com --- Comment #7 from Anthony Foiani <anthony.foiani at gmail dot com> --- Sorry to resurrect an oldish bug, but I was just bitten by a related issue (bug 57211). One case where I run into Miles' situation is when writing documentation; as mentioned, root classes often have no-op stubs, but they're also where those stubs are documented. E.g., /** * Do stuff with @a foo. * * @param[in] foo widget to frobnicate. * * @return whether foo was successfully frobbed. */ virtual bool frobnicate( Widget & foo ) {} If I use "/* foo */", then doxygen will complain that there is no matching parameter name. If I don't use those comments, then -Wunused-parameters gives me a warning. Would it be possible to introduce something like -Wno-virtual-unused-parameters to accomodate this? Or possibly merge it with a flag that would allow similar ignoring of defaulted methods (which is how I got here). Thanks!
prev parent reply other threads:[~2013-05-15 5:54 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-22 6:40 [Bug c++/50477] New: " miles at gnu dot org 2011-09-22 22:05 ` [Bug c++/50477] " pinskia at gcc dot gnu.org 2011-09-22 22:38 ` miles at gnu dot org 2011-09-23 9:00 ` jakub at gcc dot gnu.org 2011-09-23 10:00 ` miles at gnu dot org 2012-05-24 15:39 ` paolo.carlini at oracle dot com 2012-05-24 19:52 ` jason at gcc dot gnu.org 2013-05-15 5:54 ` anthony.foiani at gmail dot com [this message]
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-50477-4-yfEusxZAbf@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: linkBe 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).