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.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,158ce2376534c35d X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news3.google.com!feeder2.cambriumusenet.nl!feeder3.cambriumusenet.nl!feed.tweaknews.nl!193.201.147.78.MISMATCH!feeder.news-service.com!feeder.news-service.com!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Derived private interface Date: Wed, 10 Aug 2011 11:11:51 +0200 Organization: cbb software GmbH Message-ID: <1bs0xoar40rx.6yb23bgkfrew.dlg@40tude.net> References: <27656578-65aa-48b9-9f89-4ebd4e0cb02a@glegroupsg2000goo.googlegroups.com> <0fe3b0f8-c064-444d-899d-640e891b58c3@w4g2000yqm.googlegroups.com> <128d8eb5-1cc6-47e3-a09b-b53a5ef289ce@m10g2000yqd.googlegroups.com> <4e141501$0$6629$9b4e6d93@newsspool2.arcor-online.net> <4b2728fc-6127-45d8-a314-9fc491701c26@g12g2000yqd.googlegroups.com> <82vcve4bqx.fsf@stephe-leake.org> <4e15b223$0$6541$9b4e6d93@newsspool4.arcor-online.net> <4a4f185d-5268-4d73-a5df-8149bd117e0f@h9g2000vbr.googlegroups.com> Reply-To: mailbox@dmitry-kazakov.de NNTP-Posting-Host: Z9sOdOMnevEp2LCK1Iaf0g.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org User-Agent: 40tude_Dialog/2.0.15.1 X-Notice: Filtered by postfilter v. 0.8.2 Xref: g2news2.google.com comp.lang.ada:21475 Date: 2011-08-10T11:11:51+02:00 List-Id: On Tue, 9 Aug 2011 16:35:14 -0500, Randy Brukardt wrote: > I understand the value of the Open/Close principle, but it only is a win in > Ada if there are multiple interfaces associated with an object. Otherwise, > the amount of change is the same (or even less) for the non-OOP solution. It could be true only if there were only one place of dispatch. In reality there are many dispatching calls and many class-wide operations (for which there is no typed procedural equivalent). Procedural solution would necessary have to bend design in order to reduce the number of such places, each requiring maintenance. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de