All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Aaron Peter Bachmann <aaron_ng@inode.at>, mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org
Subject: Re: misleading note in https://man7.org/linux/man-pages/man3/bstring.3.html
Date: Sat, 31 Dec 2022 00:05:16 +0100	[thread overview]
Message-ID: <01e8c816-6b92-5776-722e-7a6c5a45a913@gmail.com> (raw)
In-Reply-To: <4e7589dc-2c5c-d705-e2a9-4b0878bfce3d@inode.at>


[-- Attachment #1.1: Type: text/plain, Size: 776 bytes --]

Hello Aaron Peter,

On 12/30/22 23:43, Aaron Peter Bachmann wrote:
> Hello!
> 
> The note section in https://man7.org/linux/man-pages/man3/bstring.3.html says:
> 
> The functions*bcmp*(),*bcopy*(), and*bzero*() are obsolete.  Use
>         *memcmp*(),*memcpy*(), and*memset*() instead.
> 
> The std-replacement replacement for bcopy() in NOT memcpy() but memmove().
> Thus it should say:
> 
> The functions*bcmp*(),*bcopy*(), and*bzero*() are obsolete.  Use
>         *memcmp*(),*memmove*(), and*memset*() instead.

Thanks!  I fixed it.  And while doing it, I also removed the text that said 
bzero(3) is deprecated.  I encourage its use.

Cheers,

Alex

> 
> Regards, Aaron Peter Bachmann
> 

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-30 23:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 22:43 misleading note in https://man7.org/linux/man-pages/man3/bstring.3.html Aaron Peter Bachmann
2022-12-30 23:05 ` Alejandro Colomar [this message]
2023-01-10  8:17   ` Sam James
2023-01-10 19:08     ` 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=01e8c816-6b92-5776-722e-7a6c5a45a913@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=aaron_ng@inode.at \
    --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 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.