Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem: some inaccuracies in manpages #3016

Merged
merged 3 commits into from
Mar 21, 2018
Merged

Problem: some inaccuracies in manpages #3016

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9f2f30b
Problem: docs say STABLE API still in DRAFT
bluca Mar 21, 2018
dba4ef2
Problem: zmq_close manpage does not say it's asynchronous
bluca Mar 21, 2018
1b733e7
Problem: zmq_connect doc says inproc has to be bound first
bluca Mar 21, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Problem: zmq_close manpage does not say it's asynchronous 
Solution: clarify it since it's a common source of confusion
  • Loading branch information
@bluca
bluca committed Mar 21, 2018
commit dba4ef28cc3419a7fa87b71c2b46ea0996f94a2d
3 changes: 3 additions & 0 deletions doc/zmq_close.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,9 @@ NOTE: The default setting of _ZMQ_LINGER_ does not discard unsent messages;
this behaviour may cause the application to block when calling _zmq_ctx_term()_.
For details refer to linkzmq:zmq_setsockopt[3] and linkzmq:zmq_ctx_term[3].

NOTE: This API will complete asynchronously, so not everything will be deallocated
after it returns. See above for details about linger.


RETURN VALUE
------------
Expand Down