Re: documentation about program_name use

[Claudio Fontana]

--- Paul Eggert <address@hidden> ha scritto: 

> Claudio Fontana <address@hidden> writes:
> 
> > I'd suggest it is prominently displayed in the
> bug-gnulib manual and
> > error module documentation.
> 
> Better yet, there should be some automated way of
> detecting the
> portability problem, even when you are testing on a
> GNU/Linux host
> where program_name is supplied.

Right. I found a progname module in gnulib, which
defines program_name as

const char* program_name;

and proceeds to define some functions to initialize
and retreive it. As much as I hate the const
qualifier, it could be good.

There is a missing dependency at least in the error
module, which should require progname.

A test could then be added as m4/progname.m4 to check
availability of the program_name definition, and if
not provided by the system, the replacement
lib/progname.c and lib/progname.h can be used.

> Perhaps the Makefile.maint stuff we're talking about
> could do that.

I don't know anything about Makefile.maint. Nothing
relevant in the many google matches or in the
bug-gnulib archive.
However, please keep it as simple as possible, gnulib
should make things easier.

CLaudio



                
___________________________________ 
Yahoo! Messenger with Voice: chiama da PC a telefono a tariffe esclusive 
http://it.messenger.yahoo.com