From: Fergus Henderson <fjh@cs.mu.OZ.AU>
To: ebritten@uci.edu
Cc: gnu-win32@cygnus.com
Subject: Re: Missing virtual functions
Date: Mon, 01 Sep 1997 18:30:00 -0000 [thread overview]
Message-ID: <199709010253.MAA26759@mundook.cs.mu.OZ.AU> (raw)
In-Reply-To: <33FF524B.7B256D82@uci.edu>
This is an off-topic answer to an off-topic question about GNU C++.
Eric Britten <ebritten@uci.edu> writes:
>Yesterday I found that if one declares virtual functions in a class
>like:
>
>class A
>{
> A();
> virtual void B();
>};
>
>and the definitions for the functions(inline or external) are not found
>by the linker then two types of linking errors result.
>
>1. Undefined reference to a vtable in the constructors of the class.
>2. Undefined reference to any other inline functions of the class that
>are used by other code.
>
>It took me a while to figure out that if all virtual functions are
>defined, then these errors go away. Is this GNU specific?
The exact error messages you get are probably specific to GNU C++.
However, the fact that you do get errors if virtual functions
are not defined is not GNU specific. The GNU behaviour conforms
to the draft ANSI/ISO C++ standard, which says that programs must
contain a definition of every virtual function. (Implementations
are not _required_ to diagnose this error, however, so such code
_may_ work on other compilers...)
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh > | of excellence is a lethal habit"
PGP: finger fjh@128.250.37.3 | -- the last words of T. S. Garp.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
prev parent reply other threads:[~1997-09-01 18:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-27 7:06 Eric Britten
1997-09-01 18:30 ` Fergus Henderson [this message]
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=199709010253.MAA26759@mundook.cs.mu.OZ.AU \
--to=fjh@cs.mu.oz.au \
--cc=ebritten@uci.edu \
--cc=gnu-win32@cygnus.com \
/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).