Re: copy-file: Silence gcc warnings

[Paul Eggert]

On 2023-05-26 15:41, Bruno Haible wrote:
> Maybe by defining
> error and error_at_line as inline functions

They're defined by glibc, no? The definitions might collide. Also, I 
suppose the compiler might not inline them and then we'd get a 
diagnostic anyway.

The basic problem is that the old 'error' API doesn't mix well with 
[[noreturn]] and the like. We could write a new function, "eexit" say, 
that behaves like "error" except it never returns. (I chose the name 
"eexit" so as to not mess up the indenting of existing code.)

Or we could just live with "die", as it works.