You are viewing a plain text version of this content. The canonical link for it is here.

Posted to c-dev@xerces.apache.org by bu...@apache.org on 2002/02/08 22:38:25 UTC

DO NOT REPLY [Bug 6336] New: - Output of XMLString::transcode not freed?

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6336>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6336

Output of XMLString::transcode not freed?

           Summary: Output of XMLString::transcode not freed?
           Product: Xerces-C++
           Version: 1.6.0
          Platform: All
               URL: http://xml.apache.org/xerces-c/schema.html
        OS/Version: All
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: Documentation
        AssignedTo: xerces-c-dev@xml.apache.org
        ReportedBy: mcervantes@adirtech.com


The documentation contains uses of XMLString::transcode that look like this:

parser->setProperty(
       XMLString::transcode("http://apache.org/xml/properties/schema/external-
noNamespaceSchemaLocation"),
       XMLString transcode("personal.xsd"));

This seems to contradict the claim in XMLString.hpp that the caller of 
XMLString::transcode() is responsible for freeing the memory.

If the example is written that way for brevity's sake, I'd say it's more 
confusing than it's worth.

---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-c-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-c-dev-help@xml.apache.org