[zeromq-dev] zmq_msg_move

KIU Shueng Chuan nixchuan at gmail.com
Wed Dec 11 11:08:28 CET 2013


Took a look at the high level C++ binding. It already does all that my
single file template does.

I use some modules of czmq under C++ and felt that it didn't make sense to
be using zframe, zmsg, zstr under C++.
On Dec 10, 2013 5:20 PM, "Pieter Hintjens" <ph at imatix.com> wrote:

> On Mon, Dec 9, 2013 at 3:23 PM, KIU Shueng Chuan <nixchuan at gmail.com>
> wrote:
> > 1) yes, needed.
> > 2) yes, it should. After the move, the origin message returns to an
> init-ed
> > state. You could get away with not closing, but in my opinion that
> relies on
> > knowing the underlying implementation.
> > 3) yes. However in this case, closing the origin message is mandatory.
> > (Unless you also know that very short messages are copied and not shared)
>
> Would you like to make a patch to the man page?
>
> > I implemented a simple multi part message c++ wrapper using the move and
> > copy functions.
> > https://github.com/pijyoi/msg_parts/blob/master/msg_parts.hpp
>
> Consider adding this to the C++ high level binding... (we may also
> want to rename that to cppzmq, and move the current cppzmq .h file
> back into libzmq).
>
> -Pieter
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20131211/bd270300/attachment.htm>


More information about the zeromq-dev mailing list