Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!portal!cup.portal.com!dan-hankins
From: dan-hankins@cup.portal.com (Daniel B Hankins)
Newsgroups: comp.lang.misc
Subject: Re: object oriented design decision
Message-ID: <11256@cup.portal.com>
Date: 13 Nov 88 07:47:04 GMT
References: <10633@cup.portal.com>
Organization: The Portal System (TM)
Lines: 15

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.

Lexical scoping inhibits reusability.  Solution: allow multiple classes with
the same name, and distinguish them on the basis of what their superclass
chain is.  Since this language has no declaration of variable class (all
type checking is done by something like lint, and at runtime), this won't
create problems with the user having to type in unmanageably long names
in type declaration statements.

Dan Hankins