Hi Michael, I'm by no means a Xalan expert but I have to assume that this is because most people will access the result string from transcode by using a char* or something similar. The vector is a contiguous memory block and rather than incur the cost of converting it to a std::string, once can simply access the string in memory using c-style semantics if there is a NULL included for termination.
It's not nice for the purist but it addresses practical concerns IMO. If you need it without the NULL you can always shorten the vector by one by using vector's resize() method. With this setup it is efficient for all and no one *needs* to do reallocations or copies to use the string. -Greg -----Original Message----- From: Michael Hughes [mailto:[EMAIL PROTECTED] Sent: Thursday, April 10, 2003 5:18 AM To: [email protected] Subject: XalanDOMString::transcode Hi, I've noticed that when I call the above, the last character that gets returned in the vector is the null terminator. Is this supposed to happen or is it a bug?
