Dan Sugalski <[EMAIL PROTECTED]> wrote:
> At 9:48 PM +0200 8/20/04, Leopold Toetsch wrote:
>>0) Parrot's nomenclature DOD vs GC is a bit misleading. The "DOD"
>>subsystem is the stop-the-world mark & sweep collector that recycles
>>object headers. The "GC" is the copying collector for variable size
André Pang <[EMAIL PROTECTED]> wrote:
> On 21/08/2004, at 5:48 AM, Leopold Toetsch wrote:
>> 3) The copying collector isn't integrated yet. But that should be easy.
>> After finishing sweep and if there is some possible wastage in the
>> memory pools, these get compacted.
> I thought Parrot wasn'
Andrà Pang writes:
> On 21/08/2004, at 5:48 AM, Leopold Toetsch wrote:
>
> >3) The copying collector isn't integrated yet. But that should be easy.
> >After finishing sweep and if there is some possible wastage in the
> >memory pools, these get compacted.
>
> I thought Parrot wasn't using copying
On 21/08/2004, at 5:48 AM, Leopold Toetsch wrote:
3) The copying collector isn't integrated yet. But that should be easy.
After finishing sweep and if there is some possible wastage in the
memory pools, these get compacted.
I thought Parrot wasn't using copying collectors, since you're exposing
PM
At 9:48 PM +0200 8/20/04, Leopold Toetsch wrote:
0) Parrot's nomenclature DOD vs GC is a bit misleading. The "DOD"
subsystem is the stop-the-world mark & sweep collector that recycles
object headers. The "GC" is the copying collector for variable sized
string and other buffer memory.
The incrementa
