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 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!gandalf.srv.welterde.de!news.jacob-sparre.dk!loke.jacob-sparre.dk!pnx.dk!.POSTED!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: UTF-8 Output and "-gnatW8" Date: Tue, 29 Mar 2016 17:35:20 -0500 Organization: JSA Research & Innovation Message-ID: References: <35689862-61dc-4186-87d3-37b17abed5a2@googlegroups.com> <3a65e71c-41ee-49eb-916d-c0be8be9abc6@googlegroups.com> <6406289c-06a8-46d1-a633-8a1c8a22f79b@googlegroups.com> NNTP-Posting-Host: rrsoftware.com X-Trace: loke.gir.dk 1459290921 29406 24.196.82.226 (29 Mar 2016 22:35:21 GMT) X-Complaints-To: news@jacob-sparre.dk NNTP-Posting-Date: Tue, 29 Mar 2016 22:35:21 +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.6157 Xref: news.eternal-september.org comp.lang.ada:29920 Date: 2016-03-29T17:35:20-05:00 List-Id: "Michael Rohan" wrote in message news:6406289c-06a8-46d1-a633-8a1c8a22f79b@googlegroups.com... ... >It does, however, feel like there is something missing where it's >"difficult" to have >a Wide_String literal without having to have extra meta data for compiler >(-gnatW8) >or having a relatively cumbersome concatenation of Wide_Character's based >on >code points. BTW, the performance of GNAT for such a concatenated string >is >pretty dismal. Both of these are clearly implementation issues as opposed to language issues. The language standard can have nothing to say about what incantation it takes to compile a program, and how one identifies the source format is just a small part of that. (As I previously said, a new compiler would probably make UTF-8 format the default, but changing the default on an existing compiler could cause trouble for many existing customers - I wouldn't expect such a change to be made lightly.) Usability of a compiler is completely out of bounds for a language standard (*any* language standard). (Janus/Ada doesn't support character values > 255 in any format; it still conforms to the older Ada Standards.) And performance, of course, is clearly an implementation issue. (I also would be quite surprised if that was an issue for truly constant strings. I could see how it might be an issue if part of the string is calculated from some variable, but since Ada defines and requires static strings in some circumstances, an Ada compiler has the machinery to avoid any runtime costs for static string expressions.) In any case, GNAT /= Ada. Randy.