Maybe I'm just sleep deprived... but, the method isUnconnected looks
odd. Perhaps it is correct, and there is a good reason for the
implementation, but "socketHandle == nil ifTrue: [^false ]" seems
counter-intuitive. If socketHandle is not defined, then, it seems, we
probably not connected... and hence should answer true.
My apologies if I am not thinking clearly... or if it is simply more
complex handle management.
Socket >>
isUnconnected
"Return true if this socket's state is Unconnected."
socketHandle == nil ifTrue: [^ false].
^ (self primSocketConnectionStatus: socketHandle) == Unconnected
-Cam
On Apr 29, 2009, at 5:00 PM, Alexandre Bergel wrote:
> Does not work for me. The problem is probably different. I still get a
> 'Socket status must Unconnected before opening a new connection'
>
Per
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
