public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page bcmp.3.
Date: Wed, 1 Nov 2023 17:24:45 +0100	[thread overview]
Message-ID: <ZUJ7zYWY2yspm3Ec@debian> (raw)
In-Reply-To: <ZUJaZPqi0HGylv3K@meinfjell.helgefjelltest.de>

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Hi Helge,

On Wed, Nov 01, 2023 at 02:02:12PM +0000, Helge Kreutzmann wrote:
> Without further ado, the following was found:
> 
> Issue:    Who is "it"?
> "B<bcmp>()  is identical to B<memcmp>(3); use it instead."

Considering that the rest of the page is there just to say this function
is deprecated and even removed from POSIX, I guess a suggestion to use
'it' can only mean use the other one, that is, memcmp(3).

Here's the entire page:

	bcmp(3)                Library Functions Manual                bcmp(3)

	NAME
	     bcmp - compare byte sequences

	LIBRARY
	     Standard C library (libc, -lc)

	SYNOPSIS
	     #include <strings.h>

	     [[deprecated]] int bcmp(const void s1[.n], const void s2[.n], size_t n);

	DESCRIPTION
	     bcmp() is identical to memcmp(3); use it instead.

	STANDARDS
	     None.

	HISTORY
	     4.3BSD.    Marked   as   LEGACY   in   POSIX.1‐2001;  removed  in
	     POSIX.1‐2008.

	SEE ALSO
	     memcmp(3)

	Linux man‐pages (unreleased)    (date)                         bcmp(3)

Cheers,
Alex

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

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

  reply	other threads:[~2023-11-01 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01 14:02 Issue in man page bcmp.3 Helge Kreutzmann
2023-11-01 16:24 ` Alejandro Colomar [this message]
2023-11-02 10:06   ` Stefan Puiu
2023-11-02 11:27     ` Alejandro Colomar
2023-11-02 11:32     ` Alejandro Colomar
  -- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann

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=ZUJ7zYWY2yspm3Ec@debian \
    --to=alx@kernel.org \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@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