> Because std::wstring is not so standard... for instance, gcc > 2.95 doesn't have it.
Heh, if that was the reason (as opposed to the fact that the *encoding* of wstring isn't standard), I'd be screaming for the change. ;-)
I was just pointing out that wstring is so standard that is not implemented on every platform. But you are right, Xerces internally uses UTF-16 strings, and wchar_t isn't a cross-platform storage for UTF-16. The point is that platforms that know this is true (like Windows) would like to see XMLCh==wchar_t, even if they can just cast them to be the desired type.
Alberto
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
