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.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,e136d2bb18e6fb60 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-11-30 06:49:49 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!arclight.uoregon.edu!wn14feed!wn12feed!worldnet.att.net!207.217.77.102!newsfeed2.earthlink.net!newsfeed.earthlink.net!stamper.news.pas.earthlink.net!stamper.news.atl.earthlink.net!harp.news.atl.earthlink.net!not-for-mail From: "Marin David Condic" Newsgroups: comp.lang.ada Subject: Re: Character Sets (plain text police report) Date: Sat, 30 Nov 2002 09:49:25 -0500 Organization: MindSpring Enterprises Message-ID: References: NNTP-Posting-Host: d1.56.b3.26 X-Server-Date: 30 Nov 2002 14:49:48 GMT X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Xref: archiver1.google.com comp.lang.ada:31321 Date: 2002-11-30T14:49:48+00:00 List-Id: It might make an easy extension to the Ada standard to include 32-bit Unicode. After all, its pretty much just a matter of taking existing packages and changing a few things so you could have Wide_Wide_Character. The question is, would it have sufficient utility to make it worth the effort? (Is there much use out there for 32-bit characters?) Perhaps if some additional utility was piled on top of it so that reading a text file, Ada would automatically determine what it was looking at and give you back text in the proper size (create something like "Universal_String" and a whole bunch of utilities around it so it would hold 8, 16 or 32-bit characters depending on how it was loaded) - but I don't see how that could be done for all text files. Only those that conformed to some other standard, like XML, where you can determine from convention what sort of characters will follow. The concept is a little vague in my mind, but I could imagine how something like this might be a useful idea for a standard Ada library. It really doesn't require any fundamental changes to the language. MDC -- ====================================================================== Marin David Condic I work for: http://www.belcan.com/ My project is: http://www.jast.mil/ Send Replies To: m c o n d i c @ a c m . o r g "I'd trade it all for just a little more" -- Charles Montgomery Burns, [4F10] ====================================================================== Robert C. Leif wrote in message news:mailman.1038602282.10532.comp.lang.ada@ada.eu.org... Oops. My apologies. Bob Leif The correct text version is below. Addendum: The solution is the creation of versions of Ada.Strings.Bounded for 16 and 32 bit characters. The 32 bit Unicode characters allow direct comparison of characters based on their position in Unicode.