home *** CD-ROM | disk | FTP | other *** search
- Organization: Junior, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA
- Path: sparky!uunet!europa.asd.contel.com!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!fs7.ece.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!sm86+
- Newsgroups: comp.lang.c++
- Message-ID: <UehC5QK00VpdEXFmlo@andrew.cmu.edu>
- Date: Mon, 14 Sep 1992 15:00:44 -0400
- From: Stefan Monnier <sm86+@andrew.cmu.edu>
- Subject: Re: Virtual methods
- In-Reply-To: <1992Sep14.145950.7661@us-es.sel.de>
- References: <#7vnafk.feustel@netcom.com>
- <1992Sep14.145950.7661@us-es.sel.de>
- Lines: 30
-
- Excerpts from netnews.comp.lang.c++: 14-Sep-92 Virtual methods
- Dalton@us-es.sel.de (664)
- > This reminds me of a question which I've been meaning to ask for some
- > time now. Ignoring performance issues, why would one not declare every
- > method in a class virtual? What circumstances might preclude its use?
-
- > --
- > Brendan J. Dalton (brendan@us-es.sel.de)
- > ----------------------------------------
- > Ritheann an fear seo ar phoitin
-
-
- You've got it: performance issue !
- (well, there could be some other issues: arrange so that future
- subclasses can't change that method (protection). But is it
- really useful ?)
- BTW: Gcc has a commandline option which declares all methods
- as virtual ! OOP is just so much less powerful without virtuality !
-
-
- Stefan Monnier
-
- -----------------------------------------------------
- -- On the average, people seem to be acting normal --
- -----------------------------------------------------
-
-
-
-
-
-