From: Joseph Myers <joseph@codesourcery.com>
To: Martin Sebor <msebor@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [doc PATCH] using multiple format-arg attributes on a single function (PR 87593)
Date: Thu, 11 Oct 2018 23:19:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1810112238140.9740@digraph.polyomino.org.uk> (raw)
In-Reply-To: <7d7bacdc-6163-6e3d-72d4-6e05857c82ee@gmail.com>
On Thu, 11 Oct 2018, Martin Sebor wrote:
> Attached is a documentation-only patch to clarify the use case
> of multiple distinct format_arg attributes on a single function.
> It's far from obvious that the use case makes sense so explicitly
> mentioning it should help avoid the mistake of assuming that
> accepting it is due to the lack of better checking in the area
> (it could also prompt Clang to support the use case -- likely
> an omission due to its obscurity).
This doc patch is OK (though I wonder if it should mention ngettext
explicitly as an example of a use case for multiple format_arg
attributes).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2018-10-11 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 22:39 Martin Sebor
2018-10-11 23:19 ` Joseph Myers [this message]
2018-10-12 2:58 ` Martin Sebor
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.21.1810112238140.9740@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@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).