This is the mail archive of the
guile@sourceware.cygnus.com
mailing list for the Guile project.
Re: gc suggestions
- To: Michael Livshin <mlivshin at bigfoot dot com>
- Subject: Re: gc suggestions
- From: Dirk Herrmann <dirk at ida dot ing dot tu-bs dot de>
- Date: Wed, 28 Jun 2000 12:52:20 +0200 (MEST)
- cc: Guile Mailing List <guile at sourceware dot cygnus dot com>
On Tue, 27 Jun 2000, Dirk Herrmann wrote:
> On 27 Jun 2000, Michael Livshin wrote:
>
> > in any case, if a Scheme-level `after-gc-hook' _is_ needed, it
> > should only be called after a GC really happened, since I hardly see
> > a user being interested whether Guile maybe considered performing a
> > GC.
>
> I fully agree with you. So, this clears things up about where to call the
> after-gc-hook.
There is even a better solution for this, namely not to directly activate
the async for the after-gc-hook from the gc, but rather have a C hook
function registered in the scm_after_gc_c_hook which then activates the
async. Thus, in the core of the gc there are only C level hooks.
The current cvs incorporates the necessary changes. The benefit is a
cleaner separation of the async stuff from the gc core and a cleaner
separation of the scheme level stuff from the gc core. The current
solution, however, does not yet add the additional C level hooks, but I am
going to provide this next.
Best regards
Dirk