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 X-Received: by 2002:aed:254c:: with SMTP id w12mr90379241qtc.127.1560643180706; Sat, 15 Jun 2019 16:59:40 -0700 (PDT) X-Received: by 2002:a05:6830:18a:: with SMTP id q10mr12830749ota.114.1560643180282; Sat, 15 Jun 2019 16:59:40 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!news.gegeweb.eu!gegeweb.org!usenet-fr.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!j96no2556711qte.0!news-out.google.com!33ni276qtt.0!nntp.google.com!j96no2556707qte.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 15 Jun 2019 16:59:40 -0700 (PDT) Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=174.23.151.147; posting-account=tfeRYAoAAACibzLrD_Ytyp0eQjMq_Py9 NNTP-Posting-Host: 174.23.151.147 User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <728c4668-8fa0-4a57-a502-2bf476fc3940@googlegroups.com> Subject: Latest suggestion for 202x From: Micah Waddoups Injection-Date: Sat, 15 Jun 2019 23:59:40 +0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Xref: reader01.eternal-september.org comp.lang.ada:56640 Date: 2019-06-15T16:59:40-07:00 List-Id: Following is my comment of appreciation AND my suggestion that is a very ba= sic and important level of support for Unicode. Frankly, the former rules for directly specifying the contents of an array = were perfect, when you can only use parenthesis. Being able to use square = brackets to improve the readability of an array is brilliant because it is = familiar to those who use other languages and it does very little to change= what is already part of the language definition (square brackets are alrea= dy use in a way that does not conflict). Therefore, it is not confusing, j= ust new. As for the other uses, I can't fully wrap my head around it, because I don'= t have time to study that part yet. I have a suggestion, and I am sorry I haven't searched thoroughly to see if= someone has suggested this already, though I don't believe they have. Uni= code and UTF are supported very well, however, the support is simply limite= d to the packages starting at Ada.Strings.UTF_Encoding. There is no connec= tion to Character_Set found in Maps. Since many lines of code are designed= around the traditional Character_Set in Ada.Strings, the categories of UTF= should be conveyable as a (Wide_+)Character_Set so that the much existing = code does not have to be fundamentally or completely redesigned in order to= use the support to Unicode. Please consider making Unicode categories ava= ilable as character_sets (obviously omitting any characters from a category= that are out of the range of the string, such as String, sans block drawin= g, vs. Wide_String, with block drawing). If the character_set support for Unicode is not included in the pre-built s= tandard libraries, then it will be much elaboration and unnecessary code to= try to implement it correctly. Does anybody agree or disagree with this very simple, but very impactful su= ggestion?