From: Benjamin Scherrey <scherrey@switchco.com>
To: gcc@gcc.gnu.org
Subject: Non-default ctors, virtual base classes, & multiple inheritance all at once!
Date: Tue, 05 Sep 2000 11:15:00 -0000 [thread overview]
Message-ID: <39B5343C.AB738C1C@switchco.com> (raw)
I'm having some trouble getting non-default constructors called for
virtual baseclasses in certain instances.. I've attached some code that
demonstrates this problem. In some cases, I can pass a parameter up the
tree to the virtual base class, in others, the default ctor is always
called even though my code clearly specifies the ctor taking a parm. Is
this a compiler bug or a language design issue?
thanx & later,
Ben Scherrey
next reply other threads:[~2000-09-05 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-05 11:15 Benjamin Scherrey [this message]
2000-09-06 3:27 ` Alexandre Oliva
2000-09-06 8:39 ` Joe Buck
2000-09-06 9:37 ` sidster
2000-09-06 20:00 ` (retracting my comment) " sidster
2000-09-06 20:42 ` Alexandre Oliva
2000-09-05 12:12 Non-default ctors, virtual base classes, & multiple inheritance all atonce! rlau
2000-09-05 16:35 ` Non-default ctors, virtual base classes, & multiple inheritance all at once! llewelly
2000-09-05 22:59 ` Benjamin Scherrey
2000-09-06 10:13 Jan Reimers
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=39B5343C.AB738C1C@switchco.com \
--to=scherrey@switchco.com \
--cc=gcc@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).