From: Alejandro Colomar <alx.manpages@gmail.com>
To: mtk.manpages@gmail.com
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org
Subject: [PATCH 07/14] gethostbyname.3: SYNOPSIS: Use 'restrict' in prototypes
Date: Sun, 28 Feb 2021 01:48:11 +0100 [thread overview]
Message-ID: <20210228004817.122463-8-alx.manpages@gmail.com> (raw)
In-Reply-To: <20210228004817.122463-1-alx.manpages@gmail.com>
glibc uses 'restrict' in gethostent_r(), gethostbyaddr_r(),
gethostbyname_r(), gethostbyname2_r().
Let's use it here too.
.../glibc$ grep_glibc_prototype gethostent_r
resolv/netdb.h:165:
extern int gethostent_r (struct hostent *__restrict __result_buf,
char *__restrict __buf, size_t __buflen,
struct hostent **__restrict __result,
int *__restrict __h_errnop);
.../glibc$ grep_glibc_prototype gethostbyaddr_r
resolv/netdb.h:170:
extern int gethostbyaddr_r (const void *__restrict __addr, __socklen_t __len,
int __type,
struct hostent *__restrict __result_buf,
char *__restrict __buf, size_t __buflen,
struct hostent **__restrict __result,
int *__restrict __h_errnop);
.../glibc$ grep_glibc_prototype gethostbyname_r
resolv/netdb.h:177:
extern int gethostbyname_r (const char *__restrict __name,
struct hostent *__restrict __result_buf,
char *__restrict __buf, size_t __buflen,
struct hostent **__restrict __result,
int *__restrict __h_errnop);
.../glibc$ grep_glibc_prototype gethostbyname2_r
resolv/netdb.h:183:
extern int gethostbyname2_r (const char *__restrict __name, int __af,
struct hostent *__restrict __result_buf,
char *__restrict __buf, size_t __buflen,
struct hostent **__restrict __result,
int *__restrict __h_errnop);
.../glibc$
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
man3/gethostbyname.3 | 31 ++++++++++++++++++++-----------
1 file changed, 20 insertions(+), 11 deletions(-)
diff --git a/man3/gethostbyname.3 b/man3/gethostbyname.3
index ac1758ca0..d2c456072 100644
--- a/man3/gethostbyname.3
+++ b/man3/gethostbyname.3
@@ -65,18 +65,27 @@ gethostent_r \- get network host entry
/* GNU extensions */
.BI "struct hostent *gethostbyname2(const char *" name ", int " af );
.PP
-.BI "int gethostent_r(struct hostent *" ret ", char *" buf ", size_t " buflen ,
-.BI " struct hostent **" result ", int *" h_errnop );
+.BI "int gethostent_r(struct hostent *restrict " ret ,
+.BI " char *restrict " buf ", size_t " buflen ,
+.BI " struct hostent **restrict " result ,
+.BI " int *restrict " h_errnop );
.PP
-.BI "int gethostbyaddr_r(const void *" addr ", socklen_t " len ", int " type ,
-.BI " struct hostent *" ret ", char *" buf ", size_t " buflen ,
-.BI " struct hostent **" result ", int *" h_errnop );
-.BI "int gethostbyname_r(const char *" name ,
-.BI " struct hostent *" ret ", char *" buf ", size_t " buflen ,
-.BI " struct hostent **" result ", int *" h_errnop );
-.BI "int gethostbyname2_r(const char *" name ", int " af,
-.BI " struct hostent *" ret ", char *" buf ", size_t " buflen ,
-.BI " struct hostent **" result ", int *" h_errnop );
+.BI "int gethostbyaddr_r(const void *restrict " addr ", socklen_t " len \
+", int " type ,
+.BI " struct hostent *restrict " ret ,
+.BI " char *restrict " buf ", size_t " buflen ,
+.BI " struct hostent **restrict " result ,
+.BI " int *restrict " h_errnop );
+.BI "int gethostbyname_r(const char *restrict " name ,
+.BI " struct hostent *restrict " ret ,
+.BI " char *restrict " buf ", size_t " buflen ,
+.BI " struct hostent **restrict " result ,
+.BI " int *restrict " h_errnop );
+.BI "int gethostbyname2_r(const char *restrict " name ", int " af,
+.BI " struct hostent *restrict " ret ,
+.BI " char *restrict " buf ", size_t " buflen ,
+.BI " struct hostent **restrict " result ,
+.BI " int *restrict " h_errnop );
.fi
.PP
.RS -4
--
2.30.1.721.g45526154a5
next prev parent reply other threads:[~2021-02-28 0:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-28 0:48 [PATCH 00/14] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 2) Alejandro Colomar
2021-02-28 0:48 ` [PATCH 01/14] getaddrinfo.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-02-28 0:48 ` [PATCH 02/14] getaddrinfo_a.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 03/14] getdate.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 04/14] getdirentries.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 05/14] getgrent_r.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 06/14] getgrnam.3: " Alejandro Colomar
2021-02-28 0:48 ` Alejandro Colomar [this message]
2021-02-28 0:48 ` [PATCH 08/14] getline.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 09/14] getmntent.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 10/14] getnameinfo.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 11/14] getnetent_r.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 12/14] getprotoent_r.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 13/14] getpwent_r.3: " Alejandro Colomar
2021-02-28 0:48 ` [PATCH 14/14] getpwnam.3: " Alejandro Colomar
2021-03-03 22:25 ` [PATCH 00/14] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 2) Michael Kerrisk (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210228004817.122463-8-alx.manpages@gmail.com \
--to=alx.manpages@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).