Removing workaround for ZMQ #1169 as the problem no longer hits
Problem: zhash public API was broken

Changing keys from 'const char *' to 'void *' broke existing applications,
and isn't necessary. The majority use case is for char keys, so the API
can show this. The marginal case is for void * keys, which zhash does
internally without modifying the API. Apps that use non-string keys will
have to cast their keys to 'const char *', which is fine (the alternative
is that all existing apps have to add a cast just to allow a few unusual
apps to not add one.)
Merge pull request #658 from hintjens/master

Removing workaround for ZMQ #1169 as the problem no longer hits
Problem: dropped & in last patch, causing segfault

Solution: run 'make check' before pushing commits :-)
Merge pull request #659 from hintjens/master

Problem: dropped & in last patch, causing segfault
zhash msvc build fixes
Merge pull request #660 from jossgray/msvc_build_fixes

zhash msvc build fixes
Revert "zhash msvc build fixes"

This reverts commit 4f78d78967af511e399a1c37463f16117bdcb4f2.
Revert "Problem: zhash public API was broken"

This reverts commit e337e2d8973e6d74b0cdf73332abae99bb0e1884.

Conflicts:

	src/zhash.c
zhash: Use const void * for keys to remain compatible with const char *
Merge pull request #662 from Q-Leap-Networks/pull-zhash-void-key

Pull zhash void key
zuuid: check for errors in constructor
zthread: Assert context creation
zthread: assert zstr_recv returns a string
zstr: assert message creation
zstr: assert zstr_recv returns a string
zsock: check creation in constructors
zsock: check zsys_vprintf returns a string
zsock: check zmsg_addmem succeeds
zsock: assert constructors succeed in test