Solution: allow for '[' character when doing the basic sanity check
on the TCP endpoint.
Also add unit tests for both IPv4 and IPv6 source;dest format.

Solution: add them

Solution: add a test for this use case

Solution: add disconnect and unbind calls to the test

Solution: refactor it to allow for multiple functionalities to be
tested

Solution: Add "\n" at end of format string.

Solution: ifdef is_ipv6_available to always return false if building
on Windows XP, as it doesn't support the needed standard libc
functions

Solution: call the function after the zmq_ctx has been created, not
before, so that the relevant Windows system calls have been setup.

This reverts commit 9adf20aa.

This is required as zmq_ctx_new calls WSAStartup. Without that the IPV6
socket creation always fails.

Solution: correct path is ../src/windows.hpp. Also added automatic linking
of iphlpapi library if required and using MSVC

only if the library is found at a specific path

Solution: Search for libzmq.lib in ../bin/Win32/Debug/v120/dynamic, don't
know how to automatically search in correct path based on current build
configuration

Expect custom messages on both explicit unsubscription and pipe termination.

Solution:
Wrap it.

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

Solution:
Reduce send count so that the test does not timeout on AppVeyor CI
environment and older Windows boxes.

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:
- Add error state coverage for zmq_ctx_term(), zmq_term() and
  zmq_ctx_shutdown(); zmq_ctx_destroy() is already covered since it only
  calls zmq_ctx_term()
- Add coverage for zmq_term()

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:
- Add file for testing ancillary API methods and any misc internal machinery
- Add tests for zmq_version(3) and zmq_strerror(3)
- Add test file into gitignore, Autotools and CMake build files
- Increase test coverage

Note:
MSVC solution files have not been updated.

Solution: mark them as DRAFT APIs

Solution: mark them as DRAFT APIs

Solution: mark them as DRAFT APIs

Solution: mark them as DRAFT APIs

Solution: mark them as DRAFT APIs

Solution: add support for --enable-drafts/ENABLE_DRAFTS=ON in
Autools and CMake.

Solution: only use ZMQ_SERVER/CLIENT if the defines are available.

Solution: before including internal headers, include platform.hpp
so that the build time options are correctly applied to the included
headers.

Solution:
Put them in the right order to quiet Coverity.

Found by:
Coverity Scan

Solution:
- Add check for the [count] parameter in zmq_sendiov() and zmq_recviov()
- Use and add test for zmq_sendiov() in tests/test_iov.cpp
- Add error state tests for zmq_sendiov() in tests/test_iov.cpp
- Add error state tests for zmq_recviov() in tests/test_iov.cpp
- Cleanup tests/test_iov.cpp for style, consistency and clarity
- Generally improve test coverage for both API methods

Hat-tip:
@somdoron, @bluca