[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CVS: cvs.openbsd.org: src
- To: source-changes_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org
- Subject: CVS: cvs.openbsd.org: src
- From: Jun-ichiro itojun Hagino <itojun_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org>
- Date: Fri, 28 Jan 2000 10:47:27 -0700 (MST)
- Reply-to: Jun-ichiro itojun Hagino <itojun_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org>
CVSROOT: /cvs
Module name: src
Changes by: itojun_(_at_)_cvs_(_dot_)_openbsd_(_dot_)_org 2000/01/28 10:47:26
Modified files:
lib/libc/net : freeaddrinfo.c
Log message:
don't permit freeaddrinfo(NULL). now the behavior is consistent
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).
Visit your host, monkey.org