unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Marius Vollmer <marius.vollmer@uni-dortmund.de>
Cc: guile-devel@gnu.org
Subject: Re: doco scm_remember_upto_1
Date: 22 May 2003 11:42:48 +0200	[thread overview]
Message-ID: <lj1xyrl3l3.fsf@troy.dt.e-technik.uni-dortmund.de> (raw)
In-Reply-To: <87wugjqx1g.fsf@raven.i.defaultvalue.org>

Rob Browning <rlb@defaultvalue.org> writes:

> 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?

Yes, that would be an improvement.  As Rob say, you are safe right
now, but having one scm_remember_upto_here too many does not hurt.

> 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.

Yes, but I'd say that for new code we could be more careful with the
scm_remembers.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2003-05-22  9:42 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
2003-05-22  9:42   ` Marius Vollmer [this message]
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=lj1xyrl3l3.fsf@troy.dt.e-technik.uni-dortmund.de \
    --to=marius.vollmer@uni-dortmund.de \
    --cc=guile-devel@gnu.org \
    /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).