This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug network/16421] IN6_IS_ADDR_UNSPECIFIED can use undefined s6_addr32
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 04 Feb 2014 04:09:45 +0000
- Subject: [Bug network/16421] IN6_IS_ADDR_UNSPECIFIED can use undefined s6_addr32
- Auto-submitted: auto-generated
- References: <bug-16421-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16421
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Rich Felker from comment #3)
> Well in that case a reasonable alternative would be to expose __s6_addr32
> instead of s6_addr32 in standards-conforming mode.
Andreas Schwab comments[1] that the macros should themselves used the internal
__s6_* names instead of the public ones, that way the implementation is always
internally consistent.
I see no reason why we shouldn't do that. It avoids the problem of always
defining s6_addr32 being problematic. It doesn't require any code to check if
you're in POSIX or non-POSIX conformance modes.
[1] https://sourceware.org/ml/libc-alpha/2013-04/msg00564.html
Comments?
--
You are receiving this mail because:
You are on the CC list for the bug.