From: Jeffrey Walton <noloader@gmail.com>
To: musl@lists.openwall.com
Cc: Stefan Puiu <stefan.puiu@gmail.com>,
Guillem Jover <guillem@hadrons.org>,
Andrew Clayton <andrew@digital-domain.net>,
linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Alejandro Colomar <alx@kernel.org>,
Brian Inglis <Brian.Inglis@systematicsw.ab.ca>,
Rich Felker <dalias@libc.org>
Subject: Re: [musl] Re: [PATCH] memmem.3: Added list of known systems where this is available
Date: Wed, 23 Nov 2022 09:55:15 -0500 [thread overview]
Message-ID: <CAH8yC8=TWk=umVZ-mt29wzQe7xGMXYQ7cZ0rgCG88Dn3x7QLNA@mail.gmail.com> (raw)
In-Reply-To: <50485f46-99d0-69ee-0882-7e403334080c@gmail.com>
On Wed, Nov 23, 2022 at 9:29 AM Alejandro Colomar
<alx.manpages@gmail.com> wrote:
> ...
> >> In any case I also find it useful to have this kind of portability
> >> information when deciding what to use in code.
>
> And I must admit it's also useful to me (this all started because Andrew and I
> had to use memmem(3) at a project where macOS compatibility is relevant --not
> critical, but relevant--).
If you are a die-hard free software person using GNU gear, then Gnulib
provides memmem. There's no need to worry about availability or
portability courtesy of Gnulib. See
https://www.gnu.org/software/gnulib/manual/html_node/memmem.html .
Jeff
next prev parent reply other threads:[~2022-11-23 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221110001318.10696-1-andrew@digital-domain.net>
[not found] ` <853fa349-8e78-8ce8-f76f-79b4b9353913@gmail.com>
[not found] ` <Y31XOPOsB932l0cd@thunder.hadrons.org>
[not found] ` <CACKs7VAQsxDc2XrsAYSEbA9eqRnLHuXykVmNTit+tCFMyGLCwA@mail.gmail.com>
2022-11-23 13:16 ` Alejandro Colomar
2022-11-23 14:55 ` Jeffrey Walton [this message]
2022-11-23 15:11 ` Alejandro Colomar
2022-11-23 15:33 ` [musl] " Shiz
2022-11-30 19:39 ` enh
2022-12-09 20:25 ` Alejandro Colomar
2022-11-24 18:57 ` [musl] " Stefan Puiu
2022-12-11 16:30 ` 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='CAH8yC8=TWk=umVZ-mt29wzQe7xGMXYQ7cZ0rgCG88Dn3x7QLNA@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=Brian.Inglis@systematicsw.ab.ca \
--cc=alx@kernel.org \
--cc=andrew@digital-domain.net \
--cc=dalias@libc.org \
--cc=guillem@hadrons.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=musl@lists.openwall.com \
--cc=stefan.puiu@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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).