From: Gerald Pfeifer <gerald@pfeifer.com>
To: Bogdan Harjoc <harjoc@gmail.com>, gcc-patches@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: [cpp,doc] PATCH for Re: CPP documentation minor typo
Date: Mon, 02 Apr 2018 16:04:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1804021803180.5083@anthias.pfeifer.com> (raw)
In-Reply-To: <CAF4+tmrVC_HEABreSVx3kH=keKhgSwWFJcPaZPy1KLOz4=6FvA@mail.gmail.com>
On Tue, 20 Feb 2018, Bogdan Harjoc wrote:
> __VA_OPT__ was documented after 7.3.0 and the eprintf example for it
> ends with two backslashes instead of one:
>
> https://gcc.gnu.org/onlinedocs/cpp/Variadic-Macros.html
Thank you for reporting this, Bogdan.
I just fixed this per the patch below.
Gerald
2018-04-02 Gerald Pfeifer <gerald@pfeifer.com>
* doc/cpp.texi (Variadic Macros): Fix line continuation in an
example.
Index: doc/cpp.texi
===================================================================
--- doc/cpp.texi (revision 259011)
+++ doc/cpp.texi (working copy)
@@ -1710,7 +1710,7 @@
not have any tokens, the @code{@w{__VA_OPT__}} expands to nothing:
@smallexample
-#define eprintf(format, @dots{}) \\
+#define eprintf(format, @dots{}) \
fprintf (stderr, format __VA_OPT__(,) __VA_ARGS__)
@end smallexample
prev parent reply other threads:[~2018-04-02 16:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 9:32 Bogdan Harjoc
2018-04-02 16:04 ` Gerald Pfeifer [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.LSU.2.21.1804021803180.5083@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=harjoc@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).