Tcl Source Code

<H1>Issue</H1>
On windows, a readable fileevent on a failed async socket connect only fires, if there is also a writable fileevent.

<H1>Examples</H1>
Following examples are in wish so there is an event loop running.

<h2>Only readable fileevent does not fire</h2>

<verbatim>
% set h [socket -async localhost 30001]
sock448
% fileevent $h readable {puts R:[fconfigure $h -error];close $h}
</verbatim>

<h2>Readable and writable fileevent fire both</h2>


Fileevent fires, if there is also a writable file event ( as in bug [794839]):
<verbatim>
% set h [socket -async localhost 30001]
sock448
% fileevent $h readable {puts R:[fconfigure $h -error];close $h}
% fileevent $h writable {puts W}
W
R:connection refused</verbatim>
</verbatim>

<h1>TCL8.6.1</H1>

The same issue is also present in tcl8.6.1, but already fixed in branch bug-13d3af3ad5, checkin [f1d2f6dbad].

Committed to core-8-5-branch by checkin [37dce67f70].

Bug closed.

Fix and test in checkin [29adf4bac3] of branch bug-581937ab1e