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 Path: border2.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "G.B." Newsgroups: comp.lang.ada Subject: Re: Quick question regarding limited type return syntax Date: Mon, 04 Aug 2014 18:51:47 +0200 Organization: A noiseless patient Spider Message-ID: References: <166aaec5-5e9c-40e0-9b07-9b9c7d5f7f33@googlegroups.com> <16a6846f-2964-438a-ab9b-2029075f7924@googlegroups.com> <20m59uxjlygw$.2mpabkt469vp.dlg@40tude.net> <1ge2ly0v5yk8d.j8pd98xg0o8v.dlg@40tude.net> Reply-To: nonlegitur@futureapps.de Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 4 Aug 2014 16:51:47 +0000 (UTC) Injection-Info: mx05.eternal-september.org; posting-host="b96887e80893c84a90c3007226ca0d1c"; logging-data="3483"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18PVZRD7mlsy+ijEAM0BaRoW+CB9L4+TZU=" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 In-Reply-To: Cancel-Lock: sha1:ulVIaxWFj9QBRjqz8sneIBsaiww= Xref: number.nntp.dca.giganews.com comp.lang.ada:188148 Date: 2014-08-04T18:51:47+02:00 List-Id: On 04.08.14 18:38, Dmitry A. Kazakov wrote: > How can you call an operation of the type on an object of this type when > the former is not yet operational? In a way that is somewhat like you say, namely on a partial object when it is needed only partially: T.comp_1: allocated and possibly initialized S.comp_2: not even allocated overriding procedure Foo (X : in out S) is begin null; end Foo; may "validly" become: alloc comp_1 jump s.foo s.foo: ret Lousy, but it may "work", even when, without optimization, some "non-existing junk" is copied for X (if it's not by ref). Not that I want that! Just imagine the outcome should the arbitrary location happen to be volatile…