From: Joseph Myers <joseph@codesourcery.com>
To: Alejandro Colomar <colomar.6.4.3@gmail.com>
Cc: fweimer@redhat.com, gcc@gcc.gnu.org, ville.voutilainen@gmail.com,
linux-man@vger.kernel.org, rusty@rustcorp.com.au,
linux-kernel@vger.kernel.org, libstdc++@gcc.gnu.org,
libc-coord@lists.openwall.com, libc-alpha@sourceware.org,
jwakely@redhat.com, enh@google.com
Subject: Re: Ping(3): [PATCH v4] <sys/param.h>: Add nitems()
Date: Tue, 17 Nov 2020 23:11:00 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2011172308010.28480@digraph.polyomino.org.uk> (raw)
In-Reply-To: <8fb9c722-4190-6115-1d60-d94f8db7f749@gmail.com>
On Tue, 17 Nov 2020, Alejandro Colomar via Libc-alpha wrote:
> Nice!
> Please update me on any feedback you receive.
Apparently the author is planning new versions of those papers so WG14
discussion is waiting for those.
> So glibc will basically hold this patch
> at least until the WG answers to that, right?
I think that whether C2x gets an array-size feature of some kind is
relevant to whether such a feature goes in glibc and what it looks like in
glibc, but the fact that it will be considered in WG14 doesn't rule out
glibc considering such a feature without waiting for WG14.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2020-11-17 23:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 19:12 [PATCH v4] <sys/param.h>: Add nitems() Alejandro Colomar via Libc-alpha
2020-10-11 16:43 ` Ping: " Alejandro Colomar via Libc-alpha
2020-10-27 11:38 ` Ping(2): " Alejandro Colomar via Libc-alpha
2020-11-17 22:23 ` Ping(3): " Alejandro Colomar via Libc-alpha
2020-11-17 22:44 ` Joseph Myers
2020-11-17 22:59 ` Alejandro Colomar via Libc-alpha
2020-11-17 23:11 ` Joseph Myers [this message]
2020-11-18 11:26 ` Alejandro Colomar via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.22.394.2011172308010.28480@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=colomar.6.4.3@gmail.com \
--cc=enh@google.com \
--cc=fweimer@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-coord@lists.openwall.com \
--cc=libstdc++@gcc.gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=ville.voutilainen@gmail.com \
/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).