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: a07f3367d7,8e11100f675ea2df X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit X-Received: by 10.66.80.200 with SMTP id t8mr12803018pax.1.1357928003027; Fri, 11 Jan 2013 10:13:23 -0800 (PST) Path: s9ni102089pbb.0!nntp.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!newsfeed.news.ucla.edu!news.snarked.org!feeder.erje.net!us.feeder.erje.net!news2.arglkargh.de!news.swapon.de!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: Jeffrey Carter Newsgroups: comp.lang.ada Subject: Re: asynchronous task communication Date: Tue, 08 Jan 2013 14:01:51 -0700 Organization: Also freenews.netfront.net; news.tornevall.net Message-ID: References: <1c2dnd5E6PMDR33NnZ2dnUVZ_sednZ2d@earthlink.com> <50e18094$0$6583$9b4e6d93@newsspool3.arcor-online.net> <7NednS4s2oukfXzNnZ2dnUVZ_oadnZ2d@earthlink.com> <7cudnYloBfQDw3_NnZ2dnUVZ_rKdnZ2d@earthlink.com> <6bqdndEYjoxeGHnNnZ2dnUVZ_sadnZ2d@earthlink.com> Mime-Version: 1.0 Injection-Date: Tue, 8 Jan 2013 21:01:53 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="656ea2f23126f57fb36504d2d15a002c"; logging-data="9511"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Ic4K4H5VFpLpegCSt74MOW6ECQl+1n2k=" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 In-Reply-To: Cancel-Lock: sha1:M7pQBy2RdPcJIdAJYkUZv4eSQvc= Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Date: 2013-01-08T14:01:51-07:00 List-Id: On 01/08/2013 11:18 AM, Simon Wright wrote: > Jeffrey Carter writes: > >> If you have an item in your (unbounded) array, indexed by Positive, at >> index 3, it will still be at index 3 if you assign to components at >> other indices, or extend the array by adding new components beyond the >> current end of the array. However, if you insert a new component >> before the existing item at index 3, then all the components after the >> new component will shift up, and the existing item will then be at >> index 4. >> >> One would think that a Cursor would behave similarly. > > Not so! The Cursor becomes ambiguous[1], and using it is a bounded > error. GNAT GPL 2012 implements Cursor using an Index, & behaves the way > you'd expect. To my mind, that is Cursor behaving similarly. Just as the index 3 is no longer the index of the item in question, so the Cursor should not be relied on. -- Jeff Carter "Whatever it is, I'm against it." Horse Feathers 46