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: backlog4.nntp.dca3.giganews.com!border4.nntp.dca.giganews.com!border2.nntp.dca.giganews.com!nntp.giganews.com!news.snarked.org!us.feeder.erje.net!feeder.erje.net!eu.feeder.erje.net!ecngs!feeder2.ecngs.de!217.188.199.168.MISMATCH!takemy.news.telefonica.de!telefonica.de!newsfeed.arcor.de!newsspool3.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Thu, 27 Mar 2014 11:54:24 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Your wish list for Ada 202X References: <7f1c01c5-3563-4b94-9831-152dbbf2ecdc@googlegroups.com> <206rutb9pqak$.11a3dufqvmrm4.dlg@40tude.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <53340361$0$22624$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 27 Mar 2014 11:54:25 CET NNTP-Posting-Host: d26f7681.newsspool1.arcor-online.net X-Trace: DXC=; [DUO9ZmI?oEic==]BZ:afN4Fo<]lROoRAFl8W>\BH3YBoGVDoLO5_QO; 9OJDO8_SKFNSZ1n^B98iJ_5GM6_^Q_]C X-Complaints-To: usenet-abuse@arcor.de Xref: number.nntp.dca.giganews.com comp.lang.ada:185371 Date: 2014-03-27T11:54:25+01:00 List-Id: On 27/03/14 09:26, Dmitry A. Kazakov wrote: > Though, isn't it so that Ada-Comment and AI are meant to be > unwelcoming in order to filter traffic? comp.lang.ada could act as a filter and also as a place to get feedback first, before suggesting something on Ada-Comment. Since the Ada situation is such that one Ada vendor _is_ working on integrating Ada and Parasail, I imagine that not every suggestion WRT Ada is scrutinized with the help of the backwards compatibility sledgehammer only. Let me try one example that is about object construction: (a)compilers diagnose when a variable is used before initialization; (b) limited (derived) types do not have certain constructors that work up the derivation hierarchy; (c) construction then requires C-style discipline lest it be forgotten, possibly leading to erroneous execution. Then, ignoring the foreseeable backwards compatibility sledgehammer for the moment; also ignoring the C-style questionimg about how this is a real, pressing need of competent programmers blah-blah, I'll ask: Can there be a language rule that requires detection of initialization of all parts of said object before use? Is it worth it? Is it simple? Is it elegant? Is it explicit enough?