socklen_t type

[Corinna Vinschen]

On Jul 29 13:30, Eric Blake wrote:
> Is there any specific reason why socklen_t on cygwin is int instead
> of uint32_t, like it is on Linux?

Other than history?  No, I don't think so.  But I also don't think
it's worth the effort.  All the underlying Windows functions typically
use int rather than uint32_t, and even the Linux man page states:

  The optlen argument of getsockopt() and setsockopt() is in reality an
  int [*] (and this is what 4.x BSD and libc4 and libc5 have).  Some
  POSIX confusion resulted in the present socklen_t, also used by glibc.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple