Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
L
libzmq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
libzmq
Commits
df012358
Commit
df012358
authored
Apr 27, 2013
by
Ian Barber
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #551 from hintjens/master
zmq_msg_close clarification in man pages
parents
522765be
cb2ee7a5
Hide whitespace changes
Inline
Side-by-side
Showing
4 changed files
with
7 additions
and
3 deletions
+7
-3
.gitignore
.gitignore
+1
-0
zmq_msg_close.txt
doc/zmq_msg_close.txt
+2
-1
zmq_msg_send.txt
doc/zmq_msg_send.txt
+2
-1
Makefile.am
tests/Makefile.am
+2
-1
No files found.
.gitignore
View file @
df012358
...
...
@@ -46,6 +46,7 @@ tests/test_disconnect_inproc
tests/test_raw_sock
tests/test_disconnect_inproc
tests/test_ctx_options
tests/test_iov
src/platform.hpp*
src/stamp-h1
perf/local_lat
...
...
doc/zmq_msg_close.txt
View file @
df012358
...
...
@@ -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.
...
...
doc/zmq_msg_send.txt
View file @
df012358
...
...
@@ -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
...
...
tests/Makefile.am
View file @
df012358
...
...
@@ -21,7 +21,7 @@ noinst_PROGRAMS = test_pair_inproc \
test_raw_sock
\
test_disconnect_inproc
\
test_ctx_options
\
test_iov
test_iov
if
!ON_MINGW
noinst_PROGRAMS
+=
test_shutdown_stress
\
...
...
@@ -48,6 +48,7 @@ test_router_mandatory_SOURCES = test_router_mandatory.cpp
test_raw_sock_SOURCES
=
test_raw_sock.cpp
test_disconnect_inproc_SOURCES
=
test_disconnect_inproc.cpp
test_ctx_options_SOURCES
=
test_ctx_options.cpp
test_iov_SOURCES
=
test_iov.cpp
if
!ON_MINGW
test_shutdown_stress_SOURCES
=
test_shutdown_stress.cpp
test_pair_ipc_SOURCES
=
test_pair_ipc.cpp testutil.hpp
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment