From: Vadim Zeitlin Date: Sat, 27 Dec 2008 18:01:59 +0000 (+0000) Subject: map EAGAIN to wxSOCKET_WOULDBLOCK too as tit has this meaning for read() (even though... X-Git-Url: https://git.saurik.com/wxWidgets.git/commitdiff_plain/42dfe2b25975537db8bb54ab104385748ff7d175 map EAGAIN to wxSOCKET_WOULDBLOCK too as tit has this meaning for read() (even though it doesn't have it for connect()) git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@57603 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- diff --git a/src/unix/sockunix.cpp b/src/unix/sockunix.cpp index 60143e73a1..d0cd4e198f 100644 --- a/src/unix/sockunix.cpp +++ b/src/unix/sockunix.cpp @@ -453,6 +453,10 @@ wxSocketError wxSocketImplUnix::GetLastError() const case ENOTSOCK: return wxSOCKET_INVSOCK; + // unfortunately EAGAIN only has the "would block" meaning for read(), + // not for connect() for which it means something rather different but + // we can't distinguish between these two situations currently... + case EAGAIN: case EINPROGRESS: return wxSOCKET_WOULDBLOCK;