Justin has left a new comment on your post "Memory Management in PIRC":
APR is the Apache Runtime library. It's centered around the idea that
all allocations are done for some specific request/task and that most
(or even all) of that memory will be needed for the duration of th
Justin has left a new comment on your post "Memory Management in PIRC":
That's one way to do it. Why not the APR way of things? Creating memory
pools in which memory can only be allocated (not freed) and after each
step is finished you simpy reclaim the entire pool (no fragmentat
rl causes a build failure, so I'm still of the thinking that we need a
shared libparrot.
A shared libparrot seems most desireable in any case. One can certainly
imagine many instances running simultaneously.
Justin: This is certainly a problem that needs solving. We can join forces
if you
object isn't in P2 anymore
and "self" in PIR replaces it, what is the equivalent in pasm? That
looks like what's breaking the OO benches right now.
Thanks,
Justin DeVuyst
--- parrot/examples/benchmarks/vpm.imc 2004-12-13 03:00:24.0 -0500
+++ parrot_new/examples/
