> So is there a silver bullet other then type casting to fix this issue ?
If you need portability, the only silver buller is one to the head to avoid the obnoxious transcoding all over your code. ;-) Otherwise, I don't know why for Windows they haven't just typedef'd it to wchar_t, but I suspect it's because people would fall into the trap without understanding the implications. Forcing the cast makes it a more conscious decision to screw yourself. I'm sure there are good reasons for why the C++ committee didn't mandate UCS-2 for wchar_t, but whatever they were, they've gone a long way in convincing the XML community to stay with Java and ignore C++. So I hope it was worth it. ;-) -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
