Re: the Linux man-pages as an educational tool

Arsen Arsenović <[email protected]> Mon, 03 Aug 2026 13:00:19 +0200
Newsgroups gmane.comp.lib.gnulib.bugs,gmane.linux.man,gmane.comp.lib.glibc.alpha
Message-ID <[email protected]>
--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

"G. Branden Robinson" <[email protected]> writes:

>> The name of a header providing some function is thus inconsequential.
>
> Then why not have one official big header file for the whole standard?
>
> #include <stdlibc.h>
>
> When you answer that to your own satisfaction, I suspect you'll have
> little trouble following Alex's argument.
>
> ...which doesn't mean you'll agree with it.

The only reason I can imagine for not having One Big Header in 2026 is
the same reason why I wouldn't make the change Alex is proposing:
because someone already chose to create many headers and changing it
would mean shuffling lots of code around for no gain.

I imagine that, at some point, the amount of time that it would take to
read and parse such a header would've been a problem also.  Perhaps that
inspired the fragmentation.  Perhaps not.

I do not know, I didn't do the historiography.

I do know that splitting an extremely widely used header (291,660
matches on Debian codesearch) to replace it with one used far less
widely (11,459 matches on that same codesearch, some of which mention
portability concerns as the motivation for including memory.h, and I
suspect most of which also have an include of string.h in the same file,
but I did not verify this) only means that people include both, perhaps
conditionally, while seeing no changes outside of the preamble of their
source files.
=2D-=20
Arsen Arsenovi=C4=87

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

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

iQECBAEWCgCqFiEE/uKz0RP8AKMWLWBhUsKUMB6ixJMFAmpwdMMbFIAAAAAABAAO
bWFudTIsMi41KzEuMTIsMiwyXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25z
Lm9wZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGRUUyQjNEMTEzRkMwMEEzMTYyRDYw
NjE1MkMyOTQzMDFFQTJDNDkzEBxhcnNlbkBhYXJzZW4ubWUACgkQUsKUMB6ixJNZ
pQEAp/uFW2lA3o+LdFIYsGomKtxzsWcECzecs1KGPvOB9dkA/3N/Jo/nO+RiNy43
104fvvKQ0NCqH2V40F7cd8TMXL8K
=DQnl
-----END PGP SIGNATURE-----
--=-=-=--