From mboxrd@z Thu Jan 1 00:00:00 1970 Path: eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lioneldraghi Newsgroups: comp.lang.ada Subject: Re: Ichbiah 2022 compiler mode Date: Sat, 21 Dec 2024 01:52:43 +0100 Organization: A noiseless patient Spider Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Sat, 21 Dec 2024 01:52:44 +0100 (CET) Injection-Info: dont-email.me; posting-host="331d1bed6150e4fbb6f2e349fe0f6448"; logging-data="3850016"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+ynO++HeZOD4ovseKdckDFX/DQTTLNeG4=" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:s6IzjkPHtmArgciLYzxmM9RoMnI= In-Reply-To: Content-Language: fr-FR, it-IT, en-US Xref: news.eternal-september.org comp.lang.ada:66495 List-Id: Le 06/09/2024 à 02:03, Randy Brukardt a écrit : > (10) Variable-returning functions are introduced. They're pretty similar the > semantics of anonymous access returns (or the aliased function returns > suggested by Tucker). This means that a variable can easily be treated as a > function (and indeed, a variable declaration is just syntactic sugar for > such a function). I suppose that to allows the compiler to discriminate this non sense code > Square (2) := 3; from the legitimate > List.Index (3) := Item; you will have to introduce some specific syntax, like Tucker's "aliased function". I see the huge benefit from a user point of view, but I'm not aware of compiler internals : doesn't the introduction of a second function type increase complexity?