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=-1.9 required=5.0 tests=BAYES_00 autolearn=ham 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!proxad.net!feeder1-2.proxad.net!news.in2p3.fr!in2p3.fr!news.ecp.fr!news.jacob-sparre.dk!pnx.dk!jacob-sparre.dk!ada-dk.org!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Derived private interface Date: Wed, 10 Aug 2011 16:56:00 -0500 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: 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> <1bs0xoar40rx.6yb23bgkfrew.dlg@40tude.net> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1313013363 14919 69.95.181.76 (10 Aug 2011 21:56:03 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Wed, 10 Aug 2011 21:56:03 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 Xref: g2news2.google.com comp.lang.ada:21488 Date: 2011-08-10T16:56:00-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:1bs0xoar40rx.6yb23bgkfrew.dlg@40tude.net... > 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. That's exactly the case I meant. > In reality > there are many dispatching calls and many class-wide operations (for which > there is no typed procedural equivalent). Reality? The reality is in the web server interface I was describing there was only one such point of dispatch, and only a single interface to dispatch to. It's clearly a special case, but one that is pretty common in the systems I've worked on. All I was saying is that in that special case, there is no value to OOP in Ada. > Procedural solution would > necessary have to bend design in order to reduce the number of such > places, > each requiring maintenance. Not necessarily; a lot of problems have obvious bottlenecks where everything goes through a single point. Making complex dispatching designs in such cases only increases complexity and difficulty of maintenance. Randy.