public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Vincent Lefevre <vincent+gcc@vinc17.org>
To: gcc@gcc.gnu.org
Subject: Re: "file name" vs "filename"
Date: Sun, 08 Apr 2018 15:18:00 -0000	[thread overview]
Message-ID: <20180407003901.GB8716@zira.vinc17.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1804021210580.14431@digraph.polyomino.org.uk>

On 2018-04-02 12:11:33 +0000, Joseph Myers wrote:
> On Sun, 1 Apr 2018, Gerald Pfeifer wrote:
> 
> > And now to the most important question of all. ;-)  Should we use
> > "file name" or "filename" when referring to the name of a file?
> 
> See the GNU Coding Standards:
> 
>   Please do not use the term ``pathname'' that is used in Unix
>   documentation; use ``file name'' (two words) instead.  We use the term
>   ``path'' only for search paths, which are lists of directory names.

IMHO, "file name" is bad as it is ambiguous if its goal is to mean
either "filename" (in the POSIX sense) or "pathname". At least,
"filename" and "pathname" have been standardized by POSIX.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

  reply	other threads:[~2018-04-07  0:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-01 20:16 Gerald Pfeifer
2018-04-01 20:56 ` Joel Sherrill
2018-04-01 22:55   ` Sandra Loosemore
2018-04-03 23:06     ` Martin Sebor
2018-04-02 12:11 ` Joseph Myers
2018-04-08 15:18   ` Vincent Lefevre [this message]
2023-04-14 22:00   ` Gerald Pfeifer
2023-04-17 18:51     ` James K. Lowden
2023-04-18 11:55       ` Richard Kenner

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=20180407003901.GB8716@zira.vinc17.org \
    --to=vincent+gcc@vinc17.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).