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.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,5bcc293dc5642650 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,CP1252 Received: by 10.68.21.229 with SMTP id y5mr4450552pbe.1.1318972833337; Tue, 18 Oct 2011 14:20:33 -0700 (PDT) Path: d5ni28916pbc.0!nntp.google.com!news2.google.com!postnews.google.com!h39g2000prh.googlegroups.com!not-for-mail From: ytomino Newsgroups: comp.lang.ada Subject: Re: Why no Ada.Wide_Directories? Date: Tue, 18 Oct 2011 14:18:37 -0700 (PDT) Organization: http://groups.google.com Message-ID: <17fa7523-7acd-44a9-aff7-f98ef9551553@h39g2000prh.googlegroups.com> References: <9937871.172.1318575525468.JavaMail.geo-discussion-forums@prib32> <418b8140-fafb-442f-b91c-e22cc47f8adb@y22g2000pri.googlegroups.com> <6e2c9988-cccc-4d07-9e4f-930d58f4fddb@s7g2000prh.googlegroups.com> <5e78c23c-088b-4447-9708-b69c37f621f3@27g2000prq.googlegroups.com> NNTP-Posting-Host: 118.6.135.155 Mime-Version: 1.0 X-Trace: posting.google.com 1318972833 3225 127.0.0.1 (18 Oct 2011 21:20:33 GMT) X-Complaints-To: groups-abuse@google.com NNTP-Posting-Date: Tue, 18 Oct 2011 21:20:33 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: h39g2000prh.googlegroups.com; posting-host=118.6.135.155; posting-account=Mi71UQoAAACnFhXo1NVxPlurinchtkIj User-Agent: G2/1.0 X-Google-Web-Client: true X-Google-Header-Order: HNKUARELSC X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_5_8) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1,gzip(gfe) Xref: news2.google.com comp.lang.ada:14065 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Date: 2011-10-18T14:18:37-07:00 List-Id: On Oct 18, 8:02=A0pm, Yannick Duch=EAne (Hibou57) wrote: > Le Tue, 18 Oct 2011 12:52:01 +0200, ytomino a =E9crit= :> OK, I've understood. > > But, UNICODE_STRING is usually not called "UTF-8 string". Because the > > content is decoded. > > UNICODE_STRING seems just array of UCS-32 code points to me. It's > > called "UTF-32 string" commonly. > > (It's same as that Wide_Wide_String is not called UTF-8 string.) > > If my mind is still right since the time I get into SmallEiffel compiler'= s =A0 > sources (back to 1999 and 2000), this was implemented with UTF-8 for =A0 > memory efficiency. May be its successor, SmartEiffel, less memory =A0 > efficient, was different. Has underlined by Dmitry, the best way is to se= e =A0 > it as a sequence of code points, as you first said, indeed (although =A0 > directly mappable to code points, UTF-32, still formally refers to an =A0 > encoding, although a straight and direct encoding=85 but don't mind, that= 's =A0 > just a detail). > > -- > =93Syntactic sugar causes cancer of the semi-colons.=94 =A0[Epigrams on = =A0 > Programming =97 Alan J. =97 P. Yale University] > =93Structured Programming supports the law of the excluded muddle.=94 [Id= em] > Java: Write once, Never revisit Fuckin' great! I downloaded and searched SmartEiffel's UNICODE_STRING.e. It has two arrays of UTF-16 values. UTF-16 array *A* has UCS-2 characters or first halfs of surrogate pair. UTF-16 array *B* has second halfs of surrogate pair. *B* is never allocated without it's required to hold a surrogate pair at least. It's certain that memory efficient and its calculation order is not increased. (This string is not my liking, but interesting!)