I would guess that the whole subtree is released but to be sure you'll have to read the large documentation (the one that starts with the function main). Oh the wonderful world of open source... :)
/ Erik > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: den 15 juli 2003 18:49 > To: [EMAIL PROTECTED] > Subject: Re: parser->parse() question > > > Thanks. > > Ok....I think I am finally beginning to understand the full story of > release ;-) > > One more question though. The part that I still find confusing is how > decisions are made about child nodes. For instance....lets say that I > load > a document, get a reference to it, and get a reference to one of its > child > nodes (foo). Then I remove this node(foo) , create a new node (newFoo) > using the document, and append the removed node (foo) to the new node > (newFoo). Finally I call release() on the new node (newFoo). Now, does > the removed node (foo) that was appended to the new node get released or > not? > > In other words, does release only get called on nodes that have been > created AND orphaned? Or, could a call to removeChild(foo) essentially > orphan a node so that it would also be released. I guess I find the rules > in the DOM Programming Guide to be a little incomplete and nebulous and I > (unfortunately) need the details on what gets released when and where. > > Again. I know these nitpicky questions are a pain....sorry. > > > > > |---------+----------------------------> > | | Gareth Reakes | > | | <[EMAIL PROTECTED]| > | | oft.com> | > | | | > | | 07/15/2003 11:36 | > | | AM | > | | Please respond to| > | | xerces-c-dev | > | | | > |---------+----------------------------> > >----------------------------------------------------------------------- > ----------------------------------------------| > | > | > | To: "[EMAIL PROTECTED]" <xerces-c- > [EMAIL PROTECTED]> | > | cc: > | > | Subject: Re: parser->parse() question > | > >----------------------------------------------------------------------- > ----------------------------------------------| > > > > > Hi, > > On Tue, 15 Jul 2003, [EMAIL PROTECTED] wrote: > > > > > So. If I try to operate on a node that has been released, it should > still > > be in memory? > > If it has not been reused. > > > Or, is it possible that I get some other node that is now > > using the memory freed up during that release? > > yep, I have had some really fun results ;) > > Gareth > > > -- > Gareth Reakes, Head of Product Development +44-1865-203192 > DecisionSoft Limited http://www.decisionsoft.com > XML Development and Services > > > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
