From: Neil Jerram <neil@ossau.uklinux.net>
Subject: [solved] Re: Weak references and GC
Date: Sat, 10 Sep 2005 00:00:44 +0100 [thread overview]
Message-ID: <87u0gtetib.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <873bogsdm6.fsf@ossau.uklinux.net> (Neil Jerram's message of "Wed, 07 Sep 2005 23:43:29 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> I'm having trouble with lists (actually source code expressions) that
> are weakly stored in several places and never being GC'd. [...]
For anyone interested... the thing preventing GC was a closure created
in an environment that included the source code expression as a local
variable. Even though the closure's code did not reference the
variable, the closure's environment still includes that variable and
its value, and so protects the value from GC.
Neil
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
prev parent reply other threads:[~2005-09-09 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 22:43 Weak references and GC Neil Jerram
2005-09-09 23:00 ` Neil Jerram [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=87u0gtetib.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
/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).