Bruno Haible <[EMAIL PROTECTED]> writes: > Normally <sys/types.h> and <sys/socket.h> should be sufficient to get > socklen_t. Which are the systems where it needs <netdb.h>?
I don't know; POSIX says both sys/socket.h and netdb.h should declare socklen_t, I was thinking of the case where a system doesn't have sys/socket.h but has netdb.h. Do you think we should only test for it in sys/types.h + sys/socket.h? There is a problem, of course, if it _is_ defined in netdb.h and the application include that header file, but the test does not look there. Then there will be a type conflict. Perhaps the M4 macro should create a socklen.h that include the proper header files that is required to get the socklen_t type? That would be the most flexible, I think. But it has the disadvantage that applications need to include socklen.h, instead of simply using socklen_t directly without worrying. Thanks, Simon _______________________________________________ bug-gnulib mailing list bug-gnulib@gnu.org http://lists.gnu.org/mailman/listinfo/bug-gnulib
