Pádraig Brady wrote:
BTW if free() may reset errno on some platforms then it's probably worth augmenting the gnulib free() wrapper to restore errno if needed,
The documented GNU behavior for 'free' allows 'free' to set errno, right? So why should the corresponding gnulib wrapper guarantee behavior above and beyond what GNU implements?
It might make sense to have a variant of 'free' that preserves errno, but we should probably give the variant a different name. 'noerr_free', say.
