From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!newsfeed.vmunix.org!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: conservative gc sucks Date: 14 Jan 2003 21:12:33 +0000 Organization: Naggum Software, Oslo, Norway Lines: 24 Message-ID: <3251567553621728@naggum.no> References: <3251188682174136@naggum.no> <8bbd9ac3.0301131719.160d091f@posting.google.com> <3251520171080849@naggum.no> <8bbd9ac3.0301141305.6629ae04@posting.google.com> Reply-To: http://naggum.no/erik/contact.html Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: maud.ifi.uio.no 1042578753 22252 129.240.65.207 (14 Jan 2003 21:12:33 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 14 Jan 2003 21:12:33 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:50508 * Andy Freeman | That data operations using valid handles are unaffected by unlink. If you want to rely on this, do you still want the stream to be closed when it is garbage collected, or do you want some control over when it ceases to exist? I guess I am trying to figure out why you brought this up in the context of garbage-collected streams with finalization semantics. Also, despite what you believe, this is not the only mechanism. The standard language semantics prevails. Someone wanted to be relieved of closing streams "manually" and wanted them to be closed when they became unreferenced. Again despite what you believe I said, I have offered three different ways to address this problem. (One of them automatic reaping of unreferenced file handles.) How you could possibly have invented the premise that one of these three would be the only one available is beyond me. -- Erik Naggum, Oslo, Norway Act from reason, and failure makes you rethink and study harder. Act from faith, and failure makes you blame someone and push harder.