Simon Giesecke

The name is badly chosen, the function determines whether the socket has not been closed (which could be termed "open", although libzmq does not use that term IIRC). Querying whether...

@maxlein I don't think this is a question related to cppzmq, but to libzmq itself. But I think in general errno must only be evaluated after a function has indicated...

If you like, provide a PR to improve the Readme file.

Any update on this? Is there anything you need to address the comments? Sorry I didn't get back until now, but from reading your responses I assumed that most things...

> I'm also missing this feature. Why not making monitor_t inherit from socket_t? I think it is not necessary, it would be sufficient if a method were added to `monitor_t`...

Agree with regard to the type safety of the flags parameter. Regarding gsl, I am hesitant to adding a dependency to that, as it might make the integration of cppzmq...

Maybe that depends. The send flags are only used as input parameters, so operator | is probably sufficient for most uses. Other flags that are also results should have operator...

EAGAIN is intentionally not thrown, since it is a normal result rather than an error in nonblocking calls. However, the API might not be designed properly to be (easily) usable....

Sorry there is no proper documentation or example for this. I can give some basic hints, which hopefully are helpful to you: You don't need monitor_socket, which is doing what...

You can do it. In that case do not use `zmq::monitor_t`, but call the C `zmq_socket_monitor` function, and then you can use a `zmq::socket_t` again to connect your monitor client.