From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-106473-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 124110 invoked by alias); 30 Oct 2019 17:26:55 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 122283 invoked by uid 89); 30 Oct 2019 17:26:54 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-2.8 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.1 spammy=H*f:sk:_8FBMhw, H*i:sk:_8FBMhw
X-HELO: mx1.suse.de
From: Andreas Schwab <schwab@suse.de>
To: Zack Weinberg <zackw@panix.com>
Cc: Florian Weimer <fweimer@redhat.com>,  GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [review] manual: Clarify strnlen, wcsnlen, strndup null termination behavior
References: <gerrit.1572431114000.Ia3e68bc2d4d7e967df141702fb2f600cbd4a6432@gnutoolchain-gerrit.osci.io>
	<mvmd0eeh5sb.fsf@suse.de> <87a79i33kt.fsf@oldenburg2.str.redhat.com>
	<mvm8sp2h51r.fsf@suse.de> <875zk6337v.fsf@oldenburg2.str.redhat.com>
	<mvm4kzqh4kd.fsf@suse.de>
	<CAKCAbMihS7iJe29vZBRcoGVrQ1OXcgCMjLwD+m3_kEOyOYnjrA@mail.gmail.com>
	<mvmeeyufbmw.fsf@suse.de>
	<CAKCAbMgYPSGZOCDX_qqmt8_DxxRWuqiEZg9OJJEEirOHSv-8+g@mail.gmail.com>
	<mvma79ifaef.fsf@suse.de>
	<CAKCAbMhopXXKgBVpkV=_8FBMhwcY9NtPTdsYASQ4Xdn128u4qw@mail.gmail.com>
X-Yow: HELLO, little boys!   Gimme a MINT TULIP!!  Let's do the BOSSA NOVA!!
Date: Wed, 30 Oct 2019 17:26:00 -0000
In-Reply-To: <CAKCAbMhopXXKgBVpkV=_8FBMhwcY9NtPTdsYASQ4Xdn128u4qw@mail.gmail.com>
	(Zack Weinberg's message of "Wed, 30 Oct 2019 12:58:41 -0400")
Message-ID: <877e4muoti.fsf@igel.home>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-SW-Source: 2019-10/txt/msg00936.txt.bz2

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.

Andreas.

-- 
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."