From mboxrd@z Thu Jan  1 00:00:00 1970
From: petridis@iit.demokritos.gr
To: gcc-gnats@gcc.gnu.org
Subject: c++/4755: virtual abstract member function
Date: Wed, 31 Oct 2001 07:56:00 -0000
Message-id: <20011031154949.10452.qmail@sourceware.cygnus.com>
X-SW-Source: 2001-10/msg00713.html
List-Id: <gcc-prs.sourceware.org>

>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: