Path: csiph.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news.iecc.com!.POSTED.news.iecc.com!nerds-end From: Hans-Peter Diettrich Newsgroups: comp.compilers Subject: Re: OOP language design after Algol 60, was Add nested-function support Date: Sun, 15 Apr 2018 00:12:57 +0200 Organization: Compilers Central Lines: 22 Sender: news@iecc.com Approved: comp.compilers@iecc.com Message-ID: <18-04-069@comp.compilers> References: <49854345-f940-e82a-5c35-35078c4189d5@gkc.org.uk> <18-03-103@comp.compilers> <18-03-042@comp.compilers> <18-03-047@comp.compilers> <18-03-075@comp.compilers> <18-03-079@comp.compilers> <18-03-101@comp.compilers> <18-04-002@comp.compilers> <18-04-003@comp.compilers> <18-04-004@comp.compilers> <18-04-024@comp.compilers> <18-04-034@comp.compilers> <18-04-041@comp.compilers> <18-04-051@comp.compilers> <18-04-057@comp.compilers> <18-04-066@comp.compilers> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Info: gal.iecc.com; posting-host="news.iecc.com:2001:470:1f07:1126:0:676f:7373:6970"; logging-data="65114"; mail-complaints-to="abuse@iecc.com" Keywords: OOP, history Posted-Date: 14 Apr 2018 21:02:14 EDT X-submission-address: compilers@iecc.com X-moderator-address: compilers-request@iecc.com X-FAQ-and-archives: http://compilers.iecc.com Xref: csiph.com comp.compilers:2080 Am 14.04.2018 um 19:40 schrieb George Neuner: > The problem is in unrelated classes that need to implement the entire > interface. Consider, e.g., serializable, or displayable - in many > languages you would end up reimplementing the entire interface in > every branch of your heirarchy, with overrides in virtually every > subclass. Please give an example where inheritance from a "serializable" base class can do something meaningful, without explicitly coded integration into the derived class. > The "implements" mechanism saves work in SI languages, but it is less > useful in an MI language where any class can simply inherit whatever > functionality it needs. See above. Fully unrelated functionality does not even deserve a relationship between both classes, no inheritance at all. Any dependencies require explicit code, even in MI. DoDi