It seems like EndOfStream could just as well be implemented as a 
Notification ... ?

----------
>From: "Raab, Andreas" <Andreas.Raab at disney.com>
>To: squeak at cs.uiuc.edu
>Subject: EndOfStream an Error???
>Date: Tue, May 23, 2000, 11:23 PM
>

> Folks,
>
> Just wondering: Who came up with the idea that EndOfStream is an error?!
> There's a definite notion in ST80 that ReadStream>>next returns nil if there
> are no more elements so that this can hardly count as an error, can it?!
> With the current definition there's a *real* problem - any Error handler
> (usually installed to capture 'real' errors) will go nuts about a trivial
> ReadStream>>next operation. E.g., assuming that you have an app that says
>
> [self runMyApp] on: Error do:[:exception|
>  self dump: exception to: self logFile.
>  self quitApp].
>
> will be triggered by
>
>  (ReadStream on: Array new) next.
>
> Wanna try?! Just load the most recent updates and try to go into PWM7.
> You'll see the effect (since the error handler in PasteUps drawing method is
> intended to catch Errors rather than an end of stream notification). Any
> ideas of how to fix this?!
>
>   - Andreas
>