On Sun, Jul 24, 2005 at 10:32:32PM -0400, Bob Rogers wrote:

>    For the record, is it acceptable in Parrot to use page
> write-protection to record whether oldspace objects have been modified
> since the last full GC?  This is what CMUCL does on most ports, but it
> occurs to me that this might be a porting headache for Parrot.

It's not a porting headache if it's not the only option. If it's viable
to use a different, slower strategy where this is not available, or a different
GC, then parrot will still run.

Nicholas Clark

Reply via email to