Yang Tse wrote:
> It is true that the recent incarnation provides little added value. We
> will get a failure at configuration step, instead of a runtime bug, in
> case some platform has mixed types for the argument whose type would
> be socklen_t in getpeername, getsockname, bind and accept. This kind
> of strange failure wouldn't be detected previously.

There is no problem for functions which take a 'socklen_t' argument,
because of prototypes, only sometimes compiler warnings. (There's no
way to check the type if they don't have prototypes anyway).

The only run-time problem would be functions which take 'socklen_t *'
(or which should).

Are there platform which has mixed types of 'socklen_t *', 'int *',
etc. between the different functions? (Including getnameinfo()).

Thanks,
-- Jamie
Received on 2005-12-16