From: Sandra Loosemore <sandra@codesourcery.com>
To: Jonathan Wakely <jwakely@redhat.com>, <gcc@gcc.gnu.org>
Subject: Re: "position independent" vs "position-independent" in documentation
Date: Tue, 01 May 2018 04:12:00 -0000 [thread overview]
Message-ID: <646c8ca5-73bb-7566-abf3-a03c47a02140@codesourcery.com> (raw)
In-Reply-To: <20180430115654.GK20930@redhat.com>
On 04/30/2018 05:56 AM, Jonathan Wakely wrote:
> Should we standardize on "position-independent" and add it to
> https://gcc.gnu.org/codingconventions.html#Spelling ?
The same generic English usage rules apply here as to other compound
phrases; hyphenate when immediately before a noun, don't hyphenate in
other contexts. So "the compiler generates position-independent code"
and "the compiler generates code that is position independent" are both
correct. However, I don't think it's common to use "position
independent" (hyphenated or not) except as a modifier for "code", so you
could add "position-independent code" (rather than just
"position-independent") to the glossary.
-Sandra
next prev parent reply other threads:[~2018-05-01 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 19:02 Jonathan Wakely
2018-05-01 4:12 ` Sandra Loosemore [this message]
2018-05-01 10:17 ` Jonathan Wakely
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=646c8ca5-73bb-7566-abf3-a03c47a02140@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jwakely@redhat.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).