From: tomas@fabula.de
Cc: guile-devel@gnu.org
Subject: Re: documentation.scm close files
Date: Sat, 24 May 2003 10:46:53 +0200 [thread overview]
Message-ID: <20030524084653.GA19308@www> (raw)
In-Reply-To: <87r86pi04f.fsf@zip.com.au>
On Sat, May 24, 2003 at 11:50:24AM +1000, Kevin Ryde wrote:
> tomas@fabula.de writes:
> >
> > it seems important to me to make even clearer that the garbage collector
> > is triggered when we are short on memory
>
> Yep, good point. New words below.
Wow. Thanks.
> I guess some sort of file descriptor threshold scheme might be cute.
> Like garbage collect after every 10 or 20 files net opened (ie. opens
> less explicit closes).
>
> I suppose to be reliable such a scheme would need to be carefully
> applied to all functions opening or closing fds. Not much value if
> it's not universal.
But file descriptors are just one of many possible resources
which might run low and which might be recovered from gc.
(that's what I was trying to hint at with this strange Oracle
anecdote). Would it be worth implementing a generalized resource
watcher framework? Are fds important enough to implement a
special case for them? May be...
Regards
-- tomas
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-24 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 22:58 documentation.scm close files Kevin Ryde
2003-05-17 20:07 ` Marius Vollmer
2003-05-18 22:54 ` Kevin Ryde
2003-05-21 22:40 ` Kevin Ryde
2003-05-22 9:59 ` tomas
2003-05-24 1:50 ` Kevin Ryde
2003-05-24 8:46 ` tomas [this message]
2003-06-05 1:00 ` Kevin Ryde
2003-05-22 15:20 ` Marius Vollmer
2003-05-23 21:20 ` Kevin Ryde
2003-06-01 21:02 ` Marius Vollmer
2003-06-05 1:17 ` doco with-input-from-file, with-output-to-file (was: documentation.scm close files) Kevin Ryde
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=20030524084653.GA19308@www \
--to=tomas@fabula.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).