[krbdev.mit.edu #6041] WIN32 SOCKET != int in gss and rpc libs

[Jeffrey Altman via RT]

Ken Raeburn via RT wrote:
> closesocket returns an int as close does.  If we're intentionally  
> ignoring the return values, please keep the (void) casts, at least for  
> now.

sure although I don't understand why ignoring that return value should 
be treated specially.

> Why do you need to define INVALID_SOCKET in svc_udp.c?

INVALID_SOCKET is a special value on Windows which is architecture 
dependent.  Is INVALID_SOCKET defined somewhere else for Unix?