From: Maciej Sobczak <see.my.homepage@gmail.com>
Subject: Re: Allocators and memory reclamation
Date: Tue, 29 Jan 2008 03:12:48 -0800 (PST)
Date: 2008-01-29T03:12:48-08:00 [thread overview]
Message-ID: <fa54c7a7-f1f5-445f-bbda-e810614f5f1c@e25g2000prg.googlegroups.com> (raw)
In-Reply-To: wccsl0h8nu1.fsf@shell01.TheWorld.com
On 29 Sty, 01:41, Robert A Duff <bobd...@shell01.TheWorld.com> wrote:
> Finalization of heap objects happens when you do
> Unchecked_Deallocation. In addition, when an access type goes
> out of scope, all remaining objects (the ones you did not
> Unchecked_Deallocate) are finalized in an arbitrary order,
> but this does not free the memory.
[...]
> In implementation terms, each finalizable heap object is
> chained onto a doubly-linked list. U_D removes the object
> from the list, finalizes it, and frees the memory.
> When the access type goes out of scope, the implementation
> walks down the list and finalizes everything on it.
[...]
This, and the replies from Adam and Dmitry give me the complete
picture of how it works. Thanks for the explanation.
--
Maciej Sobczak * www.msobczak.com * www.inspirel.com
next prev parent reply other threads:[~2008-01-29 11:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 13:49 Allocators and memory reclamation Maciej Sobczak
2008-01-28 14:52 ` gpriv
2008-01-28 14:53 ` Lucretia
2008-01-28 16:00 ` gpriv
2008-01-28 22:46 ` Alex R. Mosteo
2008-01-28 15:15 ` Dmitry A. Kazakov
2008-01-28 22:27 ` Maciej Sobczak
2008-01-28 23:54 ` Adam Beneschan
2008-01-29 9:38 ` Dmitry A. Kazakov
2008-01-28 23:07 ` Randy Brukardt
2008-01-28 22:00 ` Aurele
2008-01-29 0:41 ` Robert A Duff
2008-01-29 11:12 ` Maciej Sobczak [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-01-29 11:06 Grein, Christoph (Fa. ESG)
2008-01-29 12:50 ` Dmitry A. Kazakov
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox