Re: error and program_name

[Bruce Korb]

On 12/22/10 14:07, Bruno Haible wrote:
> Ping? No one wants to solve this? It's a critical issue for libposix.

I don't mind breaking the link, but I've been defocused by focusing
on too many things at once.  I'm leaving for Christmas in a few hours.
I'll try to get to it later next week.

Thank you for the ping.

Regards & merry Christmas to all -- Bruce

> 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
> 
>