Subject: Re: INVALID_SOCKET symbol conflict

Re: INVALID_SOCKET symbol conflict

From: Peter Stuge <>
Date: Fri, 2 Mar 2012 17:30:04 +0100

Hi, *please* don't double post! Thanks.

Lawson wrote:
> I'm sure I can craft a workaround.

Please send a proper fix instead.

> Mostly I was perplexed at why two different libraries which are
> otherwise both disciplined about defining their constants with a
> namespace prefix both chose to define this one symbol like this,
> like it was some magical special symbol that everyone knew about.

Yes, that's exactly right. But it can of course be wrapped for
non-Windows and arguably this is the good way.

Received on 2012-03-02