libc header questions

Hiroki Sakagami sakagami@gmail.com
Tue Sep 20 07:33:00 GMT 2005


On 9/17/05, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> On Sep 17 15:08, Hiroki Sakagami wrote:
> > Hi,
> >
> > I have two questions about libc include headers.
> >
> >   1. Is there any reason socklen_t is defined as a macro
> >      instead of typedef in <cygwin/socket.h>?
> 
> Is this a problem for you?  The reasons are plain historical.  I don't
> see that converting it to a typedef would add a lot functionality, though.

I had a (not-opensourced) package whose autoconf detection of
socklen_t failed.  But that's a problem of that package.  I can
live with a macro definition now.

> >   2. In <arpa/inet.h>, inet_ntop() is not consistent with POSIX.
> >
> >        Cygwin: const char *inet_ntop(int, const void *, char *, size_t);
> >        POSIX:  const char *inet_ntop(int, const void *, char *, socklen_t);
> >        http://www.opengroup.org/onlinepubs/009695399/functions/inet_ntop.html
> >
> >      Is this going to be fixed in the future version?
> 
> I've changed this in CVS.  Thanks for the hint.

OK, thanks.

--
Hiroki Sakagami

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



More information about the Cygwin mailing list