"tuned dynamically", as in at run-time? alexandre mentioned this may
be possible on #parrot, but there may be trouble with decreasing the
generation count. i don't know if run-time tuning of the generation
count is necessary, but if so, i imagine that decreasing the count at
run-time could be achieved by merging generations.
if this gc is tunable at build-time, it should be configurable such
that timely destruction can be disabled. after all, most languages
just don't need it, so why should they have the overhead?
correct me if I'm wrong, but that would mean that a Parrot built with
this gc with timely destruction disabled, can't run languages that do
need the gc with timely destruction, right? (there goes your
inter-language operability...)
If so, then this would make that Parrot rather ... ehm, disabled :-)
(anyway, this is only important when this tuning is done at build-time)
klaas-jan
