[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: error and program_name
From: |
Bruno Haible |
Subject: |
Re: error and program_name |
Date: |
Wed, 22 Dec 2010 23:07:53 +0100 |
User-agent: |
KMail/1.9.9 |
Ping? No one wants to solve this? It's a critical issue for libposix.
Eric Blake wrote:
> error() is not POSIX. Maybe the thing to do is figure out what in
> libposix is dragging in error(), and work on breaking that dependency.
> That way, a package using libposix then makes their own decision of
> whether to supplement things with error() and program_name.
I replied:
> Very good point. The dependency comes from
>
> openat --> openat-die --> error
> fdopendir
>
> Can you work on breaking this dependency? I mean, for example,
> instead of directly calling openat_save_fail() and
> openat_restore_fail(), go through a variable that contains two
> function pointers, and have openat() and fdopendir() return an error code
> if these function pointers are NULL. Like we do with
> argp_program_version_hook
> error_print_progname
> obstack_alloc_failed_handler
> See also
> c_stack_action
> install_sigpipe_die_handler
Re: error and program_name, Bruce Korb, 2010/12/22
Re: error and program_name, Bruce Korb, 2010/12/30