Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!rochester!kodak!uupsi!sunic!news.funet.fi!tukki.jyu.fi!sakkinen
From: sakkinen@tukki.jyu.fi (Markku Sakkinen)
Newsgroups: comp.object
Subject: Re: ADT vs. Objects
Message-ID: <1990Nov16.061612.14517@tukki.jyu.fi>
Date: 16 Nov 90 06:16:12 GMT
References: <1990Nov13.212012.3662@Neon.Stanford.EDU> <3187@mrsvr.UUCP> <PCG.90Nov15184256@teachk.cs.aber.ac.uk>
Reply-To: sakkinen@jytko.jyu.fi (Markku Sakkinen)
Organization: University of Jyvaskyla, Finland
Lines: 26

In article <PCG.90Nov15184256@teachk.cs.aber.ac.uk> pcg@cs.aber.ac.uk (Piercarlo Grandi) writes:
>On 14 Nov 90 16:18:52 GMT, chandra@mrsvr.UUCP (B. Chandramouli) said:

> ...

>chandra> You need inheritance provided by the language when you want to
>chandra> subclass from a class that is part of a standard class library
>chandra> provided by a vendor for which you have only the object code
>chandra> and not the source.
>
>Ahem. Really? I have ever more the impression that you have a very
>narrow definition of code sharing and reuse.

Narrow definition? I did not see any claim of inheritance being
everything one needs for code sharing and reuse.
Please share (without making us inherit) some of your broad vision with us
in the newsgroup and tell how inheritance in this sense can be practically
replaced by other means in commonly available environments.

Markku Sakkinen
Department of Computer Science and Information Systems
University of Jyvaskyla (a's with umlauts)
Seminaarinkatu 15
SF-40100 Jyvaskyla (umlauts again)
Finland
          SAKKINEN@FINJYU.bitnet (alternative network address)