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.5 required=5.0 tests=BAYES_00, PP_MIME_FAKE_ASCII_TEXT,SUBJECT_NEEDS_ENCODING,SUBJ_ILLEGAL_CHARS autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: a07f3367d7,8ea33c39efc56ac3 X-Google-Attributes: gida07f3367d7,public,usenet X-Google-NewGroupId: yes X-Google-Language: ENGLISH,ASCII Path: g2news2.google.com!news3.google.com!feeder2.cambriumusenet.nl!feed.tweaknews.nl!194.109.133.85.MISMATCH!newsfeed.xs4all.nl!newsfeed6.news.xs4all.nl!xs4all!feeder.news-service.com!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!gegeweb.org!news.ecp.fr!news.jacob-sparre.dk!pnx.dk!jacob-sparre.dk!ada-dk.org!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: sharp � and ss in Ada keywords like ACCESS Date: Mon, 10 Oct 2011 17:25:17 -0500 Organization: Jacob Sparre Andersen Research & Innovation Message-ID: References: <4e931db5$0$6541$9b4e6d93@newsspool4.arcor-online.net> <1f9a5099-f5f5-49a8-8773-b7eaca771427@s5g2000pra.googlegroups.com> <4e93381d$0$6545$9b4e6d93@newsspool4.arcor-online.net> NNTP-Posting-Host: static-69-95-181-76.mad.choiceone.net X-Trace: munin.nbi.dk 1318285520 451 69.95.181.76 (10 Oct 2011 22:25:20 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Mon, 10 Oct 2011 22:25:20 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Original X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 Xref: g2news2.google.com comp.lang.ada:22330 Date: 2011-10-10T17:25:17-05:00 List-Id: "Georg Bauhaus" wrote in message news:4e93381d$0$6545$9b4e6d93@newsspool4.arcor-online.net... ... > I'd think that the simplest of the rules is to make "ss" and "�" > the same, and ask programmers to relax. This has worked in Switzerland > for many, many years. That's what Unicode does. However, that would be incompatible and inconsistent (that is, both compile-time and run-time incompatible) with Ada 95 identifiers. That would not be acceptable. Thus, Ada 2012 uses a simpler rule (Ada 2005 just totally screwed this up, and it has to be ignored). Thus "acce�" /= "access". Also note that even if the conversion was allowed, the identifier "acce�" would be illegal: 2.3(5.3/3) [and the equivalent rule in Ada 2005] makes it illegal to have an identifier that is identical to a reserved word. And reserved words use character-by-character case conversion - any case where the number of characters change is not considered. Since Ada 2012 uses "simple case folding", 2.3(5.3/3) doesn't have any impact, but if it had used "full case folding", it would prevent words like the above. Randy.