public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/57854] Would like to have a warning for virtual overrides without C++11 "override" keyword Date: Tue, 09 Jul 2013 09:29:00 -0000 [thread overview] Message-ID: <bug-57854-4-gN1gmUoy5K@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-57854-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57854 Manuel López-Ibáñez <manu at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jason at gcc dot gnu.org, | |manu at gcc dot gnu.org --- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to Thiago Macieira from comment #0) > I would like a new (optional) warning that would point out every C++ virtual > override that is done without the C++11 keyword that indicates an override. > By necessity, this warning would only be permitted in C++11 mode. Hi Thiago, I am so grateful for KDE that I would like to help here if possible. But I would like to ask the C++ maintainer whether this is something that would be accepted in mainline G++ and whether G++ has the capabilities to detect this easily. Jason, what do you think? Perhaps the same issues that made [[base_check]] to be dropped would affect the implementation of this warning? I don't know the specifics. >From gcc-bugs-return-426003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jul 09 09:29:07 2013 Return-Path: <gcc-bugs-return-426003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 834 invoked by alias); 9 Jul 2013 09:29:07 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: <gcc-bugs.gcc.gnu.org> List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/> List-Post: <mailto:gcc-bugs@gcc.gnu.org> List-Help: <mailto:gcc-bugs-help@gcc.gnu.org> Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 653 invoked by uid 48); 9 Jul 2013 09:29:04 -0000 From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/54366] [meta-bug] decltype issues Date: Tue, 09 Jul 2013 09:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.8.0 X-Bugzilla-Keywords: meta-bug X-Bugzilla-Severity: normal X-Bugzilla-Who: paolo.carlini at oracle dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_status resolution Message-ID: <bug-54366-4-Ihocz9UfAZ@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-54366-4@http.gcc.gnu.org/bugzilla/> References: <bug-54366-4@http.gcc.gnu.org/bugzilla/> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-07/txt/msg00510.txt.bz2 Content-length: 472 http://gcc.gnu.org/bugzilla/show_bug.cgi?idT366 Bug 54366 depends on bug 51786, which changed state. Bug 51786 Summary: [c++0x] Invalid declaration with decltype accepted http://gcc.gnu.org/bugzilla/show_bug.cgi?idQ786 What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution|--- |FIXED
next prev parent reply other threads:[~2013-07-09 9:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-07-08 23:39 [Bug c++/57854] New: " thiago at kde dot org 2013-07-09 9:29 ` manu at gcc dot gnu.org [this message] 2013-07-09 9:36 ` [Bug c++/57854] " redi at gcc dot gnu.org 2013-07-09 9:50 ` manu at gcc dot gnu.org 2014-12-14 14:53 ` ville.voutilainen at gmail dot com 2015-01-13 15:57 ` ville.voutilainen at gmail 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-57854-4-gN1gmUoy5K@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).