public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@owlfolio.org>
To: Eric Blake <eblake@redhat.com>
Cc: GNU libc development <libc-alpha@sourceware.org>,
	austin-group-l@opengroup.org
Subject: Re: [PATCH] sockaddr.3type: Document that sockaddr_storage is the API to be used
Date: Fri, 14 Apr 2023 12:08:26 -0400	[thread overview]
Message-ID: <bba87d12-77ce-386c-ba85-e20a7a1e4b22@owlfolio.org> (raw)
In-Reply-To: <cgetryf5sc3cn6p4ssb47pa2nivjw5vughv6pmpc6qykt3y3bd@teqf7o5uapqm>

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

  reply	other threads:[~2023-04-14 16:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 17:13 Alejandro Colomar
2023-03-30 19:11 ` Eric Blake
2023-04-05  0:42   ` Alejandro Colomar
2023-04-06 16:24     ` Eric Blake
2023-04-06 16:31       ` Alejandro Colomar
2023-04-06 18:05         ` Zack Weinberg
2023-04-06 19:37           ` Eric Blake
2023-04-14 16:08             ` Zack Weinberg [this message]
2023-04-21 14:58               ` Alejandro Colomar
2023-04-21 15:00                 ` Alejandro Colomar
2023-04-21 15:27                   ` Eric Blake
2023-04-21 20:27                     ` [PATCH v3] sockaddr.3type: POSIX Issue 8 will solve strict-aliasing issues with these types Alejandro Colomar
2023-04-21 20:35                       ` Eric Blake

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=bba87d12-77ce-386c-ba85-e20a7a1e4b22@owlfolio.org \
    --to=zack@owlfolio.org \
    --cc=austin-group-l@opengroup.org \
    --cc=eblake@redhat.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).