[PATCH] Re: IP_MULTICAST_IF et all / Winsock[2] value conflict

[Brian Ford]

On Tue, 18 Oct 2005, Corinna Vinschen wrote:

> What I can comment about is what happened when loading set/getsockopt.
> Regardless of being dynamically loaded from wsock32 or ws2_32, they
> will always be the Winsock2 version on a Winsock2 system.  wsock32 is
> more or less just a stub which redirects function calls to ws2_32.dll.

Agreed, but I was under the impression that the wsock32 stub should have
been doing the translation for us.  Otherwise, an application designed
to work with wsock32 would be using incorrect values.

> However, I hope that's a non-issue now that Winsock1 has been dropped.

I hope so too.  I'll test as soon as it is possible.  Thanks again.

-- 
Brian Ford
Senior Realtime Software Engineer
VITAL - Visual Simulation Systems
FlightSafety International
the best safety device in any aircraft is a well-trained pilot...