home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ames!data.nas.nasa.gov!taligent!apple!voder!genie!roger
- From: roger@genie.UUCP (Roger H. Scott)
- Newsgroups: comp.lang.c++
- Subject: Re: Virtual base classes
- Keywords: virtual, class
- Message-ID: <445@genie.UUCP>
- Date: 14 Dec 92 00:20:19 GMT
- References: <1992Dec3.202705.16646@ucc.su.OZ.AU> <rmartin.723768537@thor> <1992Dec8.192759.24081@cs.brown.edu>
- Reply-To: roger@genie.UUCP (Roger H. Scott)
- Organization: proCASE Corporation, Santa Clara, CA
- Lines: 13
-
- In article <1992Dec8.192759.24081@cs.brown.edu> sdm@cs.brown.edu (Scott Meyers) writes:
- >In article <rmartin.723768537@thor> rmartin@thor.Rational.COM (Bob Martin) writes:
- >| ... There is nothing that can be done with private inheritance that cannot
- >| be done, just as simply, with containment.
- >
- >Except for redefining virtual functions and accessing protected members.
-
- If Kludge is a non-public subclass [derived class] of WellFormed then there
- isn't much point in talking about Kludge redefining WellFormed's virtual
- functions since you can't use a Kludge in a place where a WellFormed is
- expected (i.e., who would ever have hold of a Kludge and send it one of
- WellFormed'd messages [call one of WellFormed'd virtual functions], other than
- a member function of Kludge?).
-