From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!fr.clara.net!heighliner.fr.clara.net!lirmm.fr!cines.fr!univ-lyon1.fr!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: Clearing eof condition from stream. References: Mail-Copies-To: never From: Erik Naggum Message-ID: <3213990261419534@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 05 Nov 2001 23:04:22 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader1.kpnqwest.net 1005001462 193.71.66.49 (Tue, 06 Nov 2001 00:04:22 MET) NNTP-Posting-Date: Tue, 06 Nov 2001 00:04:22 MET Xref: archiver1.google.com comp.lang.lisp:19231 * Kaz Kylheku | I can't find anything in the HyperSpec about how an end of input | indication affects the state of a Lisp stream. Is there an end-of-file | state that can be removed, so that further input operations on the file | or device can be attempted? My understanding is that such "error states" are not remembered, because you are supposed to actually deal with an error condition, which is quite unlike the situation in a language where errors are routinely ignored and it would be a service to the programmer to let him clear the error/eof flag once some part of the program that cared about such things had time to look at it. So look at it as if the handler in both languages clears the error flag, but you always handle an error immediately in Common Lisp and so decoupling the error flag from the handler makes no sense. /// -- Norway is now run by a priest from the fundamentalist Christian People's Party, the fifth largest party representing one eighth of the electorate. -- Carrying a Swiss Army pocket knife in Oslo, Norway, is a criminal offense.