Solution: use buffer address instead

(and probably other MSVC versions)

It may even cause BSOD on Windows.

On systems where getifaddrs() exists but isn't implemented, behave as if 'resolve_nic_name()' were entirely unsupported

Solution:
Wrap to lte 80 chars and fix it.

Since ZMQ_USE_SODIUM is nowhere defined i guess it's meant to be ZMQ_USE_LIBSODIUM?

solution: enforce that dish and gram can only bind and radio can only
connect

Solution:
- Add checks for **poller_p_ to ensure that we do not segfault when either it
  or the value within it are NULL
- Add tests for the above and increase error state coverage

Solution:
Mark them with LIBZMQ_UNUSED macro as per convention; although in future the
appropriate pthread code should be updated to support thread scheduling
priorities (for Mac OS X, et. al.)

The TIPC protocol bindings in ZeroMQ defaults to a lookup domain
of 1.0.0 to prevent 'closest first' search, and instead always
do round robin if several sockets in the network or node have
the same name published. In retrospect, this might have been a
bad idea because it won't work on standalone configurations.
We solve this by allowing an optional domain suffix to be provided
in the address, and 0.0.0 should be used in that case, or if the
TIPC address range in the cluster configuration is defined to some
other value. Domain suffixes are only relevant for connecting
addresses.
Signed-off-by: Erik Hugne <erik.hugne@gmail.com>

Solution:
Mark it with LIBZMQ_UNUSED macro as per convention.

Solution:
Mark it with LIBZMQ_UNUSED as per our convention.

Solution:
Indent it.

Solution: add an optional dependency on libunwind, and if present
use it to print the backtrace when zmq_abort is called.

Solution: use socket object's mutex before the send_reap() call that
might deallocate it

Solution:
Wrap and clean it.