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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: "Alejandro R. Mosteo" Newsgroups: comp.lang.ada Subject: Re: Why are Ada compilers difficult to write ? Date: Mon, 25 Jun 2018 10:51:53 +0200 Organization: A noiseless patient Spider Message-ID: References: <584564c2-9f64-4965-b045-535cdaf899c0@googlegroups.com> <7cb22c58-3009-47f0-8fe7-62f3cd61785d@googlegroups.com> <2d617160-ac33-40e6-a06a-97cc0b53062d@googlegroups.com> <6f103699-811e-45e2-83ee-3b3606239cd8@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 25 Jun 2018 08:51:55 -0000 (UTC) Injection-Info: reader02.eternal-september.org; posting-host="56798da69b8456a859013d3840662c32"; logging-data="20376"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/A7ZBFex5RqsiwAcu7z9xM" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 Cancel-Lock: sha1:znZa6mas/WA2CH3tBnJOxwJHtpI= In-Reply-To: <6f103699-811e-45e2-83ee-3b3606239cd8@googlegroups.com> Content-Language: en-US Xref: reader02.eternal-september.org comp.lang.ada:53291 Date: 2018-06-25T10:51:53+02:00 List-Id: On 23/06/2018 18:14, Shark8 wrote: > On Saturday, June 23, 2018 at 6:44:41 AM UTC-6, Dan'l Miller wrote: >> On Saturday, June 23, 2018 at 12:56:43 AM UTC-5, J-P. Rosen wrote: >>> Le 22/06/2018 à 18:10, Simon Clubley a écrit : >>>> 3.10.2 (according to Randy) >>>> >>>> Personally, I don't think it's something to be proud of however. >>>> >>>> When a language is used in the critical environments that Ada is used in, >>>> it shouldn't have anything in it which is that difficult to understand. >>> >>> Well, it is an attempt at making pointers safer, and this is inherently >>> difficult. Other languages didn't even try... >> >> Except Rust nowadays, and hopefully Ada2020 will catch up > > SPARK is better than Rust in terms of safety/reliability; there was a [possible] proposed extension to SPARK to allow access-types in certain, controlled conditions that was shown to the ARG. (They asked that we not promulgate it, I think because they wanted to publish/present it for their academic career.) It was just presented in Ada-Europe 2018, and they said that it was inspired by Rust borrowing rules. What I find interesting about the Rust approach is that (perhaps by their C-fixing motivation) it addresses something that is not tackled by Ada attempts, so I find it curiously orthogonal. So having something similar in SPARK seems only logical.