> Shouldn't that parameter be a SOCKET rather than a gint? _I_ am
> being a good little Windows programmer :) and declaring all my
> sockets as SOCKET as I'm supposed to, but the above then causes
> problems. I'm guessing that in a 64-bit compile environment a
> SOCKET is a 64-bit quantity rather than 32.
It can't be a SOCKET because we don't want to have to include
<winsock2.h>.
Is there a technical reason, or is it a question of style?
It should be some other integer type that is 32 bits on
Win32 and 64 bits on Win64. Hopefully this can be handled without any
need for #ifdefs.
IIRC there is a similar issue with the routine that returns the SOCKET
(or HANDLE) from a channel. Its return type is gint.
rick
--tml
_______________________________________________
gtk-list@xxxxxxxxx
http://mail.gnome.org/mailman/listinfo/gtk-list
