diff options
| author | Alejandro Colomar <alx@kernel.org> | 2024-11-17 18:47:53 +0100 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2024-11-17 21:51:23 +0100 |
| commit | 18e7c4597c4e72fa5210c7887273e363c456c9ee (patch) | |
| tree | 97cfd22e731a4c859ae71783d70943ff72e6cb60 /man/man2/send.2 | |
| parent | 8fc6fdd8291d906e58a175b5e1b20da680aaeb4a (diff) | |
| download | man-pages-18e7c4597c4e.tar.gz | |
man/: Terminology consistency reforms (n, size, length)
Use 'length' for the lenght of a string.
Use 'n' for the number of elements.
Use 'size' for the number of bytes. (And in wide-character string
functions, 'size' also refers to the number of wide characters.)
The change is quite large, and I might have made some mistakes.
But overall, this should improve consistency in use of these terms.
Signed-off-by: Alejandro Colomar <alx@kernel.org>
Diffstat (limited to 'man/man2/send.2')
| -rw-r--r-- | man/man2/send.2 | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/man/man2/send.2 b/man/man2/send.2 index b14ef12374..82aae39230 100644 --- a/man/man2/send.2 +++ b/man/man2/send.2 @@ -19,9 +19,9 @@ Standard C library .nf .B #include <sys/socket.h> .P -.BI "ssize_t send(int " sockfd ", const void " buf [. len "], size_t " len \ +.BI "ssize_t send(int " sockfd ", const void " buf [. size "], size_t " size \ ", int " flags ); -.BI "ssize_t sendto(int " sockfd ", const void " buf [. len "], size_t " len \ +.BI "ssize_t sendto(int " sockfd ", const void " buf [. size "], size_t " size \ ", int " flags , .BI " const struct sockaddr *" dest_addr ", socklen_t " addrlen ); .BI "ssize_t sendmsg(int " sockfd ", const struct msghdr *" msg \ @@ -56,7 +56,7 @@ Also, the following call .P .in +4n .EX -send(sockfd, buf, len, flags); +send(sockfd, buf, size, flags); .EE .in .P @@ -64,7 +64,7 @@ is equivalent to .P .in +4n .EX -sendto(sockfd, buf, len, flags, NULL, 0); +sendto(sockfd, buf, size, flags, NULL, 0); .EE .in .P @@ -106,8 +106,8 @@ and .BR sendto (), the message is found in .I buf -and has length -.IR len . +and has size +.IR size . For .BR sendmsg (), the message is pointed to by the elements of the array @@ -282,7 +282,7 @@ struct msghdr { struct iovec *msg_iov; /* Scatter/gather array */ size_t msg_iovlen; /* # elements in msg_iov */ void *msg_control; /* Ancillary data, see below */ - size_t msg_controllen; /* Ancillary data buffer len */ + size_t msg_controllen; /* Ancillary data buffer size */ int msg_flags; /* Flags (unused) */ }; .EE @@ -310,7 +310,7 @@ You may send control information (ancillary data) using the and .I msg_controllen members. -The maximum control buffer length the kernel can process is limited +The maximum control buffer size the kernel can process is limited per socket by the value in .IR /proc/sys/net/core/optmem_max ; see |