This is the mail archive of the
mailing list for the GCC project.
Re: "file name" vs "filename"
- From: Sandra Loosemore <sandra at codesourcery dot com>
- To: <joel at rtems dot org>, Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: <gcc at gcc dot gnu dot org>, "Joseph S. Myers" <joseph at codesourcery dot com>
- Date: Sun, 1 Apr 2018 16:54:55 -0600
- Subject: Re: "file name" vs "filename"
- References: <alpine.LSU.firstname.lastname@example.org> <CAF9ehCUOwO4sHf577B5oJE0pNwkVujM7tUTX=9MK_3+HOqZCNw@mail.gmail.com>
On 04/01/2018 02:56 PM, Joel Sherrill wrote:
On Sun, Apr 1, 2018, 3:16 PM Gerald Pfeifer <email@example.com
And now to the most important question of all. ;-) Should we use
"file name" or "filename" when referring to the name of a file?
Our docs currently are about even and I think it would be good to
settle on one?
% grep "filename" $GCC/gcc/doc/*.texi | wc -l
% grep "file name" $GCC/gcc/doc/*.texi | wc -l
(Once we have consensus, I'll add that to codingconventions.html
and start by making the web pages consistent.)
Searching and looking at online dictionaries, it looks like filename is
the currently preferred form.
The C and C++ standards documents use "file name"; there are other
places ("bit-field") where the GCC manual has adopted the C standard
In this case it might be more appropriate to adopt the POSIX
conventions, since I suspect most of the uses in the GCC documentation
refer to the host environment rather than the target language. This
looks like the POSIX glossary:
Here "filename" is given as the correct spelling, except that that
glossary distinguishes between "filename" and "pathname" (a "filename"
is the same as a "pathname component"). So perhaps many of the "file
name"/"filename" uses in the GCC manual ought to be "pathname" instead?