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!news.eternal-september.org!feeder.eternal-september.org!aioe.org!.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: State of the compiler market Date: Fri, 30 Jun 2017 09:18:52 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <1813789782.509760763.093426.laguest-archeia.com@nntp.aioe.org> <87varxjouh.fsf@nightsong.com> <250466748.510009784.561340.laguest-archeia.com@nntp.aioe.org> <87fuelzvcq.fsf@jacob-sparre.dk> <4e60ac97-7f4f-47e7-847a-e27983accd4b@googlegroups.com> <57c26106-4e4f-464f-83e9-fe52de614cd7@googlegroups.com> <6529c392-f042-4dfe-8cdb-b785406ad788@googlegroups.com> <8643cc5f-7b09-479f-825d-8060aad7d628@googlegroups.com> NNTP-Posting-Host: vZYCW951TbFitc4GdEwQJg.user.gioia.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Complaints-To: abuse@aioe.org User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Content-Language: en-US X-Notice: Filtered by postfilter v. 0.8.2 Xref: news.eternal-september.org comp.lang.ada:47204 Date: 2017-06-30T09:18:52+02:00 List-Id: On 30/06/2017 07:27, J-P. Rosen wrote: > Le 29/06/2017 à 21:01, Lucretia a écrit : >> There's just so much stuff I need unicode strings for and we just >> don't have good enough support for it. > Well, you have Wide_String if you can stay within the BMP, or > Wide_Wide_String if you need the whole Unicode. There are packages for > character characterization/translation. You have packages for > encoding/decoding UTF8/16/32. What is the extra support you need? Encoding must be a part of the string type. This is essential for dealing with OS/API bindings. E.g. an UTF-8 string must provide a view of an array of octets (for OS/API calls) and a view of an array of code points (for the application). The second view must constitute a class. We don't need explicit conversions between string types. But the point is that the language should not have string types at all. The type system should be capable to define things as described above at the library level. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de