This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: on the topic of GC.
- To: Dirk Herrmann <dirk at ida dot ing dot tu-bs dot de>
- Subject: Re: on the topic of GC.
- From: Jim Blandy <jimb at red-bean dot com>
- Date: 20 Sep 1999 22:08:44 -0500
- Cc: Michael Livshin <mike at olan dot com>, guile at sourceware dot cygnus dot com
- References: <Pine.LNX.4.10.9909200841380.1017-100000@marvin.ida.ing.tu-bs.de>
> Wouldn't it be possible to have a function scanning some region of memory
> and looking for possible references that haven't been registered? This
> function would help debugging and could even be used to check heap areas:
> Guile does require explicit registering for heap objects, so there is even
> with the current approach a chance that you forget to register something.
I'm not sure what you're suggesting here. It sounds like the idea is
to use precise marking, but then check up on it with a conservative
scanner.
I'm not sure what benefits this provides.
- If you believe that conservative marking is more accurate than
precise marking, then you should be using conservative scanning for
marking, not just for error checking.
- If you believe that conservative marking is less accurate than
precise marking, then this error checking would produce mostly
misleading warnings.
- If you believe that conservative marking is as accurate as precise
marking, then you should use conservative marking, since it's less
trouble.
But I feel like I'm missing something...