Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!brunix!sdm
From: sdm@cs.brown.edu (Scott Meyers)
Newsgroups: comp.lang.c++
Subject: Nonvirtual base classes in MI
Message-ID: <62555@brunix.UUCP>
Date: 25 Jan 91 21:36:11 GMT
Sender: news@brunix.UUCP
Reply-To: sdm@cs.brown.edu (Scott Meyers)
Organization: Brown University Department of Computer Science
Lines: 15

Look, I've used single inheritance, both public and private, and multiple
inheritance, with virtual base classes no less, but I've never yet come up
with a plausible reason for wanting nonvirtual base classes in an
application using MI in an inheritance DAG.  If you have an application
that uses nonvirtual base classes in an inheritance DAG, I'd appreciate it
if you'd drop me a line briefly describing what you do and why you need
duplicated base classes.

Thanks,

Scott


-------------------------------------------------------------------------------
What do you say to a convicted felon in Providence?  "Hello, Mr. Mayor."