Re: [XQilla-user] Memory Management in Xqilla

[John S. <joh...@or...>]

Thomas Santana wrote:
> John Snelson wrote:
>> Hi Thomas,
>>
>> The X() and UTF8() macros construct an object which owns the 
>> transacoded string. When that object goes out of scope (under normal 
>> C++ scoping rules), the transcoded string will be destroyed. These 
>> macros should be used only for temporary transcoding.
>>
> Dumb question, I looked at the source, an thought this was the case... 
> but there is a comment in XStr.hpp that this is not very efficient. 
> Despite creating a lot of objects to be cleared is there any hidden impact?

There's no /other/ hidden impact.

>> Memory management in Xerces-C is complicated. I think you are using 
>> the DOM 3 API to XQilla. If that is correct, then you should call the 
>> release() method on both the DOMXPathExpression object and the 
>> XPath2Result object when you have finished with them.
>>
> True, I'm looking into the DOM3 API, the other Xerces-C memory 
> allocation should be considered too,correct?

You don't need to do anything more than you normally would with any of 
the other Xerces-C objects.

If you still need help, you might want to post some example code that 
you need help with.

John