From: Ben Elliston <bje@au1.ibm.com>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH, doc]: Fix typo.
Date: Tue, 01 Apr 2008 05:34:00 -0000 [thread overview]
Message-ID: <1207027909.8147.1.camel@localhost> (raw)
I'm committing the following as obvious. I'm reasonably certain to have
got the intended meaning correct here, but if I haven't, please let me
know. In the meantime, I don't think this patch will make things
worse. :-)
Cheers, Ben
2008-04-01 Ben Elliston <bje@au.ibm.com>
* doc/c-tree.texi (Function Basics): Fix grammatical error.
Index: doc/c-tree.texi
===================================================================
--- doc/c-tree.texi (revision 133784)
+++ doc/c-tree.texi (working copy)
@@ -1508,7 +1508,7 @@ whose @code{TREE_VALUE} represents a typ
@item TYPE_NOTHROW_P
This predicate holds when the exception-specification of its arguments
-if of the form `@code{()}'.
+is of the form `@code{()}'.
@item DECL_ARRAY_DELETE_OPERATOR_P
This predicate holds if the function an overloaded
next reply other threads:[~2008-04-01 5:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 5:34 Ben Elliston [this message]
2008-04-01 10:47 ` Tom Browder
2008-04-02 2:47 ` Ben Elliston
2008-04-06 18:54 ` Gerald Pfeifer
2008-04-07 11:49 ` Tom Browder
2020-04-01 17:19 [PATCH] doc: " Segher Boessenkool
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=1207027909.8147.1.camel@localhost \
--to=bje@au1.ibm.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).