From: Zack Weinberg <zackw@panix.com>
To: Andreas Schwab <schwab@suse.de>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [review] manual: Clarify strnlen, wcsnlen, strndup null termination behavior
Date: Wed, 30 Oct 2019 18:12:00 -0000 [thread overview]
Message-ID: <CAKCAbMjW3YZa3+=exm6CvCE2s98qgf04naegYASc_-BkyGgs4A@mail.gmail.com> (raw)
In-Reply-To: <877e4muoti.fsf@igel.home>
On Wed, Oct 30, 2019 at 1:26 PM Andreas Schwab <schwab@suse.de> wrote:
> On Okt 30 2019, Zack Weinberg wrote:
>
> > Yes, that could be a defect in the specification of strncpy (I can
> > argue either way about what the parenthetical "(bytes that follow a
> > NUL character are not copied)" means). How does text's presence or
> > absence in the specification of strncpy change anything about the
> > requirements on strnlen?
>
> Because it shows how flawed your argument is.
Are you seriously saying that I have to read the specification of
strncpy to understand the specification of strnlen? That's not how I
was taught to read standards.
zw
next prev parent reply other threads:[~2019-10-30 18:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-30 10:25 Florian Weimer (Code Review)
2019-10-30 10:44 ` Andreas Schwab
2019-10-30 10:55 ` Florian Weimer
2019-10-30 11:00 ` Andreas Schwab
2019-10-30 11:03 ` Florian Weimer
2019-10-30 11:10 ` Andreas Schwab
2019-10-30 12:01 ` Zack Weinberg
2019-10-30 16:20 ` Andreas Schwab
2019-10-30 16:31 ` Zack Weinberg
2019-10-30 16:47 ` Andreas Schwab
2019-10-30 16:58 ` Zack Weinberg
2019-10-30 17:26 ` Andreas Schwab
2019-10-30 18:12 ` Zack Weinberg [this message]
2019-10-30 18:36 ` Florian Weimer
2019-10-30 17:24 ` Joseph Myers
2019-11-28 9:43 ` Florian Weimer
2019-11-28 15:56 ` Carlos O'Donell
2019-11-28 15:58 ` Carlos O'Donell
2019-11-28 18:23 ` Rich Felker
2019-11-28 18:38 ` Szabolcs Nagy
2019-11-29 18:20 ` Martin Sebor
2019-11-27 19:08 ` Carlos O'Donell (Code Review)
2019-11-27 19:14 ` Florian Weimer (Code Review)
2019-11-27 22:11 ` Carlos O'Donell (Code Review)
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='CAKCAbMjW3YZa3+=exm6CvCE2s98qgf04naegYASc_-BkyGgs4A@mail.gmail.com' \
--to=zackw@panix.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).