You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've noticed that in the lib folder that are at least a few files that take a socklen_t parameter. Notable examples of this are sock_cmp_addr, sock_cmp_port, and sock_get_port (although, there are others).
None of these functions actually use the socklen_t parameter. Moreover, the sockaddr_in and sockaddr_in6 structs have their on sa_len member. Any idea why the author required the socklen_t parameter despite not actually using it?
The text was updated successfully, but these errors were encountered:
I've noticed that in the lib folder that are at least a few files that take a socklen_t parameter. Notable examples of this are sock_cmp_addr, sock_cmp_port, and sock_get_port (although, there are others).
None of these functions actually use the socklen_t parameter. Moreover, the sockaddr_in and sockaddr_in6 structs have their on sa_len member. Any idea why the author required the socklen_t parameter despite not actually using it?
The text was updated successfully, but these errors were encountered: