public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
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,
	Ulrich Drepper <drepper@redhat.com>
Subject: [PATCH 22/23] scandir.3: SYNOPSIS: Use 'restrict' in prototypes
Date: Mon,  8 Mar 2021 19:53:31 +0100	[thread overview]
Message-ID: <20210308185331.242176-23-alx.manpages@gmail.com> (raw)
In-Reply-To: <20210308185331.242176-1-alx.manpages@gmail.com>

POSIX does NOT specify scandir() to use 'restrict'.
However, glibc uses 'restrict'.
Users might be surprised by this!  Let's use it here too!

.../glibc$ grep_glibc_prototype scandir
dirent/dirent.h:255:
extern int scandir (const char *__restrict __dir,
		    struct dirent ***__restrict __namelist,
		    int (*__selector) (const struct dirent *),
		    int (*__cmp) (const struct dirent **,
				  const struct dirent **))
     __nonnull ((1, 2));
.../glibc$

Cc: glibc <libc-alpha@sourceware.org>
Cc: Ulrich Drepper <drepper@redhat.com>
Signed-off-by: Alejandro Colomar <alx.manpages@gmail.com>
---
 man3/scandir.3 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man3/scandir.3 b/man3/scandir.3
index 83a5eea7d..262e125c1 100644
--- a/man3/scandir.3
+++ b/man3/scandir.3
@@ -67,7 +67,7 @@ a directory for matching entries
 .nf
 .B #include <dirent.h>
 .PP
-.BI "int scandir(const char *" dirp ", struct dirent ***" namelist ,
+.BI "int scandir(const char *restrict " dirp ", struct dirent ***restrict " namelist ,
 .BI "            int (*" filter ")(const struct dirent *),"
 .BI "            int (*" compar ")(const struct dirent **,"
 .BR "                          const struct dirent **));"
-- 
2.30.1


  parent reply	other threads:[~2021-03-08 18:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 18:53 [PATCH 00/23] man3: SYNOPSIS: Use 'restrict' in prototypes (batch 4) Alejandro Colomar
2021-03-08 18:53 ` [PATCH 01/23] pthread_attr_setschedpolicy.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-08 18:53 ` [PATCH 02/23] pthread_attr_setscope.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 03/23] pthread_attr_setstackaddr.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 04/23] pthread_attr_setstacksize.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 05/23] pthread_attr_setstack.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 06/23] pthread_create.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 07/23] pthread_getattr_default_np.3: SYNOPSIS: Add missing 'const' Alejandro Colomar
2021-03-08 18:53 ` [PATCH 08/23] pthread_mutexattr_getpshared.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-08 18:53 ` [PATCH 09/23] pthread_mutexattr_setrobust.3: SYNOPSIS: Remove incorrect 'const' Alejandro Colomar
2021-03-08 18:53 ` [PATCH 10/23] pthread_rwlockattr_setkind_np.3: SYNOPSIS: Use 'restrict' in prototypes Alejandro Colomar
2021-03-08 18:53 ` [PATCH 11/23] pthread_setschedparam.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 12/23] putgrent.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 13/23] putpwent.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 14/23] puts.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 15/23] qecvt.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 16/23] random_r.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 17/23] rcmd.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 18/23] readdir_r.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 19/23] realpath.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 20/23] regex.3: " Alejandro Colomar
2021-03-08 18:53 ` [PATCH 21/23] rexec.3: " Alejandro Colomar
2021-03-08 18:53 ` Alejandro Colomar [this message]
2021-03-08 18:53 ` [PATCH 23/23] scandir.3: " Alejandro Colomar

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=20210308185331.242176-23-alx.manpages@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=drepper@redhat.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