From cc534ff767dad4c41e5287f32f0c6283e70ba4ea Mon Sep 17 00:00:00 2001 From: Guillermo Rodriguez Garcia Date: Thu, 16 Mar 2000 21:57:21 +0000 Subject: [PATCH] Removed bool params and retvalues in GSocket interface to avoid mismatch between C-compiled bools in gsocket and C++ real bools as passed by wxSocket git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@6777 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- src/common/socket.cpp | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/src/common/socket.cpp b/src/common/socket.cpp index a3eec9aae2..542adadde6 100644 --- a/src/common/socket.cpp +++ b/src/common/socket.cpp @@ -477,18 +477,6 @@ wxUint32 wxSocketBase::_Write(const void *buffer, wxUint32 nbytes) buffer = (const char *)buffer + ret; } - // Yes, this can happen even when the socket selects as writable! - // (probably due to a buggy kernel; Linux 2.0.36 seems to do this). - // Fake it so that we stay in the loop, but do it only for ret < 0, - // as ret == 0 means that the socket is closed. I'm not applying - // this hack for read calls as it seems unnecessary there. - // - if ((ret < 0) && (GSocket_GetError(m_socket) == GSOCK_WOULDBLOCK)) - { - wxLogDebug(_("wxSocket: working around select() bug in Write.")); - continue; - } - // If we got here and wxSOCKET_WAITALL is not set, we can leave // now. Otherwise, wait until we send all the data or until there // is an error. -- 2.45.2