Date: Fri, 03 Jun 2005 05:26:18 +0900 From: Hajimu UMEMOTO <ume@freebsd.org> To: Daniel Eischen <deischen@freebsd.org> Cc: nectar@freebsd.org, des@des.no, standards@freebsd.org, current@freebsd.org, freebsd-arch@freebsd.org Subject: Re: [CFR] correct type of addrinfo.ai_addrlen and netent.n_net Message-ID: <ygey89s8pzp.wl%ume@mahoroba.org> In-Reply-To: <Pine.GSO.4.43.0506021557130.15736-100000@sea.ntplx.net> References: <yge3bs0a7mh.wl%ume@mahoroba.org> <Pine.GSO.4.43.0506021557130.15736-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,
>>>>> On Thu, 2 Jun 2005 15:59:07 -0400 (EDT)
>>>>> Daniel Eischen <deischen@freebsd.org> said:
> Ultimately, I wish to correct struct addrinfo, too. Since correcting
> getnetbyaddr(3) breaks ABI compatibility after all, it seems storange
> to me to leave struct addrinfo alone as is. It is better to take this
> occasion to correct struct addrinfo as well.
> This breakage is only on 64 bit arch. The influence will grow as 64
> bit arch spreads. So, I believe it should be done as soon as
> possible.
deischen> Just leave it alone for now.
Please clarify what you mean for `it'. Which are you mean only struct
addrinfo issue or both?
deischen> When symbol versioning comes, you should be able to remove
deischen> the padding without bumping library versions and producing
deischen> imcompatibilities.
It's curious. Is there any plan to provide symbol versioning?
Sincerely,
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ygey89s8pzp.wl%ume>