public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102397] Documentation of attribute syntax does not discuss C++11 / C23 attribute syntax Date: Fri, 19 Jan 2024 02:52:55 +0000 [thread overview] Message-ID: <bug-102397-4-hgYAsuq3j9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102397-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102397 sandra at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sandra at gcc dot gnu.org --- Comment #1 from sandra at gcc dot gnu.org --- I committed a patch a few months ago to say that the new C++/C standard attribute syntax is supported with a gnu:: prefix, so at least the originally-reported problem has already been fixed. However, all the examples still use the old syntax. Given that there is an awful lot of legacy code using the old syntax already out there, examples are useful in helping people grok what it means, but at some point we probably want to encourage people to use the new syntax in new code for all the usual reasons why it's better to do things in a standard way, and use it also as the primary form for documentation. OTOH, I don't think we're quite there yet. Presently the manual describes C23 support as "experimental and incomplete" and says the default C language dialect is -std=gnu17. My sense is that it's not appropriate to tell users to make the switch until GCC's default dialect is advanced to something based on C23. So I'm going to leave this issue open for now instead of closing it as fixed, as a reminder that there is still more work to be done here a little farther down the road.
prev parent reply other threads:[~2024-01-19 2:52 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-09-18 11:06 [Bug c++/102397] New: " dangelog at gmail dot com 2021-09-18 15:03 ` [Bug c++/102397] " redi at gcc dot gnu.org 2024-01-19 2:52 ` sandra at gcc dot gnu.org [this message]
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=bug-102397-4-hgYAsuq3j9@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).