From: Shriramana Sharma <samjnaa@gmail.com>
To: Linux C Programming List <linux-c-programming@vger.kernel.org>
Subject: Re: Virtual functions and destructors
Date: Thu, 23 Mar 2006 07:32:21 +0530 [thread overview]
Message-ID: <200603230732.21532.samjnaa@gmail.com> (raw)
In-Reply-To: <200603222327.41672.mayday@gmx.net>
Thursday, 23 March 2006 03:57 samaye tvayaa likhitam:
> I'm not sure if this is right. Functions can always be overloaded.
He did not speak of functions being overloaded. He spoke of functions being
over-*ridden*.
> Further I believe that once a function is declared virtual it always stays
> that way. Even if in subsequently derived classes it is not explicitly
> declared virtual any longer.
Verified this using a grandchild class.
--
Tux #395953 resides at http://samvit.org
playing with KDE 3.51 on SUSE Linux 10.0
$ date [] CCE +2006-03-23 W12-4 UTC+0530
next prev parent reply other threads:[~2006-03-23 2:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 15:20 Virtual functions and destructors Shriramana Sharma
2006-03-19 17:38 ` Steve Graegert
2006-03-22 22:27 ` Benjamin Sobotta
2006-03-23 2:02 ` Shriramana Sharma [this message]
2006-03-23 22:00 ` Benjamin Sobotta
2006-03-24 1:07 ` Glynn Clements
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=200603230732.21532.samjnaa@gmail.com \
--to=samjnaa@gmail.com \
--cc=linux-c-programming@vger.kernel.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 NNTP newsgroup(s).