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-Thread: 103376,5bcc293dc5642650
X-Google-NewGroupId: yes
X-Google-Attributes: gida07f3367d7,domainid0,public,usenet
X-Google-Language: ENGLISH,UTF8
Received: by 10.68.46.193 with SMTP id x1mr2298766pbm.7.1318935726629;
        Tue, 18 Oct 2011 04:02:06 -0700 (PDT)
Path: 
 d5ni26623pbc.0!nntp.google.com!news2.google.com!goblin1!goblin2!goblin.stu.neva.ru!aioe.org!.POSTED!not-for-mail
From: =?utf-8?Q?Yannick_Duch=C3=AAne_=28Hibou57?=
 =?utf-8?Q?=29?=
 <yannick_duchene@yahoo.fr>
Newsgroups: comp.lang.ada
Subject: Re: Why no Ada.Wide_Directories?
Date: Tue, 18 Oct 2011 13:02:05 +0200
Organization: Ada @ Home
Message-ID: <op.v3jnlrgkule2fv@index.ici>
References: <9937871.172.1318575525468.JavaMail.geo-discussion-forums@prib32>
 <418b8140-fafb-442f-b91c-e22cc47f8adb@y22g2000pri.googlegroups.com>
 <j7i6va$nso$1@munin.nbi.dk> <op.v3i09evqule2fv@index.ici>
 <6e2c9988-cccc-4d07-9e4f-930d58f4fddb@s7g2000prh.googlegroups.com>
 <op.v3jkg1a3ule2fv@index.ici>
 <5e78c23c-088b-4447-9708-b69c37f621f3@27g2000prq.googlegroups.com>
NNTP-Posting-Host: KHj9AOPOidgt0YptnGtG5g.user.speranza.aioe.org
Mime-Version: 1.0
X-Complaints-To: abuse@aioe.org
User-Agent: Opera Mail/11.51 (Linux)
X-Notice: Filtered by postfilter v. 0.8.2
Xref: news2.google.com comp.lang.ada:14040
Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes
Content-Transfer-Encoding: Quoted-Printable
Date: 2011-10-18T13:02:05+02:00
List-Id: <comp.lang.ada>

Le Tue, 18 Oct 2011 12:52:01 +0200, ytomino <aghia05@gmail.com> a =C3=A9=
crit:
> 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  =

sources (back to 1999 and 2000), this was implemented with UTF-8 for  =

memory efficiency. May be its successor, SmartEiffel, less memory  =

efficient, was different. Has underlined by Dmitry, the best way is to s=
ee  =

it as a sequence of code points, as you first said, indeed (although  =

directly mappable to code points, UTF-32, still formally refers to an  =

encoding, although a straight and direct encoding=E2=80=A6 but don't min=
d, that's  =

just a detail).

-- =

=E2=80=9CSyntactic sugar causes cancer of the semi-colons.=E2=80=9D  [Ep=
igrams on  =

Programming =E2=80=94 Alan J. =E2=80=94 P. Yale University]
=E2=80=9CStructured Programming supports the law of the excluded muddle.=
=E2=80=9D [Idem]
Java: Write once, Never revisit