From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: "Ingo Schwarze" <schwarze@usta.de>,
"Colin Watson" <cjwatson@debian.org>,
linux-man@vger.kernel.org,
"Mario Blättermann" <mario.blaettermann@gmail.com>,
"Marcos Fouces" <marcos@debian.org>,
"Dr. Tobias Quathamer" <toddy@debian.org>
Subject: Re: str{n,}casecmp(3) and <strings.h> (was: Conflicting alias for some man pages)
Date: Fri, 9 Dec 2022 21:44:48 +0100 [thread overview]
Message-ID: <4c4fbb77-85cc-52d8-55ee-c6ecab64cf55@gmail.com> (raw)
In-Reply-To: <266ffba3-4831-f740-5354-3f00f9cc8dc6@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1877 bytes --]
On 12/9/22 21:43, Alejandro Colomar wrote:
> Hi Branden,
>
> On 12/9/22 21:37, G. Branden Robinson wrote:
>> On another topic, I will stump again for the idea of having separate
>> strings.h(3) and string.h(3) pages instead of the single string(3) page
>> we see here. :)
>>
>> On yet another topic, the history of strcasecmp() seems incomplete, and
>> fails to motivate why "strings.h" (note the additional "s") even exists.
>>
>> NOTES
>> The strcasecmp() and strncasecmp() functions first appeared in
>> 4.4BSD, where they were declared in <string.h>. Thus, for rea‐
>> sons of historical compatibility, the glibc <string.h> header
>> file also declares these functions, if the _DEFAULT_SOURCE (or,
>> in glibc 2.19 and earlier, _BSD_SOURCE) feature test macro is
>> defined.
>>
>> They're older than the above indicates. strings.h as a _file_ is at
>> least as old as 4.2BSD (1983),[1] a decade before 4.4BSD.
>> str{n,}casecmp() came in with 4.3BSD-Tahoe (June 1988).[2] In
>> 4.3BSD-Reno (June 1989), strings.h became a stump that loaded
>> <string.h>,[3] where it remained and after which the man-pages history
>> above picks up the story.
>>
>> Want a patch?
>
> Sure, patches are always welcome! =)
>
> Maybe that info would be better in string(3).
Oh, I missed your suggestion about having two separate pages for string.h and
strings.h. Please go ahead. I like it.
>
>>
>> [1] https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.2BSD/usr/include/strings.h
>> [2]
>> https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD-Tahoe/usr/include/strings.h
>> [3] https://minnie.tuhs.org/cgi-bin/utree.pl?file=4.3BSD-Reno/include/strings.h
>
> Cheers,
>
> Alex
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-09 20:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 14:01 Conflicting alias for some man pages Helge Kreutzmann
2022-12-03 16:36 ` Alejandro Colomar
2022-12-03 16:51 ` Helge Kreutzmann
2022-12-03 17:03 ` Alejandro Colomar
2022-12-03 17:21 ` Helge Kreutzmann
2022-12-09 18:53 ` Alejandro Colomar
2022-12-09 20:37 ` G. Branden Robinson
2022-12-09 20:43 ` str{n,}casecmp(3) and <strings.h> (was: Conflicting alias for some man pages) Alejandro Colomar
2022-12-09 20:44 ` Alejandro Colomar [this message]
2022-12-09 20:48 ` man-db bugs? " Alejandro Colomar
2022-12-10 7:56 ` Helge Kreutzmann
2022-12-10 7:53 ` Conflicting alias for some man pages Helge Kreutzmann
2022-12-11 13:52 ` Alejandro Colomar
2022-12-11 14:20 ` Helge Kreutzmann
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=4c4fbb77-85cc-52d8-55ee-c6ecab64cf55@gmail.com \
--to=alx.manpages@gmail.com \
--cc=cjwatson@debian.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=marcos@debian.org \
--cc=mario.blaettermann@gmail.com \
--cc=schwarze@usta.de \
--cc=toddy@debian.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox