Hi,
I'm using an older version of xerces-c that doesn't
have XMLString::release(). In this case, can I simply
do the following to release the memory:
XMLCh *data = XMLString::transcode("data");
delete data;
Thanks,
Monica
--- Adam Heinz <[EMAIL PROTECTED]> wrote:
> XMLString::transcode(1 arg) always returns a string
> that you should dispose of with XMLString::release.
> Look around for an XStr or StrX class in the
> examples. You'll use a _X() macro that creates an
> XStr object on the stack, then that object holds the
> heap-allocated results from XMLString::transcode
> until it falls off the stack, at which point it
> cleans up for you. It's nice enough for
> somecall(_X("foo")), etc.
>
> Adam Heinz
> Senior Software Developer
> Exstream Software
>
> -----Original Message-----
> From: Monica Lau [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 09, 2004 11:15 AM
> To: [EMAIL PROTECTED]
> Subject: RE: DOMWriter Questions
>
> Hi,
>
> Thanks for this important piece of information. I
> believe all the samples that I've seen so far use
> someCall(XMLString::transcode(...))
>
> What about the "getDOMImplementation(...)" function?
>
> Does it dynamically allocate memory in the buffer?
> (Sorry for my ignorance -- I tried looking at the
> API
> for this, but couldn't find the info that I needed.
> I'm just trying to ensure that I don't end up with
> memory leaks in my application.)
>
> Thanks,
> Monica
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
>
__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
