2 ms·
The complaint is that the underlying function which returns the thread-local errno pointer isn’t a public API, isn’t standardised, and its name varies from OS t
by skissane 7y ago
The complaint is that the underlying function which returns the thread-local errno pointer isn’t a public API, isn’t standardised, and its name varies from OS to OS (__errno or __error or __errno_location)
This specific case would be resolved if some standard (ISO C, POSIX, etc) defined a public API to do it, e.g. errno_r
(Of course, that doesn’t fix any other cases where some public functions are really macros to private functions, but this appears to be the most significant such case.)