On Fri, Sep 7, 2012 at 10:55 AM, wrote:
Sorry, but I still fail to see the need for these changes. Perhaps, we
could keep the test, but since I do not understand what it does, I can't
say if it is good idea or not.
otherwise it fails to build
I can see it is called once from ipv4/sockopt_windows.go. You might as
well implement it in go.net then.
yup, looks like that's the point.
I now plan to implement go.net/ipv4 and go.net/ipv6. those two will use
Get/SetsockoptInt, SetsockoptIPMreq, IPv6Mreq and siblings.
I think we have two options.
a) syscall provides Setsockopt and Getsockopt
other optional thin wrappers like GetsockoptInt, SetsockoptIPMreq,
IPv6Mreq, blah blah should be implemented in each package
b) syscall provides a bit detailed GetsockoptInt, SetsockoptIPMreq, etc
(b) works well for Unix families; BSD bros, a cousin Darwin and a second
cousin Liunx but I'm not sure for Windows families including 2000, XP, Vista
Do you have any suggestions or ideas?