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 that
request/task.
In
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 fragmentation,
no pointer tr
kjs has left a new comment on your post "Memory Management in PIRC":
Justin, thanks for sharing your thoughts. I'm not sure what "APR" way
of things is.. Creating memory pools and reclaiming the pool after each
step: all allocated memory is needed till the end of the compilation,
so there's no dif
