[Xcb] [PATCH 3/3] Use WSAStartup()/WSACleanup() on WIN32

Peter Harris pharris at opentext.com
Fri Jan 6 09:31:00 PST 2012

On 2012-01-06 12:12, Jon TURNEY wrote:
> On 06/01/2012 03:38, Josh Triplett wrote:
>> On Thu, Jan 05, 2012 at 04:29:47PM -0600, Ryan Pavlik wrote:
>>> On Thu, Jan 5, 2012 at 3:28 PM, Josh Triplett <josh at joshtriplett.org> wrote:
>>>> On Thu, Jan 05, 2012 at 08:57:54PM +0000, Jon TURNEY wrote:
>>>> What happens if the application using XCB has already called WSAStartup,
>>>> and passes a lower version number than 2.2?  Will XCB's call to
>>>> WSAStartup cause Winsock to start assuming 2.2 semantics instead of
>>>> whatever older semantics the application requested?  Or will Winsock
>>>> just tell XCB to use the older version?  In the latter case, can XCB
>>>> live with that?
>>> I'm not sure, but 2.2 is available since a patch for Windows 95, so I'm
>>> pretty confident that it's a safe alternative.
>> I definitely don't care about the case where the system has an older
>> Winsock; I just wondered what would happen if the application using XCB
>> called WSAStartup first, with a lower version number.
> This is an excellent question.  Unfortunately, I can't find an answer in MSDN,
> and it seems nobody knows (or at least google doesn't know :-)).

MSDN, at least, does say that you can call WSAStartup multiple times
with different versions in the same app. It doesn't say what happens if
you do that, but it doesn't say that anything dire happens.

Given that the newer versions are, for the most part, a superset of the
functionality of the old versions, I suspect it allows all the
functionality the highest version ever requested.

More information about the Xcb mailing list