From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Fluids
Date: Wed, 03 Mar 2010 13:29:42 +0100 [thread overview]
Message-ID: <m3aaupd1vt.fsf@pobox.com> (raw)
In-Reply-To: <87iq9ez3h6.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 03 Mar 2010 00:52:05 +0100")
On Wed 03 Mar 2010 00:52, ludo@gnu.org (Ludovic Courtès) writes:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Andy Wingo <wingo@pobox.com> writes:
>>
>>> But you can't / shouldn't make a new fluid every time you enter a
>>> `catch', because currently fluids are never garbage collected! We really
>>> need to fix this. I think it's a 1.9 regression.
>>
>> Indeed. We should use a weak vector or some such instead of the current
>> scm_gc_malloc’d array.
>
> Just to clarify: fluids themselves *are* GC’d, but fluid numbers aren’t
> recycled so ALLOCATED_FLUIDS grows endlessly (1 byte per fluid).
One word per make-fluid, per thread, right?
FWIW I don't need fluids to be gc'd any more, though it probably is a
good idea.
A
--
http://wingolog.org/
next prev parent reply other threads:[~2010-03-03 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 12:33 catch, throw, prompt, control, fluids, garbage collection Andy Wingo
2010-02-14 14:32 ` Fluids Ludovic Courtès
2010-02-14 15:50 ` Fluids Andy Wingo
2010-02-14 19:09 ` Fluids Ken Raeburn
2010-03-02 23:52 ` Fluids Ludovic Courtès
2010-03-03 12:29 ` Andy Wingo [this message]
2010-03-03 13:09 ` Fluids Ludovic Courtès
2010-03-05 17:24 ` Fluids Ludovic Courtès
2010-02-14 14:45 ` Plan for the next release Ludovic Courtès
2010-02-14 15:54 ` Andy Wingo
2010-02-15 22:07 ` catch, throw, prompt, control, fluids, garbage collection Andy Wingo
2010-02-18 22:35 ` Andy Wingo
2010-02-25 0:00 ` Andy Wingo
2010-02-26 12:27 ` Andy Wingo
2010-02-28 22:16 ` Neil Jerram
2010-07-17 10:15 ` Andy Wingo
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=m3aaupd1vt.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).