From: Joseph Myers <joseph@codesourcery.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Patches <GCC-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] C-family : Add attribute 'unavailable'.
Date: Mon, 4 Jan 2021 20:19:47 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2101042017450.1093969@digraph.polyomino.org.uk> (raw)
In-Reply-To: <64C89FBE-804D-43DB-B86E-EC5C72D409B5@sandoe.co.uk>
On Mon, 21 Dec 2020, Iain Sandoe wrote:
> Hi Joseph,
>
> Nathan has approved this from the C++ perspective (and Martin said that his
> comments were "not necessarily to object to the idea behind the attribute but
> to draw attention to the fact that it's not suitable for standard APIs.”)
>
> So, I wonder, do you have more comments on the revised patch, or is this
> now OK for master?
If <https://gcc.gnu.org/pipermail/gcc-patches/2020-November/558630.html>
is the current version, one of the three copies of the attribute
documentation (the one for it as a function attribute) starts with "The
@code{deprecated} attribute results in an error", when it should refer to
@code{unavailable} not @code{deprecated}. I don't have further comments
beyond that.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2021-01-04 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D12096AB-DAFD-4B69-B448-DAC32A851B40@sandoe.co.uk>
2020-11-10 7:54 ` [PATCH] " Richard Biener
2020-11-10 11:20 ` Iain Sandoe
2020-11-10 11:58 ` Richard Biener
2020-11-10 15:33 ` Joseph Myers
2020-11-10 19:38 ` [PATCH v2] " Iain Sandoe
2020-11-27 20:49 ` PING^1 " Iain Sandoe
2020-11-30 13:27 ` Nathan Sidwell
2020-11-29 23:00 ` Martin Sebor
2020-11-30 1:56 ` Iain Sandoe
2020-11-30 17:04 ` Martin Sebor
2020-12-01 21:07 ` Iain Sandoe
2020-12-21 19:58 ` Iain Sandoe
2021-01-04 20:19 ` Joseph Myers [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=alpine.DEB.2.22.394.2101042017450.1093969@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=GCC-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).