Re: [PATCH v2] man/man3/mem*(): SYNOPSIS: Document non-standard mem*() functions as provided by <memory.h>

--67qw2vvqfgxjjh2t
Content-Type: text/plain; protected-headers=v1; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
From: Alejandro Colomar <[email protected]>
To: Collin Funk <[email protected]>
Cc: Bruno Haible <[email protected]>, [email protected], 
	Sam James <[email protected]>, "G. Branden Robinson" <[email protected]>, 
	Joseph Myers <[email protected]>, Keith Bostic <[email protected]>, 
	Mark Harris <[email protected]>, Nevin Liber <[email protected]>, 
	JeanHeyd Meneide <[email protected]>, Christopher Bazley <[email protected]>, 
	Serge Hallyn <[email protected]>, Iker Pedrosa <[email protected]>, Evgeny Grin <[email protected]>, 
	Kees Cook <[email protected]>, [email protected], [email protected]
Subject: Re: [PATCH v2] man/man3/mem*(): SYNOPSIS: Document non-standard
 mem*() functions as provided by <memory.h>
Message-ID: <am6Bzu98mVTgO1Qv@devuan>
References: <[email protected]>
 <3556566.BddDVKsqQX@cagnes>
 <am50AM0bdufHa9W3@devuan>
 <15288158.RDIVbhacDa@cagnes>
 <am56ZBzNM5J07AUa@devuan>
 <[email protected]>
MIME-Version: 1.0
In-Reply-To: <[email protected]>

Hi Collin,

> Date: 2026-08-01 16:26:18-0700
> From: Collin Funk <[email protected]>
>
> Alejandro Colomar <[email protected]> writes:
>=20
> >> Still, for the next 10 years, C programmers would debate whether they =
should
> >> #include <string.h> or #include <memory.h>. Different C programmers in=
 the
> >> same team will have different personal opinions. Thus, programmer team=
 leads
> >> will have to establish coding styles/guidelines which say which header=
 to
> >> include in this case.
> >
> > I find that an acceptable result.
>=20
> But you aren't the only one who uses or references the man pages. From
> this thread, many people are not happy with the change.
>=20
> > #include's aren't that important. When reading code, the section of
> > #include's is unimportant as long as it works.
>=20
> In this case they won't "always work", hence your request that gnulib
> and illumos make changes to accommodate your preferences.

I've now carefully documented that gnulib and Illumos don't provide this
header.  Thanks!


Have a lovely night!
Alex

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

--67qw2vvqfgxjjh2t
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEES7Jt9u9GbmlWADAi64mZXMKQwqkFAmpugoQACgkQ64mZXMKQ
wqkMfQ//VrELPo5bM/U3mp+uYxFfyhpw0zhZX4rjnetaBw7LOegaSCXIacodoYoB
rd6jU4pat10Sm9dfR21qluEmXKSM7z27bFLNkjOwd0f3cFaidgEL5Kle8Q3YobsF
5Hrsc6f8SD3qmBKl7VopQkHoG0TB0z+EZmureAV11EW7uQwiycFeyTP3ODRTfG5o
cP5uZL2NtqcuedRX7lcHPBbaJr5HAWUUkVJlqtOXtZ3Uc3jV4+tpDBfIhdvwcLmG
hZaqk04bZe84gjXeg0a/dc6CtOFH2Zvg5b8MeZl9T5TyyDTQ/Fnvv/Nukh8JvArS
T26U0i5tBgys/8sgaPPpPkY6bmyGQJx8leQdNCroQjQzoiVGtS8jwKLYOxvuQ/An
WuxqPSw05rx2TmE0pQNkoGi5GLlVMngMQJEoHZsW1AeELmIc96AdSGPcJ+AfshCg
YETZ/GsZO/m82UWXP2BvAekwOFzT/BhKXDCUZqHsE3Kf540yTbRkZ8yTzyFMUMBY
+vG04GBVMgvKp1iwD8OswEsvd41ikTr8W7P7G64AjBc91Iy5vcBs+DrpZS6m0f2h
lCp7EH/qNMzdyeQp4j3u+4BFBNzR/78Pa/7oknsRafmkNJaLNXHyAUM94GoZlOVc
iQutdD4JlsnnsbEV5tAnkPwSJH7gHCNG3lWRI85irE7hVuvZVE0=
=jvTS
-----END PGP SIGNATURE-----

--67qw2vvqfgxjjh2t--