Hi Keith,
Thanks for the reply. The function in question calls the XalanDOMString.transcode() function to get a CharVectorType back. Then the function allocates a char[] of appropraite length, and then it copies characters from the vector into the array one by one. When the function tries to return, I get an Access Violation. Looking at the stack trace, it appears that the violation occurs in the vector's deconstructor method.
Ryan
Keith Rogers wrote:
Ok, I looked at the code. It actually creates a string object that encapsulates both std::wstring (UCS2) and std::string (UTF8). We don't use the transcode functions -- too many problems some years ago (Xalan 1.0?). All of our wide character data is UCS2, and char is UTF8. There are Microsoft APIs that do that conversion, or you can pretty easily write your own (what I did).
Keith Rogers <[EMAIL PROTECTED]> wrote:
I've got a fair amount of code that uses the XalanDOMString::c_str() to create std::string objects,...
