Re: [clisp-list] errors from socket-status

[Sam S. <sd...@gn...>]

Sam Steingold wrote:
>> * Bruno Haible <oe...@py...> [2008-12-30 02:33:31 +0100]:
>>
>>> Let us start with what we should do at the high level.
>>> We have a stream which will signal ECONNRESET on read.
>> I would vote for signaling a STREAM-ERROR condition - so that the
>> program gets alerted about the abrupt termination of the socket - and
>> at the same time set the stream to a state equivalent to EOF - because
>> ECONNRESET is not a transient error condition.
> 
> cool! this is what we do now - OS_filestream_error.
> no changes needed.

alas, OS_filestream_error signaled a simple OS_error for non-file streams.
this has now been fixed in the CVS.
please take a look at http://clisp.podval.org/impnotes/socket.html#so-status 
(the penultimate sentence documents the possible error signaling by SOCKET-STATUS).