Re: [PATCH 1/2] man/man3/{mem,strn}*(): SYNOPSIS, STANDARDS: Document these as provided by <memory.h>
Alejandro Colomar <[email protected]> Sat, 1 Aug 2026 02:12:49 +0200
| Newsgroups | org.kernel.vger.linux-man |
|---|---|
| Message-ID | <am04r4by8xhTKNqT@devuan> |
--jlaawasc4plsgybm Content-Type: text/plain; protected-headers=v1; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable From: Alejandro Colomar <[email protected]> To: Sam James <[email protected]> Cc: Joseph Myers <[email protected]>, [email protected], Keith Bostic <[email protected]>, Mark Harris <[email protected]>, Nevin Liber <[email protected]>, JeanHeyd Meneide <[email protected]>, Christopher Bazley <[email protected]>, "Serge E. Hallyn" <[email protected]>, Iker Pedrosa <[email protected]>, "Evgeny Grin (Karlson2k)" <[email protected]>, Kees Cook <[email protected]>, [email protected], [email protected] Subject: Re: [PATCH 1/2] man/man3/{mem,strn}*(): SYNOPSIS, STANDARDS: Document these as provided by <memory.h> Message-ID: <am04r4by8xhTKNqT@devuan> References: <[email protected]> <784288e704183a4297aeaa3d13af8edab18bc1ea.1785532392.git.alx@kernel.org> <[email protected]> <am0TUn55P7uNtTTh@devuan> <[email protected]> <am0dFT38yXK_ch_o@devuan> MIME-Version: 1.0 In-Reply-To: <am0dFT38yXK_ch_o@devuan> Hi Sam, > Date: 2026-08-01 00:19:03+0200 > From: Alejandro Colomar <[email protected]> > > > Date: 2026-07-31 22:54:27+0100 > > From: Sam James <[email protected]> > > [...] > > People want it to reflect what the standard says. >=20 > And it still does. Hmmm, this has implications. The functions that are non-standard, can be changed as of now, because, well, there's no standard saying otherwise. Maybe that's a good move. A commit now changing the following functions the be documented as provided by <memory.h>, without any mentions to <string.h>, simply because there's no standard mandating otherwise: - strndupa(3) - mempcpy(3) - memrchr(3) - memmem(3) - memfrob(3) Which is a nice introduction for this header file. Then we can leave discussion of the standard functions for later. If what the standard says is the problem, let's focus on what it doesn't say. Cheers, Alex --=20 <https://www.alejandro-colomar.es> --jlaawasc4plsgybm Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEES7Jt9u9GbmlWADAi64mZXMKQwqkFAmptOgEACgkQ64mZXMKQ wqnmOxAApec0DbaIVOm9AwskYWWUbsv6eMlTwOsWA/E6U0bPZ1XL+Y7PwiqdTXAX OnY9VCGrDJpNn0krZ4y7qSURtTRdf0Bz8mMKIjv4JR/2v8fUhsKsuMENj49QMpMr JLu4g+XCIu0qcDmdfJfVHuzQaIg1ekei748Ge3N5ychFPiZS8shtMmksfpK9GXib CMAb+hPTLJrkn6Q3xw+w744LxQQgYsy0IBDx16aEHLGDJF1+4BHM4BASsHyJW+3G +ORvyuNcKE28S9eZ/vOeM/hW7snyhaiH2IsftGwA/17xHlyd5zMHRnuBcSL6St3e 3syXMm3/Cf36y31Mo6Jg5V94bGC6GRlxx6hmd5BF4V1eu2esjccG+GJgOmwWz8BL TZNpu5h2B4qEqVPqShlXSOHGsIZY07hOquwvaWJbVQAjQ3m5SeQInbgTrXV7cd5A /MMRt9c7/Z64CKvJwyebh7hXdo/Rk2lp45QBaN2f8jNPJt//Y7wta/FtdSIyngLm 9Tv0cX6bsEtptxT1FfytB33R2wVG0VZp6GJiWO7tL4w9KKJD2zf/XhnlIz2mQETD NUnoi2PY1UOld4uQUCXKn/ivyNMHW5/AqjiZqL5qXuyYl425DR0Atgp1kKqBdnLQ at5Hzyk/Ihj736UMFB6TQPKHrf7hjvdNybvtSvElVvY026gc6Aw= =KmvV -----END PGP SIGNATURE----- --jlaawasc4plsgybm--