Path: utzoo!attcan!uunet!mcvax!hp4nl!eurtrx!euraiv1!reino
From: reino@euraiv1.UUCP (Reino de Boer)
Newsgroups: comp.lang.misc
Subject: Re^2: object oriented design decision
Message-ID: <795@euraiv1.UUCP>
Date: 14 Nov 88 12:08:55 GMT
References: <10633@cup.portal.com> <11256@cup.portal.com>
Organization: Erasmus University EF/AIV,Rotterdam,Netherlands
Lines: 17

dan-hankins@cup.portal.com (Daniel B Hankins) writes:

>Thanks for all the email responses to my query.  To summarize:

>Multiple inheritance is an indication that something is wrong with the class
>hierarchy.  Restructure that and single inheritance should do fine.  This
>also does away with things like the specific inheritance mechanism and
>method/variable drop clauses.

>Dan Hankins

How about having two separate classes for a linked list:
Class List
Class EmptyList
and trying to build a stack as subclass of List and EmptyList.
Isn't multiple inheritance nicer than trying to make class List act like
two separate concepts ?