3party/libzmq
0
0
Fork 0
mirror of https://github.com/zeromq/libzmq.git synced 2025-01-14 01:37:56 +08:00
Code Issues Projects Releases Wiki Activity

Problem: Incorrect formatting of documentation in zmq_udp.txt

Browse Source 
Solution: Replace incorrect underline pattern in zmq_udp.txt that
makes part of the text show up as pre-formatted code block with
regular underline pattern.
This commit is contained in:
Nevin Valsaraj 2022-07-22 09:14:31 -07:00
parent 8fd1ec0592
commit ea1962b825
No known key found for this signature in database
GPG Key ID: E4019A33EDD8313C
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/zmq_udp.txt
View File

@ -28,7 +28,7 @@ For the UDP transport, the transport is `udp`.
The meaning of the 'address' part is defined below. The meaning of the 'address' part is defined below.
Binding a socket Binding a socket
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ----------------
With 'udp' we can only bind the 'ZMQ_DISH' socket type. With 'udp' we can only bind the 'ZMQ_DISH' socket type.
When binding a socket using _zmq_bind()_ with the 'udp' When binding a socket using _zmq_bind()_ with the 'udp'
transport the 'endpoint' shall be interpreted as an 'interface' followed by a transport the 'endpoint' shall be interpreted as an 'interface' followed by a
@ -45,7 +45,7 @@ The UDP port number may be specified a numeric value, usually above
1024 on POSIX systems. 1024 on POSIX systems.
Connecting a socket Connecting a socket
~~~~~~~~~~~~~~~~~~~ -------------------
With 'udp' we can only connect the 'ZMQ_RADIO' socket type. With 'udp' we can only connect the 'ZMQ_RADIO' socket type.
When connecting a socket to a peer address using _zmq_connect()_ with the 'udp' When connecting a socket to a peer address using _zmq_connect()_ with the 'udp'
transport, the 'endpoint' shall be interpreted as a 'peer address' followed by transport, the 'endpoint' shall be interpreted as a 'peer address' followed by