This is still raw and experimental.
To connect through a SOCKS proxy, set ZMQ_SOCKS_PROXY socket option on
socket before issuing a connect call, e.g.:

    zmq_setsockopt (s, ZMQ_SOCKS_PROXY,
        "127.0.0.1:22222", strlen ("127.0.0.1:22222"));
    zmq_connect (s, "tcp://127.0.0.1:5555");

Known limitations:
- only SOCKS version 5 supported
- authentication not supported
- new option is still undocumented

Add documentation for GSSAPI options.

Problem: API violations are treated as recoverable errors

The example is applications passing invalid arguments to a socket option
and then failing to check the return code. The results can be very hard
to diagnose. Here are some threads that show the pain this causes:

* https://github.com/zeromq/zyre/issues/179
* http://lists.zeromq.org/pipermail/zeromq-dev/2014-June/026388.html

One common argument is that a library should never assert, and should
pass errors back to the calling application. The counter argument is
that when an application is broken enough to pass garbage to libzmq,
it cannot be trusted to handle the resulting errors properly. Empirical
evidence from CZMQ, where we systematically assert on bad arguments, is
that this militant approach makes applications more, not less, robust.

I don't see any valid use cases for returning errors on bad arguments,
with one exception: zmq_setsockopt can be used to probe whether libzmq
was e.g. built with CURVE security. I'd argue that it's nasty to use a
side effect like this. If apps need to probe how libzmq was built, this
should be done explicitly, and for ALL build options, not just CURVE.

There are/were no libzmq test cases that check the return code for an
invalid option.

For now I've enabled militant assertions using --with-militant at
configure time. However I'd like to make this the default setting.

Problem: zmq_ctx_get (ZMQ_MAX_SOCKETS) returns gibberish

Code cleanup

Well, not gibberish, but 2^31 on Linux, which is useless. The code
should probably use getrlimit on Linux and other calls depending on
the system. For now I've set the ceiling at 64K.

program dumps core when getpeername() returns EINVAL (#1085)

Fix failed assertion for WSAENOTSOCK

In de9eef30, the error number assigned to WSAENOTSOCK was EFAULT, but
zmq.cpp:919 expects an ENOTSOCK in this case.

Code cleanup

Exclude test_abstract_ipc from non-Linux builds

Corrected installer source path for VS pdb debug symbols file.  Removed ...

Refresh VS 2010/2012 projects and NuGet templ for recent VS2013 updates.

handle WSAEADDRINUSE in tcp_connecter_t::connect

(accidentially used my preferred style)

As mentioned on the mailing list, Windows may return WSAEADDRINUSE when binding
(reconnecting) to a port. Added this to the handled error codes as Pieter
suggested.

Remove copy of platform.hpp for MSVC VS2013 builds

Restore unpathed references to platform.hpp for cmake builds

Exclude MSVC temp files regardless of where they are in builds/msvc

VS set switch /Z7 in debug static (DebugLIB/DebugLTCG) base props.