This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++ v3 wants more libio functions now
- To: "Michael Vance" <briareos at lokigames dot com>,"Mike Stump" <mrs at windriver dot com>
- Subject: Re: libstdc++ v3 wants more libio functions now
- From: "Geert Bosch" <bosch at gnat dot com>
- Date: Wed, 26 Jul 2000 08:16:21 -0400
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Reply-To: "Geert Bosch" <bosch at gnat dot com>
On Tue, 25 Jul 2000 12:06:16 -0700, Michael Vance wrote:
Is wchar_t still defined as a four-byte quantity in GCC? If so, is
there a document or archived mlist discussion somewhere documenting
why this is? I know that the spec says it is
"implementation-dependent", but every implementation I'm aware of does
it as a 2-byte wide character. This was a nasty PITA when porting some
SDK code during Solder of Fortune... does GCC support some locale that
demands four-byte wide characters?
I am just fixing the code in GNAT for interfacing with C wide characters.
GNAT assumed that C wchar_t was a 16-bit quantity, but we were notified
by a user that this actually was defined as Integer'Size in GCC. If this
definition may be changed to 16-bit anytime soon, I'd like to know so
I can avoid double changes.
It seems strange to me that there is no system ABI specifying this exactly...
What do the different Unices expect in their system calls?
-Geert