Closed geirhei closed 3 years ago
You are welcome to add that as a PR. This class however has a very strange API and I would recommend to just use a vector of message_t and send/recv with zmq::send_multipart and zmq::recv_multipart.
I'll have a go at it. I think the class seems quite convenient. Any specific reason why you recommend not using it?
Just looks like a C API ported directly to C++ and looks like there are some footguns when using the *typ functions.
zmq::message_t
already hasbut there is no similar one for
zmq::multipart_t
. It only has an equal-function taking in a pointer:Having the operator== implemented for
multipart_t
as well would be very handy when writing tests.