Hi,
With Winelib now defining __TEXT nicely, its possible to use unicode strings
in code with UNICODE defined. Its not possible to create a (windows) u/c
string if UNICODE isn't defined, though.
Under windows, __TEXT gives you a string in ascii or u/c depending on whether
UNICODE is defined. But you can still always get a u/c string by using
L"foo". With winelib this gives you a glibc u/c string :-(
Any ideas on how to get around this in a source compatable manner?
Cheers,
Jon
--
"Once you realise you're not _meant_ to fit in, it all makes sense..."
[EMAIL PROTECTED] , [EMAIL PROTECTED]
