From: Gerald Pfeifer <gerald@pfeifer.com>
To: Dave Korn <dave.korn@artimi.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Sandra Loosemore <sandra@codesourcery.com>
Cc: gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [wwwdocs] Patch for RE: Coding conventions -- command line option vs command-line option
Date: Thu, 20 Sep 2007 00:52:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0709200030000.26054@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <46EE7009.9020500@codesourcery.com>
On Mon, 17 Sep 2007, Dave Korn wrote:
> Hyphenated. It's not a line option of a command, it's an option of a
> command-line.
On Mon, 17 Sep 2007, Joseph S. Myers wrote:
> As an adjective I think it should be "command-line"; I'm sure Sandra will
> correct me if I'm wrong here.
On Mon, 17 Sep 2007, Sandra Loosemore wrote:
> As an adjective immediately preceding the noun it modifies, yes, it should be
> hyphenated: "command-line option". But if you use "command line" as a noun,
> use the unhyphenated form; e.g., "use the -foo option on the command line".
Thanks to the three of you for your guidance on this, Dave, Joseph, and
Sandra!
I am committing the patch below to our coding conventions and will fix
up the existing web pages accordingly.
Gerald
Index: codingconventions.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.52
diff -u -3 -p -r1.52 codingconventions.html
--- codingconventions.html 10 Sep 2007 18:45:48 -0000 1.52
+++ codingconventions.html 19 Sep 2007 22:29:05 -0000
@@ -270,6 +270,11 @@ and code. The following table lists som
<td></td>
</tr>
<tr>
+ <td>"command-line option"</td>
+ <td>"command line option"</td>
+ <td></td>
+ </tr>
+ <tr>
<td>"dependent" (adjective), "dependence", "dependency"</td>
<td>"dependant", "dependance", "dependancy"</td>
<td></td>
next parent reply other threads:[~2007-09-19 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.64.0709141157300.11229@acrux.dbai.tuwien.ac.at>
[not found] ` <Pine.LNX.4.64.0709171123520.29659@digraph.polyomino.org.uk>
[not found] ` <46EE7009.9020500@codesourcery.com>
2007-09-20 0:52 ` Gerald Pfeifer [this message]
2007-09-20 18:57 ` Dave Korn
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=Pine.LNX.4.64.0709200030000.26054@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=dave.korn@artimi.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=sandra@codesourcery.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).