[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: conflicts between pathname.h and dirname.h

From: James Youngman
Subject: Re: conflicts between pathname.h and dirname.h
Date: Sun, 25 Feb 2007 11:02:28 +0000

On 2/22/07, Paul Eggert <address@hidden> wrote:

The GNU Coding Standards say that one shouldn't use the word
"pathname" to describe file names.

Yes.  For this reason findutils added a -wholename synonym for -path
(RMS requested this).  I complied, but now I think we may have chosen
the name too hastily.  The argument of -path may not be absolute (e.g.
find foo -path foo/bar -prune -o -print) and so calling it -wholename
is arguably misleading.

However, I can't immediately think of a word what describes a
qualified but not necessarily absolute path (e.g. foo/bar) which meets
the GNU coding standards.  Maybe "qualified file name", but that
doesn't easily translate into a mnemonic name for a test.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]