}
static void sk_tcp_close(Socket s);
-static int sk_tcp_write(Socket s, char *data, int len);
-static int sk_tcp_write_oob(Socket s, char *data, int len);
+static int sk_tcp_write(Socket s, const char *data, int len);
+static int sk_tcp_write_oob(Socket s, const char *data, int len);
static void sk_tcp_set_private_ptr(Socket s, void *ptr);
static void *sk_tcp_get_private_ptr(Socket s);
static void sk_tcp_set_frozen(Socket s, int is_frozen);
}
}
-static int sk_tcp_write(Socket sock, char *buf, int len)
+static int sk_tcp_write(Socket sock, const char *buf, int len)
{
Actual_Socket s = (Actual_Socket) sock;
return bufchain_size(&s->output_data);
}
-static int sk_tcp_write_oob(Socket sock, char *buf, int len)
+static int sk_tcp_write_oob(Socket sock, const char *buf, int len)
{
Actual_Socket s = (Actual_Socket) sock;
/* wParam is the socket itself */
- /*
- * One user has reported an assertion failure in tree234 which
- * indicates a null element pointer has been passed to a
- * find*234 function. The following find234 is the only one in
- * the whole program that I can see being capable of doing
- * this, hence I'm forced to conclude that WinSock is capable
- * of sending me netevent messages with wParam==0. I want to
- * know what the rest of the message is if it does so!
- */
- if (wParam == 0) {
- char *str;
- str = dupprintf("Strange WinSock message: wp=%08x lp=%08x",
- (int)wParam, (int)lParam);
- logevent(NULL, str);
- connection_fatal(NULL, str);
- sfree(str);
- }
+ if (wParam == 0)
+ return 1; /* boggle */
s = find234(sktree, (void *) wParam, cmpforsearch);
if (!s)