Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!decwrl!sun!hanami!landman
From: landman%hanami@Sun.COM (Howard A. Landman)
Newsgroups: comp.sys.mac.programmer
Subject: Re: The Crunched Shell (long)
Keywords: Object-oriented programming
Message-ID: <60865@sun.uucp>
Date: 21 Jul 88 19:13:04 GMT
References: <2328@pt.cs.cmu.edu> <12362@agate.BERKELEY.EDU>
Sender: news@sun.uucp
Reply-To: landman@sun.UUCP (Howard A. Landman)
Organization: Sun Microsystems, Mountain View
Lines: 17

In article <12362@agate.BERKELEY.EDU> elcond@garnet.berkeley.edu (Gregory Dow) writes:
>Classes are defined by using 3 source files:  A .c file which contains
>the code for each of the class's methods, and two header files -- one
>which declares the class's instance variables and the other which defines
>the message names and data structures.  Inheritance (single only) is
>achieved through the miracle of nested #include files.  The header files
>for a class #include the header files of its superclass.  A class inherits
>ALL the instance variables and methods of its superclass.

Gee - this sounds like you can get multiple inheritance just by nesting
2 or more include files.  So why "single only"?  (Assuming no conflicts.)
Is it because you need to know which SuperClass to pass a message to if the
local Class can't handle it, so the dispatcher would get more complicated?

	Howard A. Landman
	landman@hanami.sun.com
	UUCP: sun!hanami!landman