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=-0.3 required=5.0 tests=BAYES_00, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: "G.B." Newsgroups: comp.lang.ada Subject: Safety of user-defined operators (was: Ada Successor Language) Date: Sun, 3 Jun 2018 09:39:29 +0200 Organization: A noiseless patient Spider Message-ID: References: <5e86db65-84b9-4b5b-9aea-427a658b5ae7@googlegroups.com> Reply-To: nonlegitur@notmyhomepage.de Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Sun, 3 Jun 2018 07:39:30 -0000 (UTC) Injection-Info: h2725194.stratoserver.net; posting-host="1a955272ce1a040b58e2a7d4e23fdbc0"; logging-data="29856"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1++ejCdCSG/9Gg6e5NlXbbycJ8hKDZjcMU=" User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 Cancel-Lock: sha1:5s+h3tIwbj8N4eowkSs+jEwGK6c= In-Reply-To: Content-Language: de-DE Xref: reader02.eternal-september.org comp.lang.ada:52868 Date: 2018-06-03T09:39:29+02:00 List-Id: On 02.06.18 14:43, Dmitry A. Kazakov wrote: > It is semantically problematic because it limits the implementation or forces a wrong implementation in case of temporal, volatile, shared objects. A special operator would allow implementation via proper procedure. > > It is analogous to automatic dereferencing and indexing. There will be no solution to until these operations will be done via user-defined procedure. No number of kludges and obscure helper type will ever work. Assignment is no different. > What set of guarantees can user-defined Ada offer, in comparison, when users will provide those operations to the compiler that are now guarandteed by the language? (Where to "draw the line"?) Example: - typed, indexed RAM (array), as opposed to - typed, indexed data structure (user defined).