From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news.tele.dk!small.news.tele.dk!212.43.194.69!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: <3213990261419534@naggum.net> Mail-Copies-To: never From: Erik Naggum Message-ID: <3213993158410479@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 16 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:52:39 GMT X-Complaints-To: newsmaster@Norway.EU.net X-Trace: nreader1.kpnqwest.net 1005004359 193.71.66.49 (Tue, 06 Nov 2001 00:52:39 MET) NNTP-Posting-Date: Tue, 06 Nov 2001 00:52:39 MET Xref: archiver1.google.com comp.lang.lisp:19239 * Barry Margolin | How does the EOF error handler clear the EOF condition in CL once it has | handled it? I wonder how I managed _not_ to explain this clearly. There is no "EOF condition" on the stream to _clear_ in the first place. When the handler returns or transfers control somewhere else, the condition is _gone_. If the stream remembers that it has hit end of file and you cannot retry the operation, I consider that a violation of conformance with the standard. /// -- 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.