Re: string.h __POSIX_VISIBLE

2014-07-28 Thread Philip Guenther
On Sun, Jul 27, 2014 at 9:14 AM, frantisek holop wrote: > is there a reason why this check should be done twice? > If the code is inextricable, check the history of how it got that way. In this case, there was a mostly mechanical elimination of unnecessary __BSD_VISIBLE clauses which changed di

string.h __POSIX_VISIBLE

2014-07-27 Thread frantisek holop
is there a reason why this check should be done twice? /usr/include/string.h:117: #if __POSIX_VISIBLE >= 200809 char*stpcpy(char *__restrict, const char *__restrict); char*stpncpy(char *__restrict, const char *__restrict, size_t); char*strndup(const char *, size_t); size_t strnlen(c