From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx.manpages@gmail.com>,
'GNU C Library' <libc-alpha@sourceware.org>
Cc: "Wilco Dijkstra" <Wilco.Dijkstra@arm.com>,
"Cristian Rodríguez" <crrodriguez@opensuse.org>,
"Damian McGuckin" <damianm@esi.com.au>,
Alexis <flexibeast@gmail.com>
Subject: Re: [manual]: rawmemchr(3) and UB
Date: Thu, 5 Jan 2023 06:21:18 -0600 [thread overview]
Message-ID: <20230105122118.fk62iqxvgwlk7jfm@illithid> (raw)
In-Reply-To: <20230104201923.nd6tovbtmsghi27d@illithid>
[-- Attachment #1: Type: text/plain, Size: 1541 bytes --]
My punishment for smarting off to the libc-alpha list is that I have to
admit an error.
At 2023-01-04T14:19:23-0600, G. Branden Robinson wrote:
> The b in bzero() [is] for Bad BSD Bogosity. [...] Like index() and
> rindex() it is duplicative.
While BSD did hang on to {r,}index for a long time, I was digging around
in libc history while amiably reading C. D. Perez's "A Guide to the C
Library for Unix Users" (ca. 1981)[1] and found that I have to correct
myself...and possibly the Linux man-pages documents for them.
They date all the way back to V7 Unix and antedate str{r,}chr().
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/index.c
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/rindex.c
Mea culpa.
Alex, in your current mission you might find entertainment of the
cerebral hemorrhage-causing variety in some of the following files.
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/strcat.c
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/strcmp.c
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/strcpy.c
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/strlen.c
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/strncat.c
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/strncmp.c
https://minnie.tuhs.org/cgi-bin/utree.pl?file=V7/usr/src/libc/gen/strncpy.c
Regards,
Branden
[1] https://www.tuhs.org/Archive/Documentation/Manuals/Unix_4.0/Volume_1/D.1.2_A_Guide_to_the_C_Library.pdf
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-05 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 19:41 Wilco Dijkstra
2023-01-04 20:05 ` Alejandro Colomar
2023-01-04 20:19 ` G. Branden Robinson
2023-01-04 20:34 ` Alejandro Colomar
2023-01-05 12:21 ` G. Branden Robinson [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-30 13:13 Wilco Dijkstra
2022-12-30 14:16 ` Alejandro Colomar
2022-12-29 19:19 Alejandro Colomar
2022-12-29 19:27 ` Alejandro Colomar
2022-12-29 19:45 ` Cristian Rodríguez
2022-12-29 19:50 ` Alejandro Colomar
2022-12-30 10:31 ` Alejandro Colomar
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=20230105122118.fk62iqxvgwlk7jfm@illithid \
--to=g.branden.robinson@gmail.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=alx.manpages@gmail.com \
--cc=crrodriguez@opensuse.org \
--cc=damianm@esi.com.au \
--cc=flexibeast@gmail.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).