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,bcb6f63419c2a56b X-Google-Attributes: gid103376,public Path: controlnews3.google.com!news1.google.com!news.glorb.com!wn12feed!worldnet.att.net!bgtnsc05-news.ops.worldnet.att.net.POSTED!not-for-mail From: David Starner Subject: Re: Supporting full Unicode User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux)) Message-Id: Newsgroups: comp.lang.ada References: <9j8oc.16324$V97.13312@newsread1.news.pas.earthlink.net> <2004512-94456-948110@foorum.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Date: Wed, 12 May 2004 09:41:09 GMT NNTP-Posting-Host: 12.72.72.3 X-Complaints-To: abuse@worldnet.att.net X-Trace: bgtnsc05-news.ops.worldnet.att.net 1084354869 12.72.72.3 (Wed, 12 May 2004 09:41:09 GMT) NNTP-Posting-Date: Wed, 12 May 2004 09:41:09 GMT Organization: AT&T Worldnet Xref: controlnews3.google.com comp.lang.ada:469 Date: 2004-05-12T09:41:09+00:00 List-Id: On Wed, 12 May 2004 07:44:56 +0000, Ludovic Brenta wrote: > > Brian Catlin asked: >> The complete definition of Unicode allows for 2-,3-, and 4-byte >> characters. How is this supported in Ada95 and Ada0y? > > I am not aware of any differences between Ada 95 and Ada 2005 in that > respect. Ada 95 has a type Wide_Character, "whose values correspond > to the 65536 code positions of the ISO 10646 Basic Multilingual Plane > (BMP)." (RM 3.5.2(3)). Ada 2005 is apparently going to have a Wide_Wide_Character for full Unicode. That's unfortunate; they should have defined Wide_Character to be UTF-16 like Java did. Besides taking less space and hence often being faster, this move leaves a Wide_Character that should never be used but will anyway. (No, I don't care if you don't use those characters; one of the people using your program will be an archaeologist who wants to transfer his Unicode data from another program to yours, and will be rather annoyed that your "Unicode" program doesn't support perfectly valid Unicode data.)