Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!ncrlnk!ncrcae!hubcap!billwolf%hazel.cs.clemson.edu
From: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu (William Thomas Wolfe, 2847 )
Newsgroups: comp.object
Subject: Re: object-oriented this, that, and the other thing
Message-ID: <7292@hubcap.clemson.edu>
Date: 2 Dec 89 21:02:40 GMT
References: <10028@june.cs.washington.edu>
Sender: news@hubcap.clemson.edu
Reply-To: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu
Lines: 19

From ewan@cs.washington.edu (Ewan Tempero):
> The point I was trying to make, was that there is nothing inherent
> in objects that relates to code-sharing mechanisms. I read somewhere
> that it would be possible to put environment support on top of
> Modula-2 (or was it Ada?) that would allow things of the form
> NewModule.NewFunction = OldModule.OldFunction + stuff [this is very
> hazy and I don't have a reference for it. Does anyone?]. 

    There is a product called "Classic Ada" (available from Software
    Productivity Solutions, SPS@radc-softvax.arpa) which provides
    exactly this: it permits Ada software developers to use inheritance
    and dynamic binding in object-oriented Ada designs.  The code produced 
    is totally standardized, compile-it-anywhere, 100% portable Ada.

    A number of other vendors are jumping into this market as well,
    pending the inclusion of object-oriented facilities in Ada 9X.


    Bill Wolfe, wtwolfe@hubcap.clemson.edu


Brought to you by Super Global Mega Corp .com