From: Han-Wen <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: lazy sweeping.
Date: Tue, 30 Jul 2002 12:09:27 +0200 [thread overview]
Message-ID: <15686.26071.964366.614742@blauw.xs4all.nl> (raw)
In-Reply-To: <s3sn23mm66.fsf@cmm.kakpryg.net.cmm>
guile@cmm.kakpryg.net writes:
> > * Lazy sweeping sounds like a feature, but it actually leads to
> > simpler, more natural code than the old sweeping code.
>
> did you consider various finalizations? like closing file descriptors
> of dead ports, sort of fing.
>
> if you just lazy-sweep naively, some external resources may never get
> freed.
oh, btw, I noticed that only ports are flushed on exit of GUILE (gc.c
- onexit ()). The manual talks about "freeing resources" for the smob
free function. I believe that is inaccurate: free is only for freeing
memory. Stuff like closing files should happen in an explicitly called
function, for the free() might never get called at then end.
--
Han-Wen Nienhuys | hanwen@cs.uu.nl | http://www.cs.uu.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-30 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-28 23:32 lazy sweeping Han-Wen
2002-07-29 0:07 ` Michael Livshin
2002-07-29 9:48 ` Han-Wen Nienhuys
2002-07-29 10:14 ` Michael Livshin
2002-07-29 12:40 ` Han-Wen Nienhuys
2002-07-29 13:00 ` Michael Livshin
2002-07-29 13:06 ` Han-Wen Nienhuys
2002-07-30 10:09 ` Han-Wen [this message]
2002-07-30 12:10 ` Michael Livshin
2002-07-29 4:31 ` Tom Lord
2002-07-29 15:17 ` Han-Wen Nienhuys
2002-07-29 13:16 ` Mikael Djurfeldt
2002-07-29 13:22 ` Han-Wen Nienhuys
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=15686.26071.964366.614742@blauw.xs4all.nl \
--to=hanwen@cs.uu.nl \
--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).