Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!ames!lll-tis!helios.ee.lbl.gov!pasteur!agate!ucbvax!ucsd!nosc!cod!owen
From: owen@cod.NOSC.MIL (Wallace E. Owen)
Newsgroups: comp.lang.c++
Subject: Re: OOP languages and software reuse
Message-ID: <1319@cod.NOSC.MIL>
Date: 5 Dec 88 17:00:33 GMT
References: <1250001@hpcllca.HP.COM> <612@cadillac.CAD.MCC.COM> <10121@watdragon.waterloo.edu>
Reply-To: owen@cod.nosc.mil.UUCP (Wallace E. Owen)
Organization: Naval Ocean Systems Center, San Diego
Lines: 16

In article <10121@watdragon.waterloo.edu> akwright@watdragon.waterloo.edu (Andrew K. Wright) writes:
>ie.  I have a pre-existing class STRING (built by someone else),
>which I am not allowed to modify.  Then I cannot sort it, unless
>the designer anticipated my need and caused STRING to inherit from
>SORTABLE.
This problem 'goes away' with multiple inheritance. Derive a class
SORTABLE_STRING from SORTABLE and STRING.

BTW: When do 'we' get C++ v2.0?
>Andrew K. Wright      akwright@watmath.waterloo.edu
>CS Dept., University of Waterloo, Ont., Canada.


Wallace Owen
Naval Ocean Systems Center
cod.nosc.mil!owen