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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,70414f56d810c10c X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.12.67 with SMTP id w3mr119949pbb.3.1316554747711; Tue, 20 Sep 2011 14:39:07 -0700 (PDT) Path: lh7ni1370pbb.0!nntp.google.com!news1.google.com!postnews.google.com!d14g2000yqb.googlegroups.com!not-for-mail From: ytomino Newsgroups: comp.lang.ada Subject: Re: discriminant questions Date: Tue, 20 Sep 2011 14:39:07 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <9f37b726-d80b-4d24-bf3f-28a14255f7fd@s20g2000yql.googlegroups.com> <86015926-d652-4265-aedd-413312d399f9@dq7g2000vbb.googlegroups.com> <0d272f62-67d0-4905-972c-8a7e912c5531@en1g2000vbb.googlegroups.com> NNTP-Posting-Host: 118.8.62.179 Mime-Version: 1.0 X-Trace: posting.google.com 1316554747 21160 127.0.0.1 (20 Sep 2011 21:39:07 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 20 Sep 2011 21:39:07 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: d14g2000yqb.googlegroups.com; posting-host=118.8.62.179; posting-account=Mi71UQoAAACnFhXo1NVxPlurinchtkIj User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HNKUARELSC X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.163 Safari/535.1,gzip(gfe) Xref: news1.google.com comp.lang.ada:18056 Content-Type: text/plain; charset=ISO-8859-1 Date: 2011-09-20T14:39:07-07:00 List-Id: Thank you for your suggestion. I'm reading AARM now... For the first time, I got to know the difference between "access discriminant" and a normal discriminant having named access type. I am surprised at that a normal discriminant having named access type can have default and is able to assignment. But, in RM 4.1 (5 (2/3)), "This aspect is specified by a name that denotes an access discriminant declared for the type T."...It seems that a normal discriminant having named access type can not be Implicit_Dereferene... Close! It's regrettable. Back to the subject, lifetime of coextension, It's interesting. Coextension probably is one of the reason that objects with access discriminant can never allow them to be changed. However, I have not resulted in firm belief yet. As another reason, default of "access discriminant" has been used for discriminating which a formal limited type in generic is really(immutably) limited or non-limited since Ada 95. "immutably limited" concept is used widely. (Therefore it is hard to change this rule.) Is my understanding right...? I have not been found the reason about accessibility check yet. I'm going to read RM 3.10.2 and AI95-00230-01 at next.