[perl #36574] [PATCH] push, pop, un/shift for resizablebooleanarray

2005-07-16 Thread via RT
# New Ticket Created by Dino Morelli # Please include the string: [perl #36574] # in the subject line of all future correspondence about this issue. # https://rt.perl.org/rt3/Ticket/Display.html?id=36574 > Added new allocation code for resizablebooleanarray. Added push_integer, pop_integer, s

Re: GMC for dummies

2005-07-16 Thread Bob Rogers
From: Leopold Toetsch <[EMAIL PROTECTED]> Date: Sat, 16 Jul 2005 11:38:41 +0200 . . . We keep the invariant by several means: . . . c) a write barrier checks pointer stores into aggregates (by just comparing 2 memory addresses - basically) we can do either: - mak

Re: GMC for dummies

2005-07-16 Thread Leopold Toetsch
Nattfodd wrote: Leopold Toetsch wrote: 1) pmc_bodies have to be variable sized Oh, I believed that we would use variable-sized pmc only if the gc proved to work really well. Well, with fixed sized bodies, we don't need the extra indirection. But I really like to have a more flexible objec

Re: GMC for dummies

2005-07-16 Thread Nattfodd
Leopold Toetsch wrote: > > On Jul 16, 2005, at 2:24, Nattfodd wrote: > >> >> Hi, >> I've produced a new document on GMC (Generational Mark & Compact), the >> GC I'm trying to implement as a Summer of Code project. It's called gmc >> for dummies and I hope it's plainly understandable (if not, tell

Re: GMC for dummies

2005-07-16 Thread Leopold Toetsch
On Jul 16, 2005, at 2:24, Nattfodd wrote: Hi, I've produced a new document on GMC (Generational Mark & Compact), the GC I'm trying to implement as a Summer of Code project. It's called gmc for dummies and I hope it's plainly understandable (if not, tell me so and I'll try to make it better). I