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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,974799d066e5d38e,start X-Google-Attributes: gid103376,public From: Florian Weimer Subject: Wide_Character vs. Interfaces.C.wchar_t Date: 1999/10/13 Message-ID: <87emez6nn6.fsf@deneb.cygnus.argh.org>#1/1 X-Deja-AN: 536548743 Mail-Copies-To: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@cygnus.argh.org X-Trace: deneb.cygnus.argh.org 939844557 25823 192.168.1.2 (13 Oct 1999 19:55:57 GMT) Organization: Penguin on board Mime-Version: 1.0 User-Agent: Gnus/5.07009701 (Pterodactyl Gnus v0.97.1) Emacs/20.4 NNTP-Posting-Date: 13 Oct 1999 19:55:57 GMT Newsgroups: comp.lang.ada Date: 1999-10-13T19:55:57+00:00 List-Id: ARM B.3 seems to imply the existance of a bijective mapping between Wide_Character and Interfaces.C.wchar_t. ARM 3.5.2(3) requires that Wide_Character has exactly 2**16 distinct values. What shall be done if wchar_t (the C version) has more than just 16 significant bits? This isn't just a theoretical question because with GNU libc 2.1.2, wchar_t type has actually 32 significant bits (and GNAT declares Interfaces.C.wchar_t so that its size is 16 bits, which seems to be wrong).