From ... From: Erik Naggum Subject: Re: concatenated-stream - which component is being read from? Date: 2000/04/04 Message-ID: <3163863401819617@naggum.no>#1/1 X-Deja-AN: 606701901 References: <3163344737710362@naggum.no> <%5wE4.82$5p5.3226@burlma1-snr2> mail-copies-to: never Content-Type: text/plain; charset=us-ascii X-Complaints-To: newsmaster@eunet.no X-Trace: oslo-nntp.eunet.no 954876400 28731 195.0.192.66 (4 Apr 2000 19:26:40 GMT) Organization: Naggum Software; vox: +47 8800 8879; fax: +47 8800 8601; http://www.naggum.no User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5 Mime-Version: 1.0 NNTP-Posting-Date: 4 Apr 2000 19:26:40 GMT Newsgroups: comp.lang.lisp * hoehle-sorry@tzd.dont.telekom.spam.de.me (Joerg-Cyril Hoehle) | I believe there's a need for *particular* objects which *will* close | constituents when it has finished with them. you _could_ define an after method on read-char and read-byte on that stream that would close it once it got exhausted, using the widely available Grey streams, or something better if and when it comes along with such features available. (hi, Duane! hint for the taking! :) in an application that needed a little simpler life than it could get out of the box, I added code to the socket layer this way to automatically shut down the input side, forcing an EOF that consequently shut down the output side gracefully as well when they ran into trouble of any kind, as the socket error handling in most Unices is a disgraceful mess of special cases that neither match nor attempt to match the TCP or IP specifications. #:Erik