From: Rob Browning <rlb@defaultvalue.org>
Cc: marius.vollmer@uni-dortmund.de
Subject: Re: doco scm_remember_upto_1
Date: Thu, 22 May 2003 02:07:39 -0500 [thread overview]
Message-ID: <87wugjqx1g.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <87wugjhowm.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 22 May 2003 09:15:53 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> In the "Type checking" node of the manual showing the clear_image
> example smob code, should that function have an scm_remember_upto_1
> just before returning, in order to keep image_smob visible to a
> garbage collect that might run in another thread?
(I'm looking at the 1.6 docs)
Marius may need to comment here, but I was under the impression that
at the moment we haven't been trying to write all the code to
accomodate a C-side preemptive GC. This means that you don't need a
"remember" if there are no intervening calls (usually just scheme
calls) that could cause a GC.
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-22 7:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-21 23:15 doco scm_remember_upto_1 Kevin Ryde
2003-05-22 7:07 ` Rob Browning [this message]
2003-05-22 9:42 ` Marius Vollmer
2003-05-22 15:21 ` Rob Browning
2003-05-24 1:19 ` Kevin Ryde
2003-05-30 0:04 ` Kevin Ryde
2003-06-01 21:41 ` Marius Vollmer
2003-06-11 23:07 ` Kevin Ryde
2003-06-18 23:36 ` Marius Vollmer
2003-06-21 23:02 ` Kevin Ryde
2003-07-27 14:49 ` Marius Vollmer
2003-05-30 13:26 ` Marius Vollmer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wugjqx1g.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=marius.vollmer@uni-dortmund.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).