This month's Index
Subject: Re: INVALID_SOCKET symbol conflict
Re: INVALID_SOCKET symbol conflict
From: Alexander Lamaison <swish_at_lammy.co.uk>
Date: Fri, 2 Mar 2012 16:27:45 +0000
On 2 March 2012 16:12, Lawson <lawson08_at_yahoo.com> wrote:
I believe that both these values actually result in the same thing: an
> Note that the SNMP++ header has an #ifdef.
One way to deal with this is to do the same thing so whichever one
> 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.
I guess it *is* a magical special symbol everyone knows about ... if
My personal preference would be to declare our own constant, something
-- Easy SFTP for Windows Explorer (http://www.swish-sftp.org) _______________________________________________ libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-develReceived on 2012-03-02