Curt Arnold wrote > I had previously mentioned making DOMString's semantics match that of a > subset of wstring, so that a user could have a familiar behavior and it > would be possible (though not tested and supported) that you could redefine > DOMString to be derived from wstring. I haven't had any free time recently, > but I could take a shot at scoping the effect. Is it worth trying? >
Referring to Dean's note on More Xerces-C character encoding discussion, we can't use wstring because we can't rely on wchar_t holding Unicode values. basic_string<XMLCh> would avoid this, but wouldn't interoperate with APIs expecting wstring. -- Andy
