• Patrik Wenger's avatar
    Problem: tricky return value from zmq::socket_poller_t::wait when poller is empty · 621c965f
    Patrik Wenger authored
    Solution: return -1 (no event) instead of 0 (event)
    
    For some reason, this just returns 0 if there are no sockets registered
    on the poller. Usually this would mean there has been an event. So the
    caller would have to check the return value AND the event, or write code
    that takes the number of registered sockets into consideration.
    
    By returning -1 and setting errno = ETIMEDOUT like in the usual timeout
    cases, it's more consistent and convenient.
    
    Test case included.
    621c965f
Name
Last commit
Last update
builds Loading commit data...
doc Loading commit data...
include Loading commit data...
m4 Loading commit data...
packaging Loading commit data...
perf Loading commit data...
src Loading commit data...
tests Loading commit data...
tools Loading commit data...
.gitignore Loading commit data...
.hgeol Loading commit data...
.mailmap Loading commit data...
.travis.yml Loading commit data...
AUTHORS Loading commit data...
CMakeLists.txt Loading commit data...
COPYING Loading commit data...
COPYING.LESSER Loading commit data...
Dockerfile Loading commit data...
FindSodium.cmake Loading commit data...
INSTALL Loading commit data...
MAINTAINERS Loading commit data...
Makefile.am Loading commit data...
NEWS Loading commit data...
README.cygwin.md Loading commit data...
README.md Loading commit data...
acinclude.m4 Loading commit data...
appveyor.yml Loading commit data...
autogen.sh Loading commit data...
branding.bmp Loading commit data...
ci_build.sh Loading commit data...
configure.ac Loading commit data...
installer.ico Loading commit data...
version.sh Loading commit data...