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,673d883a7001e192 X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!postnews.google.com!g12g2000prg.googlegroups.com!not-for-mail From: "Y.Tomino" Newsgroups: comp.lang.ada Subject: Re: Pure, Storage_Size and Unchecked_Conversion Date: Sun, 15 Jul 2007 10:30:29 -0700 Organization: http://groups.google.com Message-ID: <1184520629.360909.36040@g12g2000prg.googlegroups.com> References: <1183854255.792142.110150@i38g2000prf.googlegroups.com> NNTP-Posting-Host: 219.97.90.86 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: posting.google.com 1184520629 6046 127.0.0.1 (15 Jul 2007 17:30:29 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Sun, 15 Jul 2007 17:30:29 +0000 (UTC) In-Reply-To: User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: g12g2000prg.googlegroups.com; posting-host=219.97.90.86; posting-account=ps2QrAMAAAA6_jCuRt2JEIpn5Otqf_w0 Xref: g2news1.google.com comp.lang.ada:16478 Date: 2007-07-15T10:30:29-07:00 List-Id: On Jul 10, 10:35 am, "Randy Brukardt" wrote: > You've gotten a whole bunch of answers, but I think the correct one has not > be provided: > it is a compiler bug and there should not be an error at F2. Thank you, the situation became clear for me. I was looking for the cause and found the correction point of gcc. sem_ch3.adb -------------- if Comes_From_Source (Id) and then In_Pure_Unit and then not In_Subprogram_Task_Protected_Unit + and then not No_Pool_Assigned (T) then Error_Msg_N ("named access types not allowed in pure unit", N); ---------------- The compiler after changing passes the above-mentioned code though I do not understand whether my correction is correct. > I'd suggest that you (and others as well) should ask the people at AdaCore > about what appear to be compiler bugs (especially in things changed by the > Amendment, which are highly likely to be buggy as they are new) rather than > confusing many with examples that seem to show non-existent limitations of > Ada (as opposed to a particular compiler). OTOH, if you don't have an > AdaCore contract, you won't get a timely answer from them, but I'd have to > say that you get what you pay for in that case... Oh....I cannot pay the cost so much.