This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/20207] null constructor not needed in multiple inheritance
- From: "Serge dot Iovleff at univ-lille1 dot fr" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Feb 2005 15:43:14 -0000
- Subject: [Bug c++/20207] null constructor not needed in multiple inheritance
- References: <20050225144353.20207.Serge.Iovleff@univ-lille1.fr>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From Serge dot Iovleff at univ-lille1 dot fr 2005-02-25 15:43 -------
(In reply to comment #1)
> I think this is invalid code but I don't know how to produce it right now.
Yes you can add an explicit call to the constructor of A0 in B and C,
in this case the error deseappear.
hovewer, as B and C are abstract virtual class, this constructor should never be
called by these class, but only by the derived class, like D.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20207