public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gdr at cs dot tamu dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/17920] add __attribute__((reimpl)) as a replacement for the (optional) virtual keyword for reimplementations of virtual functions Date: Sun, 10 Oct 2004 22:46:00 -0000 [thread overview] Message-ID: <20041010224640.24581.qmail@sourceware.org> (raw) In-Reply-To: <20041010085558.17920.mutz@kde.org> ------- Additional Comments From gdr at cs dot tamu dot edu 2004-10-10 22:46 ------- Subject: Re: add __attribute__((reimpl)) as a replacement for the (optional) virtual keyword for reimplementations of virtual functions "giovannibajo at libero dot it" <gcc-bugzilla@gcc.gnu.org> writes: | As far as I can tell, this is just a hint for the compiler to | generate better diagnostic. Pretty much like attribute(sentinel) for | instance: we just give the compiler more information, we are not | modifying the semantic of a program. | | I'm actually in favor of this PR so I will confirm this. This is not an | extension as in we are modifying the language semantic, adding | strange features or whatnot. I disagree with the notion that it is just a diagnostic related issue; because it comes with a semantics part. Let's not not disguise a language extension under the name of diagnostic improvement. It helps nobody. -- Gaby -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17920
next prev parent reply other threads:[~2004-10-10 22:46 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-10 8:56 [Bug c++/17920] New: " mutz at kde dot org 2004-10-10 14:20 ` [Bug c++/17920] " pinskia at gcc dot gnu dot org 2004-10-10 16:06 ` pinskia at gcc dot gnu dot org 2004-10-10 16:14 ` gdr at cs dot tamu dot edu 2004-10-10 22:41 ` giovannibajo at libero dot it 2004-10-10 22:46 ` gdr at cs dot tamu dot edu [this message] 2004-10-11 9:28 ` giovannibajo at libero dot it 2004-10-11 12:54 ` bangerth at dealii dot org [not found] <bug-17920-5280@http.gcc.gnu.org/bugzilla/> 2008-08-21 18:45 ` thomas dot mcguire at gmx dot net 2008-08-21 19:06 ` pluto at agmk dot net 2008-08-21 19:16 ` thomas dot mcguire at gmx dot net 2008-11-30 15:47 ` Woebbeking at web dot de 2008-12-27 22:05 ` pinskia at gcc dot gnu dot org 2010-01-05 16:27 ` shcherbakov at daad-alumni dot de 2010-01-06 11:58 ` jwakely dot gcc at gmail dot com [not found] <bug-17920-4@http.gcc.gnu.org/bugzilla/> 2011-06-21 16:02 ` redi at gcc dot gnu.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=20041010224640.24581.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: 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).