Gareth Reakes wrote:
> http://blog.parthenoncomputing.com/xerces/archives/2005/05/memory_man
>ageme.html
>
> Please give comments. This comes up now and again so its worth
> spending a bit of time on to make it understandable.
3) This scheme can give the appearance of memory leaks. If the nodes new
anything during their creation or use (for example, Element creates an
attribute list in its constructor) then releasing the node will not
release that memory.
For me it seems rather inconsistent. What happens to e.g the attribute
list after an element has been released? What is it used for? Or,
asking differently, should I explicitly release an element's attribute
list before releasing the element? Are there, besides attribute lists,
any other ressources that are handled similarly?
What would speak against just releasing all associated ressources when
releasing an element?
(Please, forgive that I have not searched this topic in the list
archives, so maybe my questions are stupid duplicates)
Cheers,
Axel
--
Humboldt-Universit�t zu Berlin
Institut f�r Informatik
Signalverarbeitung und Mustererkennung
Dipl.-Inf. Axel Wei�
Rudower Chaussee 25
12489 Berlin-Adlershof
+49-30-2093-3050
** www.freesp.de **
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
