|
From: | Holger Hans Peter Freyther |
Subject: | Re: [Help-smalltalk] Re: Exception in the socket code |
Date: | Fri, 25 Mar 2011 15:28:59 +0100 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Lightning/1.0b2 Thunderbird/3.1.9 |
On 03/25/2011 03:23 PM, Paolo Bonzini wrote: he normal Socket>>#atEnd. > > I guess I didn't explain myself very well... sorry, more me being jet-lagged fro my last flight. > > st> (FileDescriptor on: 0) nextAvailable: 1 into: nil startingAt: 1 > > Object: nil error: did not understand #+ > MessageNotUnderstood(Exception)>>signal (ExcHandling.st:254) > UndefinedObject(Object)>>doesNotUnderstand: #+ (SysExcept.st:1407) > FileDescriptor>>nextAvailable:into:startingAt: (FileDescr.st:802) > UndefinedObject>>executeStatements (a String:1) > nil okay, looks very similar. I am not able to reproduce this right now. :) > > I'll apply the Buffers.st part since it's good anyway. hmm. does this mean I can't read data out of a remotely closed socket? Or only when I have called close myself. Sorry for the stupid question.
[Prev in Thread] | Current Thread | [Next in Thread] |