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!feeder.eternal-september.org!news.unit0.net!news.uni-stuttgart.de!news-1.dfn.de!news.dfn.de!news.uni-weimar.de!medsec1.medien.uni-weimar.de!slucks
From: Stefan.Lucks@uni-weimar.de
Newsgroups: comp.lang.ada
Subject: Re: Latest suggestion for 202x
Date: Mon, 24 Jun 2019 13:12:54 +0200
Organization: Bauhaus-Universitaet Weimar
Message-ID: <alpine.DEB.2.21.1906241248220.27033@hexenstieg>
References: <86h88obeu0.fsf@gaheris.avalon.lan>
 <39e749cd-de5c-44fa-b8ec-50d36f3bd52c@googlegroups.com>
 <qe8b41$pji$1@gioia.aioe.org> <lnef3rnb8d.fsf@kst-u.example.com>
 <qeh0sh$3rd$1@franka.jacob-sparre.dk> <qei8ps$nec$1@gioia.aioe.org>
 <lnd0j6kdsl.fsf@kst-u.example.com>
 <qej8gm$1b40$1@gioia.aioe.org> <ln8stuk7pu.fsf@kst-u.example.com>
 <qekjbb$vu0$1@gioia.aioe.org> <lnr27likgv.fsf@kst-u.example.com>
 <e81c87e1-8090-45e4-892b-ea62585f4a38@googlegroups.com>
 <ehdvgepli93bqfiisllgca27350n3nledo@4ax.com>
 <qeplr0$bk1$1@dont-email.me>
NNTP-Posting-Host: medsec1.medien.uni-weimar.de
Mime-Version: 1.0
Content-Type: multipart/mixed;
 boundary="915268786-544897357-1561374775=:27033"
X-Trace: pinkpiglet.scc.uni-weimar.de 1561374776 25552 141.54.178.228 (24 Jun
 2019 11:12:56 GMT)
X-Complaints-To: news@pinkpiglet.scc.uni-weimar.de
NNTP-Posting-Date: Mon, 24 Jun 2019 11:12:56 +0000 (UTC)
X-X-Sender: slucks@hexenstieg
In-Reply-To: <qeplr0$bk1$1@dont-email.me>
User-Agent: Alpine 2.21 (DEB 202 2017-01-01)
Xref: reader01.eternal-september.org comp.lang.ada:56730
Date: 2019-06-24T13:12:54+02:00
List-Id: <comp.lang.ada>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--915268786-544897357-1561374775=:27033
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

> The principle for any decent language is that if two identifiers mean=20
> the same thing in the brain of the reader, then they must correspond to=
=20
> the same entity. And the meaning of a word is not changed by casing.

Do you really think so?

I think, the capical 'I' is very different from i=3Dsqrt(-1).  ;-)

To be honest, I agreee that Ada should not adapt the concept of many other=
=20
case-sensitive languages that capitalization (such as changing between 'I'=
=20
and 'i') gives you two different identifiers, to be used interchangeably.

On the other hand, I would prefer the compiler to require a consistent=20
casing. E.g., if you define an identifier "Ada", you are not allowed to=20
spell the same identifier as "ADA", "ada", "aDa", ... anywhere else.

Or consider

   procedure P(Value: Integer) is ...
   ...

   declare
     i: Integer :=3D 0;
   begin
     declare
       I: Integer :=3D 1;
     begin
       P(i); -- DOES call P(1) in Ada, since Ada is
             --      not case-sensitive
             -- WOULD call P(0) in most other modern languages,
             --       which usually have case-sensitive identifiers
             -- SHOULD be treated as an error, because "i" and "I"
             --        are *different* identifiers, nevertheless "i"
             --        has been hidden by  "I".
      end;
   end;


--------  I  love  the  taste  of  Cryptanalysis  in  the morning!  -------=
-
www.uni-weimar.de/de/medien/professuren/mediensicherheit/people/stefan-luck=
s
----Stefan.Lucks (at) uni-weimar.de, Bauhaus-Universit=C3=A4t Weimar, Germa=
ny----

--915268786-544897357-1561374775=:27033--