From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-65-14.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!aioe.org!l6SSJpCTNdcdYkpTNEWC9Q.user.46.165.242.91.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: New aggregates with Ada 2022. Date: Tue, 21 Jun 2022 00:18:01 +0200 Organization: Aioe.org NNTP Server Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: gioia.aioe.org; logging-data="25833"; posting-host="l6SSJpCTNdcdYkpTNEWC9Q.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org"; User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-US Xref: reader02.eternal-september.org comp.lang.ada:64003 List-Id: On 2022-06-20 23:47, Randy Brukardt wrote: > The reason for this is obvious in your question: it is ambiguous if an > aggregate is an array aggregate or a container aggregate wherever the full > type is visible, and that is not worth making work (any choice would be a > surprise in some contexts). I don't agree that making the language regular does not worth work. The choice is obviously inconsistent with handling both existing cases: 1. Built-in operations -> hiding: type T is private; function "+" (Left, Right : T) return T; -- Perfectly legal private type T is range 1..100; 2. Primitive operations -> overriding. What's good for the goose is good for the gander? Nope. Here is a totally new way of handling an operation! -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de