Re: wchar_t support at kernel level ?
Re: wchar_t support at kernel level ?
- Subject: Re: wchar_t support at kernel level ?
- From: Francis Bouchard <email@hidden>
- Date: Tue, 13 Nov 2001 09:26:20 -0500
Brian Bergstrand wrote something like :
>
>
Not only that, but if you will be using wchar_t's for what most
>
people using them for (Unicode strings), there are two other
>
pitfalls. First, GCC is the only mainstream compiler that defines
>
wchar_t's as 32bit int's instead of 16bit ints. This will bite you in
>
the ass if you have code that does the following:
>
>
wchar_t ustr[] = L"Hello World";
>
>
There are other cases where this causes trouble, but the above is the
>
most common.
>
This is exactly what I wanted to do... Hummm... Theses strings are used to
identify the driver and things like that, but we must use unicode c'ause of
Japanese... (so 16 bit...)
Now, I have the opportunity to redefine a _MACRO_ WCHAR (widechar - 16 bit).
I tried unsigned short, but then it does not allow me to initialize the
string properly
typedef unsigned short WCHAR;
const WCHAR test[24] = L"bonjour";
This gives me an invalid initializer error. The goal is not to change the
source code. This will allow me to get the source (from another departement)
without having to change it every time and benefit from the bug fixes and
more... I can play with the compilation environnements and the headers
though.
Any suggestions ?
FRanics