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-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,195bd8ec4227e968 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-02-11 10:41:56 PST Path: archiver1.google.com!news2.google.com!news.maxwell.syr.edu!eusc.inter.net!cs.tu-berlin.de!uni-duisburg.de!not-for-mail From: Georg Bauhaus Newsgroups: comp.lang.ada Subject: Re: [Q] non-limited record and "self-pointer" Date: Wed, 11 Feb 2004 18:41:56 +0000 (UTC) Organization: GMUGHDU Message-ID: References: <86d68pl0tc.fsf@sonnenregen.at.home> NNTP-Posting-Host: l1-hrz.uni-duisburg.de X-Trace: a1-hrz.uni-duisburg.de 1076524916 28797 134.91.1.34 (11 Feb 2004 18:41:56 GMT) X-Complaints-To: usenet@news.uni-duisburg.de NNTP-Posting-Date: Wed, 11 Feb 2004 18:41:56 +0000 (UTC) User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (HP-UX/B.11.00 (9000/800)) Xref: archiver1.google.com comp.lang.ada:5445 Date: 2004-02-11T18:41:56+00:00 List-Id: Robert I. Eachus wrote: : Stephen Leake wrote: : : :> This definitely looks like a compiler bug. Perhaps because Container :> is tagged, Read_Only_Set is being labeled "aliased". But that's not in :> the ARM. : : I don't see that. 3.10(9) says in part: "Finally, the current instance : of a limited type, and a formal parameter or generic formal object of a : tagged type are defined to be aliased." Thanks for the answers. Still I wonder what is going on here. In Dan Eilers' example there is no parameter. It is just the Controlled component which seems to make the compiler happy. If the "container" component is replaced with a component of some tagged type other than one derived from Controlled, the self reference is not allowed, according to the compiler. Am I missing something? -- Georg