There are no ipv6 parts in mingw win32api.
Must be added
struct in_addr6, #define IN6ADDR_SETANY(x), etc..
I know that Danny is already working on the winsock headers. So I've reassigned this to him.
I'm having a hard time finding documentation of IN6ADDR_SETANY(x). Can any one tell me what it does?
"etc" is a really big problem. The world is fll of etc's. Which one do you mean?
I have looked through MS Technology Preview for IPV6 and the MS Research IPV6 implentation as well as the PSDK doc's.
The definition of such basic structures as in_addr6 and sockaddr_in6 differs in the three implentations. In fact in_addr6 is now in6_addr (in conformity with RFC 2533) in the Research implentation. The point is that IPV6 is far from production stability, nor, IMO, is the way that the public headers get organised.
The macro IN6ADDR_SETANY(x) is not in any msdn documentation that I could find, nor could I find it in any of the headers that come with the Technology Preview or the Research implementation. There are however, other macros/inline functions in RFC 2553 that serve analogous purpose to what INADDR_ANY, INADDR_BROADCAST, INADDR_LOOPBACK, etc do in IPV4.
I suggest that we postpone fixing this bug until the MS interface becomes more stable and better documented.
In any event, I can't do it any more, since I have looked very intently at the headers - as that was all the documentation I could find.
Incidentally, in the research implemenation, there is reference to GNU-style "extern inline" as a alternative to MSCVER-style "__inline" in the headers. Also each header starts off with
-*- mode: C++; tab-width: 4; indent-tabs-mode: nil -*-
Someone in MS uses GNU emacs.
Logged In: YES
I am going to close this because Ive just commited a patch
that adds a bit of IPv6 support. I haven't added
IN6ADDR_SETANY nor etc because no docs.