From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!uio.no!nntp.uio.no!ifi.uio.no!not-for-mail From: Erik Naggum Newsgroups: comp.lang.lisp Subject: Re: closing files by gc Date: 09 Jan 2003 10:01:39 +0000 Organization: Naggum Software, Oslo, Norway Lines: 23 Message-ID: <3251095299409304@erik.naggum.no> References: <43co3c6ck.fsf@beta.franz.com> Reply-To: http://naggum.no/erik/contact.html Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: maud.ifi.uio.no 1042106500 5953 129.240.65.207 (9 Jan 2003 10:01:40 GMT) X-Complaints-To: abuse@ifi.uio.no NNTP-Posting-Date: 9 Jan 2003 10:01:40 GMT Mail-Copies-To: never User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 Xref: archiver1.google.com comp.lang.lisp:50111 * Tom Lord | In other words: it isn't just a "safety net" to compensate for | sloppy programming (like `with-foo' implementations that aren't | quite right). In fact, for some algorithms, it's essential. | | All the people advising "Hey, just use `with-foo'" -- well, as a | rule of thumb, that's fine. But as an absolute rule it means "Hey, | there are some algorithms you can't code in lisp" and that's just | icky. | | Geeze, isn't this completely obvious? Y'all are writing satire, | right? What I find rather obvious is that any stream you read from may be closed when you hit end-of-file, regardless of where this happens. Users of a stream can test for open-ness with `open-stream-p´, which is quite remarkably different from testing for end-of-file. -- 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.