Hi,
Following on from Aaron's reply to my comment.
>There is no mechanism in Poplog for
> > protecting an object against relocation and it would be technically
>> demanding to do such a thing.
>
>I think this is not correct.
I should have been a little more expansive. What I was trying to say
is that Poplog does not have a POST-CREATION, PER OBJECT mechanism
for protecting against relocation. In other words, you can't
dynamically decide to "fix" an object.
In particular, -sys_lock_heap- doesn't count in this regard because
it is not a per-object method. -cons_fixed- is something that has to
be applied at creation time (presumably to simplify the management of
heap fragmentation) and so doesn't count either.
By the way, this shouldn't be read as a serious criticism of Poplog.
I am unaware of any relocating garbage collector that has such a
feature. Furthermore, it really would be very technically demanding
to implement. Although one can easily hallucinate a hybrid garbage
collection strategy that makes it possible, one should bear in mind
that this effectively doubles the complexity of a garbage collector.
--
Steve
|