From 7e129a405ce42724df42cfbd2102e5938b3595cd Mon Sep 17 00:00:00 2001 From: Pieter Hintjens Date: Sat, 27 Apr 2013 12:48:29 +0200 Subject: [PATCH] Clarified zmq_msg_close not needed after zmq_msg_send --- doc/zmq_msg_close.txt | 3 ++- doc/zmq_msg_send.txt | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/zmq_msg_close.txt b/doc/zmq_msg_close.txt index 1d8ddcfd..e67538b6 100644 --- a/doc/zmq_msg_close.txt +++ b/doc/zmq_msg_close.txt @@ -21,7 +21,8 @@ message object shall be postponed by 0MQ until all users of the message or underlying data buffer have indicated it is no longer required. Applications should ensure that _zmq_msg_close()_ is called once a message is -no longer required, otherwise memory leaks may occur. +no longer required, otherwise memory leaks may occur. Note that this is NOT +necessary after a successful _zmq_msg_send()_. CAUTION: Never access 'zmq_msg_t' members directly, instead always use the _zmq_msg_ family of functions. diff --git a/doc/zmq_msg_send.txt b/doc/zmq_msg_send.txt index 750b16dd..099eaf6c 100644 --- a/doc/zmq_msg_send.txt +++ b/doc/zmq_msg_send.txt @@ -38,7 +38,8 @@ it using (e.g. using _zmq_msg_copy()_). NOTE: A successful invocation of _zmq_msg_send()_ does not indicate that the message has been transmitted to the network, only that it has been queued on -the 'socket' and 0MQ has assumed responsibility for the message. +the 'socket' and 0MQ has assumed responsibility for the message. You do not need +to call _zmq_msg_close()_ after a successful _zmq_msg_send()_. Multi-part messages