public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@pfeifer.com>
To: Chris Gregory <czipperz@gmail.com>, gcc-patches@gcc.gnu.org
Cc: gcc@gcc.gnu.org
Subject: [wwwdocs] PATCH for Re: GCC Coding Conventions typo
Date: Tue, 16 Aug 2016 09:28:00 -0000	[thread overview]
Message-ID: <alpine.LSU.2.20.1608161124360.2571@anthias.pfeifer.com> (raw)
In-Reply-To: <CAH6RvXgP6o+RixbWgssKf=d1eP3SuB3KHPqdx0Noz=yzvT3jhg@mail.gmail.com>

On Fri, 22 Apr 2016, Chris Gregory wrote:
> https://gcc.gnu.org/codingconventions.html#ExternC
> 
> In the `Extern "C"` commentary, the coding conventions says:
> 
>     Definitions within the body of a namespace are not indented.
> 
> This should read
> 
>     Definitions within the body of an `extern "C"` block are not indented.

Thank you for the report, Chris!

I just fixed this (finally) by applying the patch below, attributed
to you.

Gerald

Index: codingconventions.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.74
diff -u -r1.74 codingconventions.html
--- codingconventions.html	27 May 2016 19:25:16 -0000	1.74
+++ codingconventions.html	16 Aug 2016 09:23:03 -0000
@@ -1304,7 +1304,7 @@
 </code></pre></blockquote>
 
 <p>
-Definitions within the body of a namespace are not indented.
+Definitions within the body of an <code>extern "C"</code> block are not indented.
 </p>
 
 <h4><a name="Namespace_Form">Namespaces</a></h4>

      reply	other threads:[~2016-08-16  9:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22 17:34 Chris Gregory
2016-08-16  9:28 ` 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.20.1608161124360.2571@anthias.pfeifer.com \
    --to=gerald@pfeifer.com \
    --cc=czipperz@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@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).