Silently handle freeaddrinfo(NULL) for compatibility with code which works on other OSes.

[kib]

Summary

Also avoid unnecessary NULL check, free(NULL) is valid.

I did read https://lists.freebsd.org/pipermail/freebsd-net/2004-September/005065.html. But Linux accepts NULL and more and more code just expects this to work. It costs nothing to us, while removing another trip over the porting.

[• hselasky]

lib/libc/net/getaddrinfo.c

38 ↗

(On Diff #33009)

s/current/Current/

[kib]

Capitalize start of sentence.

[bjk]

lib/libc/net/getaddrinfo.3

364 ↗

(On Diff #33011)

I would suggest something like:
The behavior of
.Li freeadrinfo(NULL)
is left unspecified by both
.St -susv4
and
.Dv "RFC 3493" .
The current implementation ignores a
.Dv NULL
argument for compatibility with programs that rely on the implementation
details of other operating systems.

A potential alternative to ".Li freeaddrinfo(NULL)" is "a .Dv NULL argument to .Nm" (with appropriate newlines).

[kib]

bjk suggestion on the proper language.