Re: Fatal warnings in client code

On Tuesday March 07 2023 09:54:32 Lawrence D'Oliveiro wrote:
>On Mon, 06 Mar 2023 21:35:13 +0100, René J.V. Bertin wrote:
>
>> always also return an error that allows the calling code to handle
>> the situation gracefully (and correct the bug).
>
>By definition, if the client code is not using the library correctly,
>it’s not in a position to “correct the bug”. In this situation, it

My bad, "(and allows its developers to correct the bug)". Or at least avoid it.

As implied, I'm not getting into a debate, but let me just add that I wouldn't use an OS in which a central library calls abort every time one of its functions gets called with an invalid argument.

R.