Will the real sqUnixSocket.c step forward?

John M McIntosh johnmci at smalltalkconsulting.com
Mon May 6 03:42:07 UTC 2002


>Lex Spoon <lex at cc.gatech.edu> wrote:
>
>>  Alternatively, we could mimick the way READ_NOTIFY and WRITE_NOTIFY
>>  get turned on: when the image asks if there is a connection available,
>>  then, if there is not, turn on CONN_NOTIFY.  The place to do this would
>>  be socketStatus().  Simply turn on CONN_NOTIFY if state==WaitingForConnect.
>>  Then all the other places CONN_NOTIFY gets turned on could be eliminated.
>>  This is a slight change in how things are done, but it seems simpler
>>  and easier to get right on the whole.
>
>Okay this is done on SF.  Comanche, Celeste, and Scamper seem to work
>okay in quick trials.  Could others try it?
>
>Lex

Actually Ian has spent a great part of the weekend rewriting 
sqUnixSocket.c and aio.c and sqUnixXWindow.c. Almost all the Socket 
SUnit tests run now. I suspect by tomorrow we should have the loose 
ends wrapped up and a new version up somewhere.

-- 
--
===========================================================================
John M. McIntosh <johnmci at smalltalkconsulting.com> 1-800-477-2659
Corporate Smalltalk Consulting Ltd.  http://www.smalltalkconsulting.com
===========================================================================



More information about the Squeak-dev mailing list