From: <don...@is...> - 2011-04-10 17:33:40
|
I think I've mentioned this before, but am reminded by recent hg activity. We define status for a SOCKET:SOCKET-SERVER or a SOCKET:SOCKET-STREAM to be :ERROR if any i/o operation will cause an ERROR. My first complaint is that I don't know how to interpret "any" above. It could mean either quantifier "for all" or "there exists" in <quantifier> operation op, op on stream will cause an error However, I don't really believe that statement in either case. For instance, as has been pointed out in other recent discussion, EOF is an error. Also, what exactly qualifies as an io operation? Is socket-status an IO operation? Can you give me an example where socket-status returns :error ? One case that seems to qualify is if I close the stream and then call socket-status on it - but this does not return :error either. Instead I get an error from it. My current best guess is that the value NIL is returned when either the operation would block or it would cause an error (other than EOF). |
From: Sam S. <sd...@gn...> - 2011-04-10 21:01:38
|
> * Don Cohen <qba...@vf...3-vap.pbz> [2011-04-10 10:33:36 -0700]: > > I think I've mentioned this before, but am reminded by recent hg > activity. > > We define status for a SOCKET:SOCKET-SERVER or a > SOCKET:SOCKET-STREAM to be :ERROR if any i/o operation will cause > an ERROR. :ERROR means select() says that the fd has an error conditions pending. -- Sam Steingold (http://sds.podval.org/) on Ubuntu 10.10 (maverick) X http://dhimmi.com http://mideasttruth.com http://camera.org http://pmw.org.il http://www.memritv.org http://jihadwatch.org My other CAR is a CDR. |