All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: memcpy.2: missing restrict keyword
Date: Mon, 28 Dec 2020 10:25:48 +0100	[thread overview]
Message-ID: <105b8883-d6a8-b3c3-3aff-ee1d6e88980a@gmail.com> (raw)
In-Reply-To: <5a8997be-479b-d813-ce7a-558a8e6633e9@gmx.de>

Hi Heinrich,

I agree.  That's on my todo list.

I'm first fixing the prototypes for syscalls, which have significant
deviations, then I'll have a look at glibc wrappers, and then I'll fix
glibc library calls.

Thanks,

Alex

On 12/27/20 9:01 PM, Heinrich Schuchardt wrote:
> Hello Michael,
> 
> Since C99 the memcpy is defined as
> 
> void *memcpy(void* restrict dst, const void* restrict src, size_t n);
> 
> Shouldn't the restrict keyword be shown in the prototype on the man-page?
> 
> Other concerned functions include:
> 
> memccpy(), strcat(), strncat, strcpy(), strncpy(), strxfrm(), strtok(),
> strtok_r(), printf()-family, fcvt_r(), strtoimax()-family,
> getmntent_r(), ...
> 
> Just grep for restrict in the standard includes.
> 
> Best regards
> 
> Heinrich

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      reply	other threads:[~2020-12-28  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-27 20:01 memcpy.2: missing restrict keyword Heinrich Schuchardt
2020-12-28  9:25 ` Alejandro Colomar (man-pages) [this message]

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=105b8883-d6a8-b3c3-3aff-ee1d6e88980a@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=xypron.glpk@gmx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.