diff options
| author | Robert G. Jakabosky <bobby@sharedrealm.com> | 2011-04-03 20:44:02 +0200 |
|---|---|---|
| committer | Martin Sustrik <sustrik@250bpm.com> | 2011-04-03 20:44:02 +0200 |
| commit | 2c7af35827863b1e0a167298140a38180980502c (patch) | |
| tree | 7360d877164e9e305d7745bb50783c81b67271b9 | |
| parent | 54ea458f629cc380440e1a349ecf572eed2ecbd4 (diff) | |
Add note about thread-safety to zmq_msg_init_data() manpage.
Signed-off-by: Robert G. Jakabosky <bobby@sharedrealm.com>
| -rw-r--r-- | doc/zmq_msg_init_data.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/zmq_msg_init_data.txt b/doc/zmq_msg_init_data.txt index 8378757..a36787c 100644 --- a/doc/zmq_msg_init_data.txt +++ b/doc/zmq_msg_init_data.txt @@ -28,6 +28,9 @@ supplied to _zmq_msg_init_data()_. CAUTION: Never access 'zmq_msg_t' members directly, instead always use the _zmq_msg_ family of functions. +CAUTION: The deallocation function 'ffn' needs to be thread-safe, since it +will be called from an arbitrary thread. + CAUTION: The functions _zmq_msg_init()_, _zmq_msg_init_data()_ and _zmq_msg_init_size()_ are mutually exclusive. Never initialize the same 'zmq_msg_t' twice. |