From: Andy Wingo <wingo@pobox.com>
Subject: Re: scheme closures: crash during garbage collection
Date: Fri, 27 Oct 2006 11:49:31 +0200 [thread overview]
Message-ID: <1161942572.27538.32.camel@localhost.localdomain> (raw)
In-Reply-To: <87u05s2l1e.fsf@zagadka.de>
Hi,
I'm just now getting around to taking care of this oldie.
On Sat, 2006-07-08 at 18:06 +0300, Marius Vollmer wrote:
> Neil Jerram <neil@ossau.uklinux.net> writes:
> > (See
> > http://lists.gnu.org/archive/html/guile-gtk-general/2006-06/msg00013.html
> > if you didn't see the whole description on guile-gtk-general already.)
[...]
> By using this combination of tracing and reference counting it is
> possible to break the cycle that is formed by the proxy pointing to
> the GtkObject and the GtkObject pointing back.
I'm going to look into what it would take to use mark functions, as
guile-gtk does, instead of rolling our GC protection scheme, as Gregory
did[0]. I'll also look into what python does, as they probably have
things right. Then again, I thought I had things right...
[0] http://lists.gnu.org/archive/html/guile-gtk-general/2006-07/msg00056.html
Cheers,
Andy.
--
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-10-27 9:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <64e2f6fe0606081528m4e5f9979yff9b8294ecedf6d2@mail.gmail.com>
2006-06-09 19:54 ` scheme closures: crash during garbage collection Neil Jerram
2006-06-09 21:54 ` Han-Wen Nienhuys
2006-06-10 9:40 ` Marius Vollmer
2006-06-12 22:34 ` Neil Jerram
2006-06-12 23:33 ` Han-Wen Nienhuys
2006-06-12 23:45 ` Neil Jerram
2006-07-08 15:06 ` Marius Vollmer
2006-07-12 21:48 ` Neil Jerram
2006-10-27 9:49 ` Andy Wingo [this message]
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=1161942572.27538.32.camel@localhost.localdomain \
--to=wingo@pobox.com \
/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).