public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>,
	linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>
Subject: Re: [PATCH] index.3, memchr.3, strchr.3, string.3, strpbrk.3, strsep.3, strspn.3, strstr.3, strtok.3: Deprecate index(3) and rindex(3)
Date: Thu, 5 Jan 2023 19:47:48 +0100	[thread overview]
Message-ID: <72facfb2-c219-1558-181c-8ea06b2d1283@gmail.com> (raw)
In-Reply-To: <20230105184446.10141-1-alx@kernel.org>


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

index(3)                   Library Functions Manual                   index(3)

NAME
        index, rindex - locate character in string

LIBRARY
        Standard C library (libc, -lc)

SYNOPSIS
        #include <strings.h>

        [[deprecated]] char *index(const char *s, int c);
        [[deprecated]] char *rindex(const char *s, int c);

DESCRIPTION
        index() is identical to strchr(3).

        rindex() is identical to strrchr(3).

        Use strchr(3) and strrchr(3) instead of these functions.

STANDARDS
        4.3BSD;  marked  as  LEGACY  in POSIX.1‐2001.  POSIX.1‐2008 removes the
        specifications of index() and rindex(), recommending strchr(3) and str‐
        rchr(3) instead.

SEE ALSO
        strchr(3), strrchr(3)

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

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

      reply	other threads:[~2023-01-05 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 18:44 [PATCH] index.3, memchr.3, strchr.3, string.3, strpbrk.3, strsep.3, strspn.3, strstr.3, strtok.3: Deprecate index(3) and rindex(3) Alejandro Colomar
2023-01-05 18:47 ` Alejandro Colomar [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=72facfb2-c219-1558-181c-8ea06b2d1283@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    /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