Subject: Re: concatenated-stream - which component is being read from?
From: Erik Naggum <>
Date: 2000/04/04
Newsgroups: comp.lang.lisp
Message-ID: <>

* (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