From ... Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!ossa.telenet-ops.be!nmaster.kpnqwest.net!nreader1.kpnqwest.net.POSTED!not-for-mail Newsgroups: comp.lang.lisp Subject: Re: CLOSE and OUTPUT-STREAM-P References: Mail-Copies-To: never From: Erik Naggum Message-ID: <3226652067142909@naggum.net> Organization: Naggum Software, Oslo, Norway Lines: 21 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 01 Apr 2002 12:14:11 GMT X-Complaints-To: newsmaster@KPNQwest.no X-Trace: nreader1.kpnqwest.net 1017663251 193.71.199.50 (Mon, 01 Apr 2002 14:14:11 MET DST) NNTP-Posting-Date: Mon, 01 Apr 2002 14:14:11 MET DST Xref: archiver1.google.com comp.lang.lisp:30684 * Kent M Pitman | I think INPUT-STREAM-P and OUTPUT-STREAM-P are intended to guide you as | to what kinds of things you are intended to do on an object you've just | found. Agreed. | In this regard, I would say it's most important that if you do | (input-stream-p x) => t | on a closed stream, you are implying that peeking for data on the stream | is going to yield eof information without a problem and not complain that | it was improper for you to do this. Analogously for OUTPUT-STREAM-P. Here I disagree. If you are going to attempt any operations on a stream, open-stream-p gives the authoritative answer on whether any I/O will work on it, not whether it is an input-stream or an output-stream. /// -- In a fight against something, the fight has value, victory has none. In a fight for something, the fight is a loss, victory merely relief.