New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider that IPv6 is always enabled in Windows code #10185
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It makes sense to assume that Windows supports IPv6 nowadays, I think, but @dra27 knows better.
I would suggest a more defensive change to otherlibs/unix/socket.c
(see below), just because I believe in defensive coding for Unix system programming.
8e0f3a8
to
5fafb6b
Compare
Done, thank you for your review. David actually warned me that you'd want to keep |
Looking at the history, we've actually always been Winsock 2, although it was only when ocamldebug support was merged in 2008 that the "new" ws2_32 library was linked rather than the legacy wsock32. I believe the APIs have been supported since late 1995... even I don't have a VM that old to hand (at least not one I can start-up since, ahem, Microsoft Virtual PC 2004 was superseded by the way less cool Virtual PC 2007) |
5fafb6b
to
264aad8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fine, thanks.
Would you like to add an entry to the Changes file? Your choice. |
IPv6 is always enabled on Windows.
264aad8
to
b9b7b12
Compare
I've added a small Changes entry. I wasn't sure if it was needed for that PR. Thank you! |
Thanks! |
HAS_IPV6
is hardcoded in the build system, support in Windows has been there for a long time, so we can unconditionally use IPv6.