Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!rice!uw-beaver!sumax!amc-gw!jimm
From: jimm@amc-gw.amc.com (Jim McElroy)
Newsgroups: comp.lang.c++
Subject: comp.lang.c++
Keywords: C++, inheritance, composition
Message-ID: <1418@amc-gw.amc.com>
Date: 3 May 90 18:50:25 GMT
Organization: Applied Microsystems Corp.; Redmond, WA
Lines: 31



In the most recent issue of _The C++ Report_, Tom Cargill has an
article titled: "Multiple Inheritance: Still a Research Project?"

He writes that in the various published examples that he has seen,
the code can be rewritten to use single inheritance without the
code becomming larger or more complex.  The rewriting generally
involves making one of the classes a member of the other
(composition, instead of a second line of inheritance).

I would like to know the opinions of the readers of this group on
the following points:

	Multiple inheritance is --

		-- not worth it's weight in complexity

		-- convenient in a few instances, but non-essential

		-- very convenient

		-- absolutely essential

Also, can anyone show examples of program organization in which
multiple inheritance is a big win?

Jim McElroy
Meta-Analytics
Bellevue, Washington
jimm@amc.com