From: Gerald Pfeifer <gerald@pfeifer.com>
To: gcc-patches@gcc.gnu.org
Cc: Sandra Loosemore <sandra@codesourcery.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: [pushed] wwwdocs: codingconventions: Recommend "file name" over "filename"
Date: Fri, 14 Apr 2023 23:51:12 +0200 (CEST) [thread overview]
Message-ID: <20230414215115.2011733E1A@hamza.pair.com> (raw)
This is based on an exchange with Sandra and Joseph back in, umm,
April 2018.
Pushed for now.
Gerald
---
This aligns with the C and C++ standards as well as the GNU Coding
Standards, though POSIX uses "filename" as a component of "pathname".
---
htdocs/codingconventions.html | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index 8b3cb8bb..9b6d243d 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -469,6 +469,11 @@ and code. The following table lists some simple cases:</p>
<td>"run time" or "runtime"</td>
<td></td>
</tr>
+ <tr>
+ <td>file name</td>
+ <td>filename</td>
+ <td></td>
+ </tr>
<tr>
<td>"floating-point" (adjective)</td>
<td>"floating point"</td>
--
2.40.0
reply other threads:[~2023-04-14 21:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230414215115.2011733E1A@hamza.pair.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@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).