>> Previous behavior was working correctly. You have to handle
>> at some point and that means when error is handled it is zeroed (or
>> GRUB_ERR_NONE). So code is in callee where that loop was.
>I suggest that we never set grub_errno to 0 (except the initialization).
>That would match the standard errno behavior:
But is it correct to check and handle errno in some `library` function (now we do) ? I CAN, but i do not have to examine errno after each non-error-free call; is it right?