Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!wuarchive!uunet!odi!dlw
From: dlw@odi.com (Dan Weinreb)
Newsgroups: comp.object
Subject: Re: Examples of Multiple Inheritance?
Message-ID: <1990Dec6.161153.20397@odi.com>
Date: 6 Dec 90 16:11:53 GMT
References: <60700005@inmet> <13688@cadillac.CAD.MCC.COM>
Reply-To: dlw@odi.com
Organization: Object Design, Inc.
Lines: 15
In-Reply-To: franke@lynx.cad.mcc.com's message of 5 Dec 90 15:22:29 GMT

In article <13688@cadillac.CAD.MCC.COM> franke@lynx.cad.mcc.com (David Franke) writes:


   >Our hypothesis is that multiple inheritance can rarely be useful
   >unless planned for in advance, which seems to defeat the purpose.

   It is certainly true in this case that the multiple inheritance was
   planned in advance.

I don't see anything wrong with planning in advance.  Indeed, many
people actually think that it is a virtue to design software in
advance. :-) The reason for multiple inheritance is not specially to
facilitate unplanned ex-post-facto kludges.  Seriously, in most cases
of multiple inheritance that I know about, it was entirely planned
that way from the beginning.


Brought to you by Super Global Mega Corp .com