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=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,421baaa91aa096a7 X-Google-Attributes: gid103376,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news2.google.com!news1.google.com!newsfeed2.dallas1.level3.net!news.level3.com!newsfeed-00.mathworks.com!lon-transit.news.telstra.net!lon-in.news.telstra.net!news.telstra.net!news-server.bigpond.net.au!53ab2750!not-for-mail From: Dale Stanbrough Newsgroups: comp.lang.ada Subject: Re: Wide_[Wide_]Character References: <4878950d$0$25515$4d3efbfe@news.sover.net> <4878a2c7$0$6560$9b4e6d93@newsspool3.arcor-online.net> User-Agent: MT-NewsWatcher/3.5.2 (Intel Mac OS X) Message-ID: Date: Tue, 15 Jul 2008 12:37:16 GMT NNTP-Posting-Host: 58.161.16.225 X-Complaints-To: abuse@bigpond.net.au X-Trace: news-server.bigpond.net.au 1216125436 58.161.16.225 (Tue, 15 Jul 2008 22:37:16 EST) NNTP-Posting-Date: Tue, 15 Jul 2008 22:37:16 EST Organization: BigPond Internet Services Xref: g2news2.google.com comp.lang.ada:6887 Date: 2008-07-15T12:37:16+00:00 List-Id: Georg Bauhaus wrote: > package Standard specifize 'Size of Wide_Wide_Character, > > type Wide_Wide_Character is > (nul, soh ... Hex_7FFFFFFE, Hex_7FFFFFFF); > for Wide_Wide_Character'Size use 32; thanks, I hadn't seen that. > Annex B has some hints as to the internal representation: > > 43.a/2 Discussion: The C types wchar_t and char16_t seem to be the same. > However, wchar_t has an implementation-defined size, whereas > char16_t is guaranteed to be an unsigned type of at least 16 bits. > Also, char16_t and char32_t are encouraged to have UTF-16 and UTF-32 > representations; that means that they are not directly the same as > the Ada types, which most likely don't use any UTF encoding. This seems to be in reference to the Ada C.Interfaces type, not Wide_Wide_Character. > Isn't this just like the RM not specifying the bit layout of > numeric objects? I'm not sure what the point of Wide_Wide_Character is if not to deal with Unicode (or ISO-10646:2003). You could invent your own 32 bit Character code (or use the one the vendor gives you), but playing in your own backyard doesn't seem very productive. To me the only point is if it implements the code. Dale -- dstanbro@spam.o.matic.bigpond.net.au