From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.5-pre1 Path: eternal-september.org!reader02.eternal-september.org!aioe.org!yy9MKEJN2ULhWGfnfq4v5w.user.gioia.aioe.org.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: GCC 11 bug? lawyer needed Date: Thu, 06 May 2021 21:02:54 +0100 Organization: Aioe.org NNTP Server Message-ID: References: NNTP-Posting-Host: yy9MKEJN2ULhWGfnfq4v5w.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain X-Complaints-To: abuse@aioe.org User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (darwin) Cancel-Lock: sha1:D6cPxI+jcXzrMQKk9hhB32oQeO0= X-Notice: Filtered by postfilter v. 0.9.2 Xref: reader02.eternal-september.org comp.lang.ada:61962 List-Id: "Randy Brukardt" writes: > I agree that the original author of that program should not have used > "aliased" in the way that they did (they don't need the special semantics), > but we realize that some people would prefer to *explicitly* mark things as > aliased when they are going to take 'Access (and not worry about the type of > the parameter -- after all, it could change). That is, they don't want to > depend on the implicit behavior of tagged types -- or perhaps they don't > even know about it. Which leads to the problem that occurs here, as > "aliased" has slightly different meanings for functions (now just composite > functions) and procedures. The original code, from the Alire project, had (I've edited it slightly) package Holders is new Ada.Containers.Indefinite_Holders (Node'Class); type Tree is new Holders.Holder and ... function Root (This : Tree) return Node'Class is (This.Constant_Reference); where that Constant_Reference is inherited (eventually) from Ada.Containers.Indefinite_Holders.Holder, function Constant_Reference (Container : aliased Holder) return Constant_Reference_Type; pragma Inline (Constant_Reference); Shame it had to be there. I've just tried splattering 'aliased' wherever the compiler told me it was needed; it's now spreading into other packages. Ugh. The solution might just be using composition rather than inheritance.