[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bug-gnulib] Re: use of program_name
From: |
James Youngman |
Subject: |
Re: [bug-gnulib] Re: use of program_name |
Date: |
Mon, 9 Jan 2006 15:26:13 +0000 |
User-agent: |
Mutt/1.5.9i |
On Mon, Jan 09, 2006 at 02:49:45PM +0100, Bruno Haible wrote:
> And how about a runtime failure that occurs in every invocation? We
> could add a check in getopt() and getopt_long(), verifying that
> program_name is non-NULL. Most GNU programs use getopt() and
> getopt_long().
I like the principle of this check, but doesn't this produce a problem
with the process of syncing gnulib and glibc? We're talking about a
permanent difference between the getopt() in glibc and the getopt() in
gnulib (since glibc should not force users to call
set_program_name()). After all, there are plenty of non-GNU programs
that use getopt_long().
James.
- Re: getprogname, (continued)
- Re: use of -fno-common on Darwin, James Youngman, 2006/01/10
- Re: getprogname, Bruno Haible, 2006/01/11
- Re: getprogname, Paul Eggert, 2006/01/11
- Re: [bug-gnulib] Re: use of program_name, Bruno Haible, 2006/01/09
- Re: use of program_name, James Youngman, 2006/01/05
- Re: [bug-gnulib] Re: use of program_name, Bruno Haible, 2006/01/09
- Re: [bug-gnulib] Re: use of program_name,
James Youngman <=
- Re: use of program_name, Dave Love, 2006/01/05
- Re: [bug-gnulib] Re: use of program_name, Bruno Haible, 2006/01/09
- Re: [bug-gnulib] Re: use of program_name, Bruno Haible, 2006/01/09
Re: [bug-gnulib] use of program_name, Bruno Haible, 2006/01/09