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 04:31:47 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 11:31:47 GMT NNTP-Posting-Host: 12.72.69.81 X-Complaints-To: abuse@worldnet.att.net X-Trace: bgtnsc04-news.ops.worldnet.att.net 1082201507 12.72.69.81 (Sat, 17 Apr 2004 11:31:47 GMT) NNTP-Posting-Date: Sat, 17 Apr 2004 11:31:47 GMT Organization: AT&T Worldnet Xref: archiver1.google.com comp.lang.ada:7249 Date: 2004-04-17T11:31:47+00:00 List-Id: On Tue, 13 Apr 2004 10:14:25 -0400, Robert I. Eachus wrote: > I think you are confused here. What operating system are you targeting? > And which Ada compiler do you want to use? So we can just toss portability out the window. > The technical decisions that in standard mode, > Character = Latin1, Wide_Character = BMP are just decisions about a > standard default. RM 3.5.2(4) says: "In a nonstandard mode, an > implementation may provide other interpretations for the predefined > types Character and Wide_Character, to conform to local conventions." In a nonstandard mode, an implementation may do anything. > If you need an implementation that maps Wide_Character to Unicode > instead of the BMP, fine. Personally, I have never needed to go outside > the BMP. (Klingon anyone?) Try Hong Kong Chinese. In any case, I've never needed to use 'Storage_Size, but that doesn't mean that I should go around writing programs to process Ada code that doesn't support it. Furthermore, dismissing Unicode outside the BMP as Klingon is offensive and just plain wrong. There's characters for musical notation, for Linear A and B, for Gothic, for Aegean numbers, for a Mormon orthography for English, for Chinese characters for non-Mandarian Chinese or Vietnamese or archaic Chinese, but no characters for Klingon. In fact, the Unicode Consortium has specifically said that Klingon is not suitable for encoding at this time. Let's try dismissing things for technical reasons, instead of the rumors and falsehoods that have been used so many times against Ada. > But as I see > it, that is complaining that you choose the wrong compiler, not the > wrong language. So I can't process plain text, in the modern encoding that the IETF says every new RFC must support by default, in standard Ada; instead I need to be tied to one vendor. > Or you can compile with -gnatW8, which makes UTF-8 the > default representation. I've always found this wrong. Information like this should be embedded in the code, not in the compiler options.