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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.236.23.74 with SMTP id u50mr12616789yhu.13.1432933051693; Fri, 29 May 2015 13:57:31 -0700 (PDT) X-Received: by 10.182.97.231 with SMTP id ed7mr83597obb.42.1432933051633; Fri, 29 May 2015 13:57:31 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!z60no4544324qgd.1!news-out.google.com!n7ni47644igk.0!nntp.google.com!h15no222089igd.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Fri, 29 May 2015 13:57:31 -0700 (PDT) In-Reply-To: <87a8wnu3v0.fsf@adaheads.sparre-andersen.dk> Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=67.0.105.201; posting-account=lJ3JNwoAAAAQfH3VV9vttJLkThaxtTfC NNTP-Posting-Host: 67.0.105.201 References: <127b004d-2163-477b-9209-49d30d2da5e1@googlegroups.com> <59a4ee45-23fb-4b0e-905c-cc16ce46b5f6@googlegroups.com> <46b2dce1-2a1c-455d-b041-3a9d217e2c3f@googlegroups.com> <87a8wnu3v0.fsf@adaheads.sparre-andersen.dk> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <288e200f-8379-45b3-8eb7-342564c920ef@googlegroups.com> Subject: Re: Build language with weak typing, then add scaffolding later to strengthen it? From: Shark8 Injection-Date: Fri, 29 May 2015 20:57:31 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Received-Bytes: 3174 X-Received-Body-CRC: 568827107 Xref: news.eternal-september.org comp.lang.ada:26078 Date: 2015-05-29T13:57:31-07:00 List-Id: On Friday, May 29, 2015 at 3:31:33 AM UTC-6, Jacob Sparre Andersen wrote: >=20 > Isn't that in itself an argument for letting Ada 2020 be a major change, > where backwards compatibility isn't as important as using our current > knowledge to improve the language? I wouldn't want an Ada 2012 program > to be accepted by an Ada 2020 compiler with a different meaning, but I > wouldn't mind it if the Ada 2020 compiler told me that I have to do > things differently in Ada 2020. If we accept a breaking change, then we could clean up the [[Wide_]Wide_]Ch= aracter and [[Wide_]Wide_]Strings. -- Randy had an interesting idea about = that a while back (I forget the details though). If we went with a sort of "abstract type" idea we could we could simplify t= he Character/String-packages in the standard library. It might also give us= a chance to look at allowing User-defined attributes... though that might = be a bad idea (I like being able to look any particular attribute up in the= standard Another thing that would be nice is a way to initialize containers in-sourc= e w/o functions -- but overloading the aggregates more than they already ar= e to handle that might be far too much effort for the comparatively little = gain. Also, a way to refer to indices when in an array-aggrigare would be n= ice; Ex: I:Array(1..4,1..4) of Integer :=3D (others =3D> (if I'Index(1) =3D= I'Index(2) then 1 else 0));