summaryrefslogtreecommitdiff
path: root/lib/libc/net/freeaddrinfo.c
AgeCommit message (Collapse)Author
2000-01-28don't permit freeaddrinfo(NULL). now the behavior is consistentJun-ichiro itojun Hagino
across {free,net,open}bsd. both rfc2553 and X/Open spec are silent about the behavior, and there's no strong consensus either. i think library should NOT be forgiving in this case, to promote development of more robust 3rd-party codebase (code works on "freeaddrinfo(NULL) = SEGV" will work on "freeaddrinfo(NULL) is okay" environment, but not the other way around). only issue i have now is NRL freeaddrinfo() compatibility, which permits freeaddrinfo(NULL).
2000-01-27avoid memory leakage on freeaddrinfo().Jun-ichiro itojun Hagino
(this bug was introduced since we mix KAME getaddrinfo and NRL freeaddrinfo).
1999-06-23KNFTheo de Raadt
1999-06-23Added some protocol independent interfaces (supposedly IPv6 support APIs, butcmetz
ones that are useful for all protocols, not just IPv6).