bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: socklen_t


From: Albert Chin
Subject: Re: socklen_t
Date: Fri, 2 Sep 2005 09:35:05 -0500
User-agent: Mutt/1.5.6i

On Fri, Sep 02, 2005 at 09:26:16AM +0200, Simon Josefsson wrote:
> Albert Chin <address@hidden> writes:
> 
> > On Thu, Sep 01, 2005 at 01:28:39PM +0200, Simon Josefsson wrote:
> >> Albert Chin <address@hidden> writes:
> >> 
> >> > We created the following macro for curl. It's been tested on the
> >> > following systems:
> >> 
> >> Has the copyright been assigned to the FSF?
> >
> > No. I'd like to see a liberal license with this though. Curl is under
> > a very liberal license. We'd like to see other programs use this macro
> > for detecting socklen_t as well (lftp has adopted a derivative of it
> > and KDE I think has).
> 
> This is what M4 macros in gnulib generally use, is it ok?
> 
> dnl Copyright (C) 2005 Free Software Foundation, Inc.
> dnl This file is free software; the Free Software Foundation
> dnl gives unlimited permission to copy and/or distribute it,
> dnl with or without modifications, as long as this notice is preserved.

Ok, I'll start working on the paperwork.

> > BTW, having socklen_t doesn't mean it's used by some of the networking
> > functions. Check this out:
> >   http://bugs.kde.org/show_bug.cgi?id=78238
> >   http://www.mail-archive.com/address@hidden/msg01246.html
> 
> Ouch.  I don't think the proposed solution was good, I want to use
> "socklen_t" in my code.  I think we should try hard to make that
> possible.  I don't want to make my code unreadable to cater to broken
> platforms.
> 
> However, adapting your M4 code first would solve to problem on several
> platforms, and we can return to the HP-UX problem later.  I haven't
> encountered that problem on HP-UX myself, so perhaps it doesn't always
> happen.

Sounds good. Only lftp and KDE have encountered the problem.

-- 
albert chin (address@hidden)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]