[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: doco scm_remember_upto_1
From: |
Marius Vollmer |
Subject: |
Re: doco scm_remember_upto_1 |
Date: |
01 Jun 2003 23:41:57 +0200 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 |
Kevin Ryde <address@hidden> writes:
> I'd like to propose the words below, assuming they're true. Perhaps
> experts can review the last para in particular, and decide how much
> can or should be said about gc and pre-emption.
We can make the guarantee that a GC wont run asynchronously. What
abut this wording:
In a multi-threaded program, it might be thought that a garbage
collection could occur in another thread at any time, and hence
mean a routine like `clear_image' would require protection too.
But this is not the case, a GC will only run when all threads are
in a safe place and have been stopped. But when in doubt, be
conservative: include the call to scm_remember_upto_here_1 when
you are not sure that it is safe to leave it out. A call to
scm_remember_1 will cost at most as much as a call to an empty
function.
> I don't think the varargs scm_remember_upto_here should be documented,
> because I don't think it can be implemented as an inline.
Is that important? A note that says that the non-varargs functions
might be more efficient should suffice, no?
The rest is very nice!
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
- Re: doco scm_remember_upto_1,
Marius Vollmer <=