This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
c++/4755: virtual abstract member function
- To: gcc-gnats at gcc dot gnu dot org
- Subject: c++/4755: virtual abstract member function
- From: petridis at iit dot demokritos dot gr
- Date: 31 Oct 2001 15:49:49 -0000
- Reply-To: petridis at iit dot demokritos dot gr
>Number: 4755
>Category: c++
>Synopsis: virtual abstract member function
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: wrong-code
>Submitter-Id: net
>Arrival-Date: Wed Oct 31 07:56:00 PST 2001
>Closed-Date:
>Last-Modified:
>Originator: Sergios
>Release: gcc version 3.0
>Organization:
>Environment:
windows 2000, cygwin
>Description:
Hi,
I'm not certain that this should be considered as a bug. However it is the only case that I now, where when calling a virtual member function that is declared as abstract (=0),
the linker (and not the compiler) produces the error.
This can be confusing, when a big number of nested classes is involved.
Hope I helped !
>How-To-Repeat:
struct A
{
virtual int f() = 0;
};
struct B : A
{
int f()
{
return A::f();
};
};
int main()
{
B t;
};
>Fix:
The linker message is informative enough
>Release-Note:
>Audit-Trail:
>Unformatted: