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.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c39ad3e35a7690a9 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,UTF8 Received: by 10.68.136.40 with SMTP id px8mr1407716pbb.1.1329327043529; Wed, 15 Feb 2012 09:30:43 -0800 (PST) Path: wr5ni28684pbc.0!nntp.google.com!news1.google.com!goblin1!goblin.stu.neva.ru!news.visyn.net!visyn.net!news-2.dfn.de!news.dfn.de!news.uni-stuttgart.de!news.belwue.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 15 Feb 2012 18:30:41 +0100 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Convention for naming of packages References: <4f355230$0$21451$ba4acef3@reader.news.orange.fr> <4f3b9a60$0$7627$9b4e6d93@newsspool1.arcor-online.net> <4f3ba604$0$7619$9b4e6d93@newsspool1.arcor-online.net> In-Reply-To: Message-ID: <4f3bebc1$0$7609$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 15 Feb 2012 18:30:41 CET NNTP-Posting-Host: 9a8dbb83.newsspool1.arcor-online.net X-Trace: DXC=6C\C93G9kLL2jYf>V4L0gLic==]BZ:afN4Fo<]lROoRA<`=YMgDjhgBeMA8gLLT@VBnc\616M64>JLh>_cHTX3jM^76[OOCP\8M X-Complaints-To: usenet-abuse@arcor.de Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Date: 2012-02-15T18:30:41+01:00 List-Id: On 15.02.12 13:55, Yannick Duchêne (Hibou57) wrote: >>> Motto: Don't use characters as symbols. > Even symbols may be ambiguous. No one should be afraid of that. If no one is afraid of ambiguity of identifiers, it will cause errors sooner or later. Stupid errors. Pardon my French. The readability of a program's source text obviously should not depend on the choice of font if that font alone makes ambiguity disappear. This kind of witchcraft is good for producing nightmares for the programmers who need to fix the program. > Unicode already provides some data on the different meanings of similar > glyphs, and it does not suggest I vs l (or i vs j with some fonts) is the same > as ∅ vs ø vs ⌀. What do the Unicode data not not suggest? There is not three nots in the preceding sentence.