> 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.
I agree. The big advantage of this is that this: basic_string<XMLCh> is not legal C++. Nor does it work in any recent g++ version, because they chose strict compliance over continuing to let this work. It's not a simple trade-off, but it's a serious bitch to work around, since it makes it really hard to do efficient STL programming. But since you can cast on Windows, and since Windows is the only platform that you can do it on anyway, it's not really a big help for the library to do the definition for you. If all you need is Windows, there are lots of built in XML options now, and if you play these kinds of games, none of your Xerces code will port anyway. -- Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
