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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5cb36983754f64da X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2004-04-17 15:23:41 PST Path: archiver1.google.com!news1.google.com!news.glorb.com!wn13feed!worldnet.att.net!bgtnsc04-news.ops.worldnet.att.net.POSTED!not-for-mail From: David Starner Subject: Re: No call for Ada (was Re: Announcing new scripting/prototyping language) User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux)) Message-Id: Newsgroups: comp.lang.ada References: <20040206174017.7E84F4C4114@lovelace.ada-france.org> <54759e7e.0402071124.322ea376@posting.google.com> <406EB6D2.8030801@noplace.com> <87d66pyw1g.fsf@insalien.org> <406EEC35.7040109@noplace.com> <874qs0zvy1.fsf@insalien.org> <40714C98.90601@noplace.com> <1073gv22t969q5a@corp.supernews.com> <40729B9D.30906@noplace.com> <1076000ef5oj06f@corp.supernews.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: Sat, 17 Apr 2004 22:23:41 GMT NNTP-Posting-Host: 12.72.88.255 X-Complaints-To: abuse@worldnet.att.net X-Trace: bgtnsc04-news.ops.worldnet.att.net 1082240621 12.72.88.255 (Sat, 17 Apr 2004 22:23:41 GMT) NNTP-Posting-Date: Sat, 17 Apr 2004 22:23:41 GMT Organization: AT&T Worldnet Xref: archiver1.google.com comp.lang.ada:7281 Date: 2004-04-17T22:23:41+00:00 List-Id: On Sat, 17 Apr 2004 09:58:09 -0400, Robert I. Eachus wrote: > I was not "dismissing" Unicode outside of the BMP as useless, Referring to Klingon is the standard way of doing that, whether or not you intended it that way. It ignores the real usages for one that often inspires ridicule. > You CAN imbed use of UTF-8 for Ada.Text_IO files in the form string. But > -gnatWa (for various values of a) tells the compiler how to interpret > the character set in the SOURCE file. That is a little difficult to do > in the source file itself. Why would you think that? HTML and XML does it. Unless you're dealing with EBCDIC, you have two encodings to deal with in order to reach a "pragma charset ("UTF-8");": ASCII and UTF-16, which are trivial to distinguish. In any case, using it to distinguish source character set isn't evil. It's using it change the default Text_IO character set, and worse yet, coupling the two, that's bad.