Date: Wed, 12 Mar 2003 22:42:35 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Sean Chittenden <seanc@FreeBSD.ORG> Cc: standards@FreeBSD.ORG Subject: Re: environ.7 update (#include <unistd.h> ?)... Message-ID: <20030312222222.F29327@gamplex.bde.org> In-Reply-To: <20030312091658.GS79234@perrin.int.nxad.com> References: <20030312091658.GS79234@perrin.int.nxad.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 12 Mar 2003, Sean Chittenden wrote: > Simple question: should environ(7) be updated to include <unistd.h> in > its SYNOPSIS? > > It's not required, but I think it's good form to do so. There was > some debate as to this on IRC so I'm positing the question. No. Includes don't belong in section 7 man pages, and environ isn't even declared in <unistd.h>. It is intentionally not declared in any header in POSIX.1-2001(draft7): 547 2.2.2 The Name Space 548 All identifiers in this volume of IEEE Std 1003.1-200x, except environ, are defined in at least one 549 of the headers, as shown in the Base Definitions volume of IEEE Std 1003.1-200x, Chapter 13, ... 2229 A.8.1 Environment Variable Definition 2230 The variable environ is not intended to be declared in any header, but rather to be declared by the 2231 user for accessing the array of strings that is the environment. This is the traditional usage of the 2232 symbol. Putting it into a header could break some programs that use the symbol for their own 2233 purposes. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030312222222.F29327>