From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fac41,953e1a6689d791f6 X-Google-Attributes: gidfac41,public X-Google-Thread: f79bb,953e1a6689d791f6 X-Google-Attributes: gidf79bb,public X-Google-Thread: fdb77,953e1a6689d791f6 X-Google-Attributes: gidfdb77,public X-Google-Thread: 103376,953e1a6689d791f6 X-Google-Attributes: gid103376,public From: donh@syd.csa.com.au (Don Harrison) Subject: Re: Eiffel and Java Date: 1996/10/30 Message-ID: #1/1 X-Deja-AN: 193156425 sender: news@syd.csa.com.au x-nntp-posting-host: dev11 references: <55562c$nkd@mulga.cs.mu.OZ.AU> organization: CSC Australia, Sydney reply-to: donh@syd.csa.com.au newsgroups: comp.lang.eiffel,comp.lang.ada,comp.lang.sather,comp.lang.java.advocacy Date: 1996-10-30T00:00:00+00:00 List-Id: Fergus Henderson writes: :donh@syd.csa.com.au (Don Harrison) writes: : :>What is the purpose of separating interface and implementation inheritance? : :Suppose I have two existing library classes (perhaps supplied by different :vendors) which have some commonality, but don't inherit from a common :base class. In Sather, one can simply create a new interface and :declare these classes to be instances of this interface, without :modifying the existing code. Sorry. Don't follow. Can you give an example? Isn't this creating a superclass rather than separating interface and implementation inheritance? Don. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Don Harrison donh@syd.csa.com.au