|
| From: | Holger Hans Peter Freyther |
| Subject: | Re: [Help-smalltalk] Timeouts for BlockClosures |
| Date: | Thu, 21 Apr 2011 10:41:41 +0200 |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110411 Lightning/1.0b2 Thunderbird/3.1.9 |
On 04/21/2011 07:52 AM, Paolo Bonzini wrote:
> but you're walking on thin ice here. Every time you have a timeout,
> you should assume that the data structures are in an inconsistent
> state (just like when you #terminate a Process). I suggest making
> your sockets unbuffered if it's not too much overhead.
Right. It is not Erlang after all and we have side-effects. I am not sure on
the semantics of the following. My work around would be something like
[
socket waitUntilItCanRead
] timeout...
but I am not sure if canRead and such will behave better.
| [Prev in Thread] | Current Thread | [Next in Thread] |