[Top][All Lists]

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

Re: [bug-gnulib] gnulib broken on systems lacking fchdir

From: Bruno Haible
Subject: Re: [bug-gnulib] gnulib broken on systems lacking fchdir
Date: Thu, 30 Nov 2006 15:18:14 +0100
User-agent: KMail/1.9.1

Eric Blake wrote:
> Also, GNU coding 
> standards recommend using just 'name', rather than 'filename' or even 'file'.

Huh? I think there is a misunderstanding. The GNU standards don't want
'pathname' to occur in the documentation in the sense as POSIX uses it,
because of the PATH variable and the concept of search paths. Paul then
doesn't want to use 'pathname' in code either, so that there are less
differences between the code and user documentation. But 'filename' and
'file' are fine according to everyone.

Personally I find 'name' a bad identifier in this context, because 'name'
can be a property name, table name, program name, user name, etc.
'filename' sounds better, or 'dir_name' which says what it really is.


reply via email to

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