From owner-freebsd-doc@FreeBSD.ORG Wed Mar 2 03:50:17 2005 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5694716A4CE for ; Wed, 2 Mar 2005 03:50:17 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 36D4643D1D for ; Wed, 2 Mar 2005 03:50:17 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.1/8.13.1) with ESMTP id j223oHJc054792 for ; Wed, 2 Mar 2005 03:50:17 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.1/8.13.1/Submit) id j223oHRd054791; Wed, 2 Mar 2005 03:50:17 GMT (envelope-from gnats) Date: Wed, 2 Mar 2005 03:50:17 GMT Message-Id: <200503020350.j223oHRd054791@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: abc@ai1.anchorage.mtaonline.net Subject: Re: docs/75711: opendir manpage X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: abc@ai1.anchorage.mtaonline.net List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Mar 2005 03:50:17 -0000 The following reply was made to PR docs/75711; it has been noted by GNATS. From: abc@ai1.anchorage.mtaonline.net To: "Giorgos Keramidas" Cc: abc@ai1.anchorage.mtaonline.net, bug-followup@freebsd.org Subject: Re: docs/75711: opendir manpage Date: Wed, 2 Mar 2005 03:49:15 GMT > abc@ai1.anchorage.mtaonline.net wrote: > > man opendir(), only the closedir() info states errno settings. > The opendir() implementation in libc calls the following functions or > systems calls that may fail: close(), fcntl(), fstat(), malloc(), > mergesort(), open(), stat(), reallocf(). > Should we document the join of all the possible errors these calls may > fail with in opendir()'s manpage? the manpage should at LEAST state that it sets the extern "errno", otherwise, it is assumed it doesn't, and this assumption can easily result in programming catastrophies. if "errno" is not documented, and thus, not checked for in a program, "errno" will get trapped by some other function that does check for it. all calls that may set "errno" should explicity say so - so programmers can check for it after a call. thank you.