public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "igodard at pacbell dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/21917] New: Missing warning? (or error?) Date: Sat, 04 Jun 2005 22:18:00 -0000 [thread overview] Message-ID: <20050604221804.21917.igodard@pacbell.net> (raw) struct virt { virt() : i(2) {} virt(int i) : i(i){} int i; }; struct der1 : public virtual virt { der1(int i) : virt(i) {} }; struct der2 : public virtual virt { der2(int i) : virt(i) {} }; struct top : public der1, public der2 { top () : der1(0), der2(1) {} }; int main() { top t; } Compiles without comment. However, the null constructor for "virt" is called rather than the explicit constructor that is indicated by the constructor chain from top. In fact, the der* constructors say " : virt(i)" but that sub-constructor will never be called because virt is a virtual base class. I don't know if it is actually an error to try to explicitly construct a virtual base, but is sure is misleading and I think deserves at least a warning. -- Summary: Missing warning? (or error?) Product: gcc Version: 3.4.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: igodard at pacbell dot net CC: gcc-bugs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21917
next reply other threads:[~2005-06-04 22:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-04 22:18 igodard at pacbell dot net [this message] 2005-06-04 22:22 ` [Bug c++/21917] " igodard at pacbell dot net 2005-06-05 3:03 ` pinskia at gcc dot gnu dot org 2005-06-06 1:24 ` [Bug c++/21917] Missing warning? pinskia at gcc dot gnu dot org 2005-07-13 13:17 ` pinskia at gcc dot gnu dot org 2005-07-13 13:31 ` pinskia at gcc dot gnu dot 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=20050604221804.21917.igodard@pacbell.net \ --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).