Path: utzoo!attcan!uunet!mcvax!unido!laura!exunido!georg
From: georg@exunido.uucp (Georg A. M. Heeg)
Newsgroups: comp.lang.smalltalk
Subject: Re: Smalltalk versus C++
Keywords: object-oriented languages
Message-ID: <833@laura.UUCP>
Date: 7 Jan 89 15:29:20 GMT
References: <447@ubbpc.UUCP> <824@laura.UUCP> <451@ubbpc.UUCP> <907@scubed.UUCP>
Sender: root@laura.UUCP
Reply-To: georg@exunido.UUCP (Georg A. M. Heeg)
Organization: Georg Heeg, Dortmund, W-Germany
Lines: 31

In article <907@scubed.UUCP> warner@s3snorkel.UUCP (Ken Warner) writes:
...
>Duh...sorry to intrude on your conversation but could you explain to me
>the difference between dynamic and static classes.  I'm not trying to pick
>a fight; I really don't understand the difference.
Don't be shy! I welcome any contribution. In standard compilation languages
like c or c++ you do not have a chance to change any class during the run
time of an application. You have to change sources and recompile and relink
the whole thing. This is called "static". "Dynamic" you know yourself being
a Smalltalk-80 programmer.

>>> >(3) Smalltalk has multiple inheritance...
>
>I am working with ParcPlace ST-80.  How do I do multiple-inheritance?  It 
>sounds interesting.
In the VI2.2 documentation there is a reprint of Borning's article how to use
it. What is described there also works in VI2.3 (I did not test VI2.4 yet).

use 
subclass: t otherSupers: others instanceVariableNames: f classVariableNames: d category: cat 

instead of:
subclass: t instanceVariableNames: f classVariableNames: d poolDictionaries: s category: cat 

as class creation message.

I played a bit with this feature. But I decided to never use it really.
I think this is the reason ParcPlace excluded the description from their
new documentation.

Georg Heeg