From a4b74a7b05e9631be9593018092fbfb292600bea Mon Sep 17 00:00:00 2001 From: Luca Boccassi Date: Mon, 19 Mar 2018 20:15:24 +0000 Subject: [PATCH] Problem: ZMQ_ZERO_COPY_RCV not marked as DRAFT in docs Solution: update manpages --- doc/zmq_ctx_get.txt | 1 + doc/zmq_ctx_set.txt | 1 + 2 files changed, 2 insertions(+) diff --git a/doc/zmq_ctx_get.txt b/doc/zmq_ctx_get.txt index 10cba5af..1ff6871f 100644 --- a/doc/zmq_ctx_get.txt +++ b/doc/zmq_ctx_get.txt @@ -43,6 +43,7 @@ ZMQ_ZERO_COPY_RCV: Get message decoding strategy ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The 'ZMQ_ZERO_COPY_RCV' argument return whether message decoder uses a zero copy strategy when receiving messages. Default value is 1. +NOTE: in DRAFT state, not yet available in stable releases. ZMQ_SOCKET_LIMIT: Get largest configurable number of sockets diff --git a/doc/zmq_ctx_set.txt b/doc/zmq_ctx_set.txt index f461b8e2..e350059d 100644 --- a/doc/zmq_ctx_set.txt +++ b/doc/zmq_ctx_set.txt @@ -134,6 +134,7 @@ use a zero copy strategy when receiving messages. The zero copy strategy can lead to increased memory usage in some cases. This option allows you to use the older copying strategy. You can query the value of this option with linkzmq:zmq_ctx_get[3] using the 'ZMQ_ZERO_COPY_RECV' option. +NOTE: in DRAFT state, not yet available in stable releases. [horizontal] Default value:: 1