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.1 required=5.0 tests=BAYES_00,PDS_OTHER_BAD_TLD autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,6aa1ec264ce25142 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.66.74.40 with SMTP id q8mr1096120pav.19.1346366049398; Thu, 30 Aug 2012 15:34:09 -0700 (PDT) Received: by 10.66.84.38 with SMTP id v6mr1175018pay.7.1346366049072; Thu, 30 Aug 2012 15:34:09 -0700 (PDT) Received: by 10.68.134.129 with SMTP id pk1mr1455214pbb.13.1346366049054; Thu, 30 Aug 2012 15:34:09 -0700 (PDT) Path: a5ni27412pbv.0!nntp.google.com!news2.google.com!4no29650311pbn.1!news-out.google.com!t10ni131547224pbh.0!nntp.google.com!r4no6841682pbs.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Thu, 30 Aug 2012 15:34:08 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=66.126.103.122; posting-account=duW0ogkAAABjRdnxgLGXDfna0Gc6XqmQ NNTP-Posting-Host: 66.126.103.122 References: <1p5r39cusgc1n$.18nj9sytckk6$.dlg@40tude.net> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: Real syntax problems in Ada From: Adam Beneschan Injection-Date: Thu, 30 Aug 2012 22:34:09 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Date: 2012-08-30T15:34:08-07:00 List-Id: On Thursday, August 30, 2012 3:06:41 PM UTC-7, (unknown) wrote: > On Tuesday, August 28, 2012 4:13:02 AM UTC-4, Dmitry A. Kazakov wrote: >=20 > > What are real problems with Ada syntax as opposed to the imaginary ones >=20 >=20 >=20 > Not that it's a syntax problem, but I've always been suprised by the choi= ce to use 'all' to explicitly dereference an access value; I don't think a = casual reader of the langauge would be able to guess what it does. It makes some sense if A is an access to a record; then you can say A.abc f= or component "abc" in the record, A.xyz for component xyz, and A.all for th= e whole thing, i.e. all components. Of course, to be consistent, that woul= d mean that if A were an access to an array, we'd use A(2) for the index=3D= 2 element, A(2..5) to refer to a slice of the array, and A(all) to refer to= the entire array. Oh well. -- Adam