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

Alejandro Colomar <[email protected]> Sun, 2 Aug 2026 01:34:28 +0200

Newsgroups	gmane.comp.lib.gnulib.bugs,gmane.linux.man,gmane.comp.lib.glibc.alpha
Message-ID	<am6Bzu98mVTgO1Qv@devuan>

Hi Collin,

> Date: 2026-08-01 16:26:18-0700
> From: Collin Funk <[email protected]>
>
> Alejandro Colomar <[email protected]> writes:
> 
> >> 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.
> 
> 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.
> 
> > #include's aren't that important. When reading code, the section of
> > #include's is unimportant as long as it works.
> 
> 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

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

signature.asc (application/pgp-signature, 833 B)