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,29d8139471e3f53e X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!193.201.147.80.MISMATCH!news.astraweb.com!border3.a.newsrouter.astraweb.com!news.netcologne.de!ramfeed1.netcologne.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail From: "Dmitry A. Kazakov" Subject: Re: Securing type extensions Newsgroups: comp.lang.ada User-Agent: 40tude_Dialog/2.0.15.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Reply-To: mailbox@dmitry-kazakov.de Organization: cbb software GmbH References: <87iq2bfenl.fsf@mid.deneb.enyo.de> <874odv9npv.fsf@ludovic-brenta.org> <87y6b7cedd.fsf@mid.deneb.enyo.de> <66a3704c-54f9-4f04-8860-aa12f516134b@t3g2000vbb.googlegroups.com> <87d3sib44t.fsf@mid.deneb.enyo.de> <134q4k2ly2pf4$.17nlv1q6q5ivo.dlg@40tude.net> <4c8dec8e$0$6990$9b4e6d93@newsspool4.arcor-online.net> <4c8e3f44$0$6769$9b4e6d93@newsspool3.arcor-online.net> <4c8e87f8$0$6877$9b4e6d93@newsspool2.arcor-online.net> Date: Mon, 13 Sep 2010 22:41:40 +0200 Message-ID: NNTP-Posting-Date: 13 Sep 2010 22:41:39 CEST NNTP-Posting-Host: 3f80afec.newsspool4.arcor-online.net X-Trace: DXC=Ych4AnB7I>g:i=48;n?Z:`4IUK On Mon, 13 Sep 2010 22:22:30 +0200, Georg Bauhaus wrote: > Yes, exactly, the design decision to declare a publicly tagged > type (which of course will not be "final") entails mutual obligations: > my calls on overridden subprograms will rely on profiles and further > assumptions about overridden ops > (such as the LSP that has been mentioned), as do the overriding > ops of the user defined type. This kind of mutual > trust is unrelated to Ada's visibility rules. Of course it is. You have to see the operation as primitive, you have to see the object class-wide in order to dispatch. > Another reason, not stated, to ask about an event driven parser > with user supplied type extensions was to learn how this can > be done without dispatching calls on subprograms not known > by the author of the parser (and possibly back). This design pattern is not related to either final methods or re-dispatch. > (Calling user supplied prim ops might become a problem if > some bug (even a misuse) will make parties blame each > other. Calling any operation can. Dispatching call is no less or more safe than a non-dispatching one [*, **] * Assuming that dispatch may not fail ** Re-dispatching call is unsafe and relies on luck -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de