Re: [PATCH] clean: use warning_errno() when appropriate
Jeff King <peff@peff.net> writes:
> So in that sense doing the errno dance as close to the caller who cares
> is the most _obvious_ thing, even if it isn't the shortest.
Show 6 quoted lines
> It would be nice if there was a way to annotate a function as
> errno-safe, and then transitively compute which other functions were
> errno-safe when they do not call any errno-unsafe function. I don't know
> if any static analyzers allow that kind of custom annotation, though
> (and also I wonder whether the cost/benefit of maintaining those
> annotations would be worth it).
Junio C Hamano <gitster@pobox.com>