Rich Felker wrote: > I would prefer something like: > > "glibc historically stores the error number in errno in addition to > returning it. Assuming this behavior is not portable; applications > should use the return value, not errno, to determine the result." I claim that "applications should use the return value, not errno, to determine the result" independently of whether the glibc maintainers decide to keep the current "historical" behaviour or not. Simply because the new text that is scheduled to be included in POSIX Issue 8 does not mention 'errno' here. > Non-setting of errno is not part of the contract of the musl libc > implementation of this function Nonetheless, I find it worth mentioning in the comments (not the text) of the man page, simply because musl libc is currently the most important libc available for Linux that does not set 'errno' here. Bruno
