From 597cc5edd624525563e6549dc0057eca2a51c81d Mon Sep 17 00:00:00 2001 From: Micah Anderson Date: Tue, 11 Nov 2014 13:30:46 -0500 Subject: upgrade to new version --- doc/zmq_msg_close.html | 826 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 826 insertions(+) create mode 100644 doc/zmq_msg_close.html (limited to 'doc/zmq_msg_close.html') diff --git a/doc/zmq_msg_close.html b/doc/zmq_msg_close.html new file mode 100644 index 0000000..c038689 --- /dev/null +++ b/doc/zmq_msg_close.html @@ -0,0 +1,826 @@ + + + + + +zmq_msg_close(3) + + + + + +
+
+

SYNOPSIS

+
+

int zmq_msg_close (zmq_msg_t *msg);

+
+
+
+

DESCRIPTION

+
+

The zmq_msg_close() function shall inform the ØMQ infrastructure that any +resources associated with the message object referenced by msg are no longer +required and may be released. Actual release of resources associated with the +message object shall be postponed by ØMQ 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. 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.
+
+
+
+
+

RETURN VALUE

+
+

The zmq_msg_close() function shall return zero if successful. Otherwise +it shall return -1 and set errno to one of the values defined below.

+
+
+
+

ERRORS

+
+
+
+EFAULT +
+
+

+Invalid message. +

+
+
+
+
+ +
+

AUTHORS

+
+

This page was written by the ØMQ community. To make a change please +read the ØMQ Contribution Policy at http://www.zeromq.org/docs:contributing.

+
+
+
+

+ + + -- cgit v1.2.3