From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by sourceware.org (Postfix) with ESMTPS id 285DE3858D20 for ; Fri, 14 Apr 2023 16:08:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 285DE3858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=owlfolio.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=owlfolio.org Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 105B15C014E; Fri, 14 Apr 2023 12:08:27 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Fri, 14 Apr 2023 12:08:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=owlfolio.org; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1681488507; x=1681574907; bh=3RBadfHuXi8PITrOLAqoo5OGMbtH7LgtFgV KH5YLLk0=; b=b1fDFfrUjZUeADWnS2jlNF/Q8puF+s63JKwaZ5DW8BY7TdDkpKm d63rXzmsKO3dKCQZLdvxaCSao5brnec5t6gFGhdiVVaqWehopDr0sLTbuZQFjBGA +VTY++v3lyT5BKxLcbo9WEK4DugqNfDVHfm2myX+HjlNvA6IaIJRrLGjrIzhumSB c8emNXzYpUqXH8RzpBD6yLPg9OD+uJIVCkZ9mPKdm0VG5mc4G87bPcH0AUMjUIoR vG/mZ2Q76qfXHk29ZCVjAQ+gRFdEWZz8bxuJNJ/qOxJSs6FkDl5GzJz3Me7qC6de 1HiDnKfcaaAoy7d4yu6PpO70rpbiEgGHsCA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1681488507; x=1681574907; bh=3RBadfHuXi8PITrOLAqoo5OGMbtH7LgtFgV KH5YLLk0=; b=Rtb3ZIVuaImdFHrFnDVDImKuOuAx+LkFtvRuTzYcKNE5QUtmqva bmJOt2tHCSetTuc/LXWSjg2SJ/tCD9yoshoolUnV+T+74Oe9vw8Tg941T1+WPz8u 5cN6Qj+rldW5TH25oXpK/6R8jOIoa1IWHp9XdTncbTIet+lsFJv4uolPfPKgEx2B dy79bGPTWS0+CE3Va/G9HQP+dB9Yi7xK/YUwU99eKWaXo/GwPPNUViOpKMIRZFve Z39+0PTmX6hiVufLBAhlBek7XLGAdOUqtz2lvd/yrihQjOXtIGWIjUN0v4lbIV0t FiachdClI2Kzp8oexnjnROU5m3Kg56SlcIQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrvdeltddgleejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpegkrggt khcuhggvihhnsggvrhhguceoiigrtghksehofihlfhholhhiohdrohhrgheqnecuggftrf grthhtvghrnhepudefkeelteekheffuddvhfefkeeileeiudduleekudduffeuffevteef ffejgefhnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epiigrtghksehofihlfhholhhiohdrohhrgh X-ME-Proxy: Feedback-ID: i876146a2:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 14 Apr 2023 12:08:26 -0400 (EDT) Message-ID: Date: Fri, 14 Apr 2023 12:08:26 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCH] sockaddr.3type: Document that sockaddr_storage is the API to be used Content-Language: en-US To: Eric Blake Cc: GNU libc development , austin-group-l@opengroup.org References: <20230330171310.12330-1-alx@kernel.org> <9b528ba9-e1c6-1c03-8ec7-177c4dc66e19@gmail.com> <7396024c-62d4-a19c-b7bc-e24a9d4bcb31@gmail.com> <6fdadcff-95a2-44fe-9453-d0200822e01e@app.fastmail.com> From: Zack Weinberg In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-4.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,JMQ_SPF_NEUTRAL,NICE_REPLY_A,RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 2023-04-06 3:37 PM, Eric Blake wrote: > Since Issue 7 is tied to C99, and Issue 8 will be tied to C17, both of > which use the same section number despite being a different edition of > the C standard, being that specific may work. Or, we might try > something focusing more on wording instead of document location, as > in: > > Additionally, the structures shall be defined in such a way that the > compiler treats an access to the stored value of the sa_family_t > member of any of these structures, via an lvalue expression whose type > involves any other one of these structures, as permissible even if the > types involved would not otherwise be deemed compatible with the > effective type of the object ultimately being accessed. I quite like this way of putting it. It subsumes both what I wrote and the related potential headache with deciding whether the sa_family_t field is considered an object or just a range of bytes within a larger object. zw