Correct, the object "row" is going out of scope almost immediately after
this call. I've tried setting it to NULL and that doesn't change behavior.
I've also added a line to set the clone object to NULL, again with no
changes to the leak.
I'm using Xerces-C 1.4.0.
Thanks
-Evan
-----Original Message-----
From: Bill Schindler [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 13, 2001 4:45 PM
To: [EMAIL PROTECTED]
Subject: Re: DOM_Node::cloneNode() clones not getting released?
Just to be sure of a few things...
Which version of Xerces are you using?
>> table.removeChild(row);
The node "row" is going out of scope or being set to NULL after
this, right?
It appears as though cloneNode() goes through all the right
gyrations. I'm not entirely convinced that a node-with-children
outside of the DOM tree gets properly cleaned up. (There's code to
catch that case, but the conditions for actually deleting a node
are somewhat obscure.)
--Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
