Jon Griffiths wrote:
>
> Hi,
>
> > Of course the name is a bit long (and it's WINE specific) so you
> > could do:
> >
> > #define VTEXTW(x) WINE_UNICODE_TEXT(x)
[...]
> Actually, having said that, have you tested -fshort-wchar? does it require
> libc to be rebuilt? or just to build with a different set of headers (i.e.
> lib funcs still cannot be used)? My assumption is that it just changes the
> behaviour of L'foo', and doesn't address the crt issues at all.
That's right, it does not address the crt issues at all.
Actually it helps a little in that you can use the standard C library
headers (e.g. to get wcslen) and then link with crtdll or msvcrt.
But the libc C still expect 4byte Unicode chars and I don't expect
this to change anytime soon. It would require two implementations of
each Unicode function which means two versions of the library.
--
François Gouget
[EMAIL PROTECTED]
