[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: winsock: needs access to SOCKET in application code
From: |
Bruno Haible |
Subject: |
Re: winsock: needs access to SOCKET in application code |
Date: |
Thu, 16 Oct 2008 00:42:10 +0200 |
User-agent: |
KMail/1.5.4 |
Hi Simon,
> > The return type should be SOCKET, which is either `unsigned int' or
> > 'unsigned long' (don't know about win64).
>
> How would that work on non-Mingw systems? The idea should be that gsasl
> calls the function unconditionally, in order to work around limitations
> of the gnulib winsock wrappers.
Hmm, I thought the function would be defined only on native Win32 systems,
since its return type 'SOCKET' does not exist on Unix, and we don't want
Win32 types to be used in code meant to compile on Unix. (Emulate POSIX
on Win32, not vice versa.)
But I have no definite opinion on this.
Bruno
- winsock: needs access to SOCKET in application code, Simon Josefsson, 2008/10/13
- Re: winsock: needs access to SOCKET in application code, Bruno Haible, 2008/10/13
- Re: winsock: needs access to SOCKET in application code, Paolo Bonzini, 2008/10/14
- Re: winsock: needs access to SOCKET in application code, Simon Josefsson, 2008/10/14
- Re: winsock: needs access to SOCKET in application code, Paolo Bonzini, 2008/10/14
- Re: winsock: needs access to SOCKET in application code, Bruno Haible, 2008/10/14
- Re: winsock: needs access to SOCKET in application code, Simon Josefsson, 2008/10/15
- Re: winsock: needs access to SOCKET in application code,
Bruno Haible <=
- Re: winsock: needs access to SOCKET in application code, Simon Josefsson, 2008/10/16
Re: winsock: needs access to SOCKET in application code, Simon Josefsson, 2008/10/14