Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Sat, 17 Sep 2005 10:55:46 +0200
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: libc header questions
Message-ID: <20050917085546.GR5555@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <8389af8b0509162308b57a819 AT mail DOT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8389af8b0509162308b57a819@mail.gmail.com>
User-Agent: Mutt/1.4.2i

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.

>   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.


Corinna

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

--
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/