From: Jonathan Wakely <jwakely@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Add reference to pp_format to Coding Conventions
Date: Wed, 21 Sep 2022 10:39:27 +0100 [thread overview]
Message-ID: <20220921093927.870907-1-jwakely@redhat.com> (raw)
Finding the docs for the GCC-specific diagnostic formats isn't easy.
This might help.
OK for wwwdocs?
---
htdocs/codingconventions.html | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index e4d30510..f1d1f165 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -333,7 +333,8 @@ code token.</li>
<li>Diagnostics using the GCC diagnostic functions should generally
use the GCC-specific formats such as <code>%qs</code> or
<code>%<</code> and <code>%></code> for quoting and
-<code>%m</code> for <code>errno</code> numbers.</li>
+<code>%m</code> for <code>errno</code> numbers. See
+<tt>pp_format</tt> in <tt>pretty-print.cc</tt> for supported formats.</li>
<li>Identifiers should generally be formatted with <code>%E</code> or
<code>%qE</code>; use of <code>identifier_to_locale</code> is needed
--
2.37.3
next reply other threads:[~2022-09-21 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 9:39 Jonathan Wakely [this message]
2022-10-18 11:15 ` [ping] " Jonathan Wakely
2022-10-18 11:27 ` Jakub Jelinek
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=20220921093927.870907-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@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: 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).