From: Alejandro Colomar <alx.manpages@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: [C2x] Disallow function attributes after function identifier
Date: Fri, 10 Jun 2022 23:35:25 +0200 [thread overview]
Message-ID: <a457d1ee-d889-9d31-aaa2-3e85006cfad4@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2206102102390.209945@digraph.polyomino.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 886 bytes --]
Hi Joseph,
On 6/10/22 23:09, Joseph Myers wrote:
>> P.S.: The latest draft that I know of is N2731. I guess there are newer ones.
>> Could you please name the latest one?
>
> It's N2912 (June 8 version - the version originally published on June 7
> had various problems; there are still some issues, especially in Annex H,
> that have been fixed since the June 8 version, but fewer than in the June
> 7 version). As far as I know, N2912 incorporates all changes accepted so
> far for C23; the deadline for final versions of ongoing proposals to be
> considered at the July meeting is 17 June (and the July meeting is the
> deadline for new features to get in before the CD ballot).
>
Thanks! Will update my links :)
Cheers,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; http://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-06-10 21:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 20:40 Alejandro Colomar
2022-06-10 21:09 ` Joseph Myers
2022-06-10 21:35 ` Alejandro Colomar [this message]
2022-06-10 21:16 ` Jakub Jelinek
2022-06-10 21:31 ` Alejandro Colomar
2022-06-10 22:47 ` Jonathan Wakely
2022-06-11 9:03 ` Alejandro Colomar
2022-06-11 12:08 ` Gabriel Ravier
2022-06-11 20:20 ` Alejandro Colomar
2022-06-13 15:54 ` Jonathan Wakely
2022-06-11 12:53 ` Jonathan Wakely
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=a457d1ee-d889-9d31-aaa2-3e85006cfad4@gmail.com \
--to=alx.manpages@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.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).