2010-02-10 16:18:46 +01:00
|
|
|
zmq_msg_close(3)
|
|
|
|
================
|
|
|
|
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
2010-03-09 18:47:31 +01:00
|
|
|
zmq_msg_close - release 0MQ message
|
2010-02-10 16:18:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
2010-03-09 18:47:31 +01:00
|
|
|
*int zmq_msg_close (zmq_msg_t '*msg');*
|
2010-02-10 16:18:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
2010-03-09 18:47:31 +01:00
|
|
|
The _zmq_msg_close()_ function shall inform the 0MQ 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 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.
|
|
|
|
|
|
|
|
CAUTION: Never access 'zmq_msg_t' members directly, instead always use the
|
|
|
|
_zmq_msg_ family of functions.
|
2010-02-10 16:18:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
RETURN VALUE
|
|
|
|
------------
|
2010-03-09 18:47:31 +01:00
|
|
|
The _zmq_msg_close()_ function shall return zero if successful. Otherwise
|
2010-03-10 12:19:39 +01:00
|
|
|
it shall return `-1` and set 'errno' to one of the values defined below.
|
2010-02-10 16:18:46 +01:00
|
|
|
|
|
|
|
|
|
|
|
ERRORS
|
|
|
|
------
|
|
|
|
No errors are defined.
|
|
|
|
|
|
|
|
|
|
|
|
SEE ALSO
|
|
|
|
--------
|
|
|
|
linkzmq:zmq_msg_init[3]
|
|
|
|
linkzmq:zmq_msg_init_size[3]
|
|
|
|
linkzmq:zmq_msg_init_data[3]
|
2010-03-09 18:47:31 +01:00
|
|
|
linkzmq:zmq_msg_data[3]
|
|
|
|
linkzmq:zmq_msg_size[3]
|
|
|
|
linkzmq:zmq[7]
|
2010-02-10 16:18:46 +01:00
|
|
|
|
|
|
|
|