From owner-freebsd-current Mon Dec 9 9:29:15 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3F7537B401; Mon, 9 Dec 2002 09:29:13 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id F408B43EF2; Mon, 9 Dec 2002 09:29:12 -0800 (PST) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.12.6/8.12.3) with ESMTP id gB9HTCuB056658; Mon, 9 Dec 2002 10:29:12 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Mon, 09 Dec 2002 10:26:49 -0700 (MST) Message-Id: <20021209.102649.81146459.imp@bsdimp.com> To: marc@informatik.uni-bremen.de Cc: mike@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: sys/file.h and POSIX From: "M. Warner Losh" In-Reply-To: <659000000.1039368696@leeloo.intern.geht.de> References: <619340000.1039364545@leeloo.intern.geht.de> <20021208114718.G74206@espresso.q9media.com> <659000000.1039368696@leeloo.intern.geht.de> X-Mailer: Mew version 2.1 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message: <659000000.1039368696@leeloo.intern.geht.de> Marc Recht writes: : > A conforming application cannot make use of facilities outside the : > scope of the standard. This means that if you define : > _POSIX_C_SOURCE=200112L you don't want RPC. : I don't said that the application is _strictly_ POSIX conforming. It only : wants to use POSIX functions and RPC. : FreeBSD's way seems to be not to define POSIX/XSI (and so) on to : _indirectly_ get it and the BSD stuff That's right. We take great care to exclude all namespace pollution when you ask for a specific standard. : Another idea would be to make a WANT_STRICT_POSIX. WANT_STRICT_POSIX is namespace pollution. : > Not really. Conforming applications have no trouble (obviously), : > pseudo-conforming applications only need a little work (removing bogus : > POSIX keywords that specify conformance), and non-conforming BSD : > applications (the majority of software) have no problems. : I had this in mind. : http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap02.html: : : A conforming implementation shall meet all of the following criteria: : [...] : 4. The system may provide additional utilities, functions, or facilities : not required by IEEE Std 1003.1-2001. may != MUST. We do not pollute the name space. Providing additional facilities pollutes the name space, breaking strictly conforming programs. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message