From owner-freebsd-standards Sun Mar 9 6:27: 0 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E5BC37B401 for ; Sun, 9 Mar 2003 06:26:59 -0800 (PST) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id D691E43FA3 for ; Sun, 9 Mar 2003 06:26:58 -0800 (PST) (envelope-from leimy2k@mac.com) Received: from asmtp01.mac.com (asmtp01-qfe3 [10.13.10.65]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h29EQw5f016839 for ; Sun, 9 Mar 2003 06:26:58 -0800 (PST) Received: from mac.com ([216.78.178.84]) by asmtp01.mac.com (Netscape Messaging Server 4.15) with ESMTP id HBHK4X00.THY for ; Sun, 9 Mar 2003 06:26:57 -0800 Date: Sun, 9 Mar 2003 08:26:57 -0600 Mime-Version: 1.0 (Apple Message framework v551) Content-Type: text/plain; charset=US-ASCII; format=flowed Subject: previous implementation of getpwnam_r From: David Leimbach To: freebsd-standards@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: <2F2A12C6-523B-11D7-969F-0003937E39E0@mac.com> X-Mailer: Apple Mail (2.551) Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG So does anyone have "anything" I can look at that would at least conform to the correct "style" and placement of the getpwnam_r implementation? It said it was 1/2 done and that Wes Peters was working on it [IIRC]. I'd like to see what he had. Someone who did the getpwnam function or was working on it was in contact with me also saying he was going to try to implement this as well but I don't believe he has synced up with the people on this project to do so. This leaves me in a somewhat ambiguous state of not being able to find my ass with both hands as to what the next move is. 1. Do I put this implementation in libc_r? or is that just for the userland version of pthreads and nothing else? 2. If not one where exactly is this implementation expected? Next to getpwnam? Any direction anyone can provide or incomplete attempts at this function would pretty much be a big help to my completion of this task. Dave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Sun Mar 9 22:15:53 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08B9237B404; Sun, 9 Mar 2003 22:15:51 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7200E43F93; Sun, 9 Mar 2003 22:15:49 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.8/8.12.8) with ESMTP id h2A6Fmjx085410; Mon, 10 Mar 2003 09:15:48 +0300 (MSK) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.8/8.12.6/Submit) id h2A6Fme5085409; Mon, 10 Mar 2003 09:15:48 +0300 (MSK) (envelope-from ache) Date: Mon, 10 Mar 2003 09:15:48 +0300 From: "Andrey A. Chernov" To: standards@freebsd.org, current@freebsd.org Subject: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030310061548.GA85361@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Many programs (from ports too) defines _ISOC99_SOURCE to get C99 functions, but we don't sense this define currently. Here is the fix for review: --- cdefs.h.bak Wed Oct 23 05:04:06 2002 +++ cdefs.h Mon Mar 10 09:11:01 2003 @@ -360,6 +360,9 @@ #define __POSIX_VISIBLE 198808 #define __ISO_C_VISIBLE 0 #endif /* _POSIX_C_SOURCE */ +#ifdef _ISOC99_SOURCE +#define __ISO_C_VISIBLE 1999 +#endif #else /*- * Deal with _ANSI_SOURCE: @@ -378,7 +381,7 @@ #define __XSI_VISIBLE 0 #define __BSD_VISIBLE 0 #define __ISO_C_VISIBLE 1990 -#elif defined(_C99_SOURCE) /* Localism to specify strict C99 env. */ +#elif defined(_ISOC99_SOURCE) /* Strict C99 env. */ #define __POSIX_VISIBLE 0 #define __XSI_VISIBLE 0 #define __BSD_VISIBLE 0 -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Mon Mar 10 7:57:41 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 04B6A37B401; Mon, 10 Mar 2003 07:57:40 -0800 (PST) Received: from espresso.bsdmike.org (espresso.bsdmike.org [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5BAD743FDF; Mon, 10 Mar 2003 07:57:39 -0800 (PST) (envelope-from mike@espresso.bsdmike.org) Received: by espresso.bsdmike.org (Postfix, from userid 1002) id D12289C62; Mon, 10 Mar 2003 10:44:34 -0500 (EST) Date: Mon, 10 Mar 2003 10:44:34 -0500 From: Mike Barcroft To: "Andrey A. Chernov" Cc: standards@freebsd.org, current@freebsd.org Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030310104434.P70629@espresso.bsdmike.org> References: <20030310061548.GA85361@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030310061548.GA85361@nagual.pp.ru>; from ache@nagual.pp.ru on Mon, Mar 10, 2003 at 09:15:48AM +0300 Organization: The FreeBSD Project Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrey A. Chernov writes: > Many programs (from ports too) defines _ISOC99_SOURCE to get C99 > functions, but we don't sense this define currently. Here is the fix for > review: Cool. I didn't realize there was an existing precedence, or I would have used it. > --- cdefs.h.bak Wed Oct 23 05:04:06 2002 > +++ cdefs.h Mon Mar 10 09:11:01 2003 > @@ -360,6 +360,9 @@ > #define __POSIX_VISIBLE 198808 > #define __ISO_C_VISIBLE 0 > #endif /* _POSIX_C_SOURCE */ > +#ifdef _ISOC99_SOURCE > +#define __ISO_C_VISIBLE 1999 > +#endif This part isn't needed... > #else > /*- > * Deal with _ANSI_SOURCE: > @@ -378,7 +381,7 @@ > #define __XSI_VISIBLE 0 > #define __BSD_VISIBLE 0 > #define __ISO_C_VISIBLE 1990 > -#elif defined(_C99_SOURCE) /* Localism to specify strict C99 env. */ > +#elif defined(_ISOC99_SOURCE) /* Strict C99 env. */ > #define __POSIX_VISIBLE 0 > #define __XSI_VISIBLE 0 > #define __BSD_VISIBLE 0 ...since the next line here is: #define __ISO_C_VISIBLE 1999 Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 6:45: 8 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 673B437B404; Tue, 11 Mar 2003 06:45:06 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0F5B43F85; Tue, 11 Mar 2003 06:45:04 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.8/8.12.8) with ESMTP id h2BEj3jx000941; Tue, 11 Mar 2003 17:45:03 +0300 (MSK) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.8/8.12.6/Submit) id h2BEj3BY000940; Tue, 11 Mar 2003 17:45:03 +0300 (MSK) (envelope-from ache) Date: Tue, 11 Mar 2003 17:45:02 +0300 From: "Andrey A. Chernov" To: Mike Barcroft Cc: standards@FreeBSD.org, current@FreeBSD.org Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311144501.GA364@nagual.pp.ru> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030310104434.P70629@espresso.bsdmike.org> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Mar 10, 2003 at 10:44:34 -0500, Mike Barcroft wrote: > Andrey A. Chernov writes: > > Many programs (from ports too) defines _ISOC99_SOURCE to get C99 > > functions, but we don't sense this define currently. Here is the fix for > > review: > > Cool. I didn't realize there was an existing precedence, or I would > have used it. Just search Google about _ISOC99_SOURCE and see :-) > This part isn't needed... > > > #else > > /*- > > * Deal with _ANSI_SOURCE: > > @@ -378,7 +381,7 @@ > > #define __XSI_VISIBLE 0 > > #define __BSD_VISIBLE 0 > > #define __ISO_C_VISIBLE 1990 > > -#elif defined(_C99_SOURCE) /* Localism to specify strict C99 env. */ > > +#elif defined(_ISOC99_SOURCE) /* Strict C99 env. */ > > #define __POSIX_VISIBLE 0 > > #define __XSI_VISIBLE 0 > > #define __BSD_VISIBLE 0 > > ...since the next line here is: > > #define __ISO_C_VISIBLE 1999 Hm, I don't quite understand, which one part you mean? My patch handles 2 following cases: 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in the same time. 2) _ISOC99_SOURCE without any _POSIX_C_SOURCE. In that case it overrides _ANSI_SOURCE like old _C99_SOURCE does. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 8: 2:52 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E285D37B401; Tue, 11 Mar 2003 08:02:50 -0800 (PST) Received: from espresso.bsdmike.org (espresso.bsdmike.org [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 507DE43FAF; Tue, 11 Mar 2003 08:02:50 -0800 (PST) (envelope-from mike@espresso.bsdmike.org) Received: by espresso.bsdmike.org (Postfix, from userid 1002) id 790E89C5F; Tue, 11 Mar 2003 10:49:43 -0500 (EST) Date: Tue, 11 Mar 2003 10:49:43 -0500 From: Mike Barcroft To: "Andrey A. Chernov" Cc: standards@FreeBSD.org, current@FreeBSD.org Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311104943.A88290@espresso.bsdmike.org> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030311144501.GA364@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Mar 11, 2003 at 05:45:02PM +0300 Organization: The FreeBSD Project Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrey A. Chernov writes: > Hm, I don't quite understand, which one part you mean? My patch handles > 2 following cases: > > 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example > (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in > the same time. I don't like this at all. The meaning of _ANSI_SOURCE is that the source is exclusively written in C89 with no BSD, POSIX, or XSI extentions. Similarly, I was intending _C99_SOURCE to be used without any POSIX. Programs looking for C99+POSIX functions should specify POSIX.1-2001, which incorporates both of these. > 2) _ISOC99_SOURCE without any _POSIX_C_SOURCE. In that case it overrides > _ANSI_SOURCE like old _C99_SOURCE does. Yes, _ANSI_SOURCE and any other standard constant are mutually exclusive. Defining _C99_SOURCE or _ANSI_SOURCE with some other standard constant results in unspecified behaviour. I'd like to keep things this way if you're going to rename _C99_SOURCE. Best regards, Mike BArcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 8:42:47 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 53E0F37B401; Tue, 11 Mar 2003 08:42:46 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA69043FCB; Tue, 11 Mar 2003 08:42:44 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.8/8.12.8) with ESMTP id h2BGghjx002470; Tue, 11 Mar 2003 19:42:43 +0300 (MSK) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.8/8.12.6/Submit) id h2BGghYV002469; Tue, 11 Mar 2003 19:42:43 +0300 (MSK) (envelope-from ache) Date: Tue, 11 Mar 2003 19:42:41 +0300 From: "Andrey A. Chernov" To: Mike Barcroft Cc: standards@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311164240.GA2305@nagual.pp.ru> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030311104943.A88290@espresso.bsdmike.org> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Mar 11, 2003 at 10:49:43 -0500, Mike Barcroft wrote: > > 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example > > (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in > > the same time. > > I don't like this at all. The meaning of _ANSI_SOURCE is that the > source is exclusively written in C89 with no BSD, POSIX, or XSI > extentions. Similarly, I was intending _C99_SOURCE to be used without > any POSIX. Programs looking for C99+POSIX functions should specify > POSIX.1-2001, which incorporates both of these. What to do, if, say, C99 program want to use some POSIX functions from lower (and not from higher) POSIX standard? Currently we have problem with ImageMagick - undefined prototypes for vsnprintf() and other like, because it wants right that: magick/studio.h: ... #define _GNU_SOURCE 1 #define _ISOC99_SOURCE 1 #define _POSIX_C_SOURCE 199506L #define _XOPEN_SOURCE 500 #define _LARGEFILE64_SOURCE 1 -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 8:51: 2 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 74A3137B405; Tue, 11 Mar 2003 08:51:01 -0800 (PST) Received: from espresso.bsdmike.org (espresso.bsdmike.org [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id B9E0443F93; Tue, 11 Mar 2003 08:51:00 -0800 (PST) (envelope-from mike@espresso.bsdmike.org) Received: by espresso.bsdmike.org (Postfix, from userid 1002) id 329D79C5F; Tue, 11 Mar 2003 11:37:54 -0500 (EST) Date: Tue, 11 Mar 2003 11:37:54 -0500 From: Mike Barcroft To: "Andrey A. Chernov" Cc: standards@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311113754.C88290@espresso.bsdmike.org> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org> <20030311164240.GA2305@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030311164240.GA2305@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Mar 11, 2003 at 07:42:41PM +0300 Organization: The FreeBSD Project Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrey A. Chernov writes: > On Tue, Mar 11, 2003 at 10:49:43 -0500, Mike Barcroft wrote: > > > 1) Any _POSIX_C_SOURCE with _ISOC99_SOURCE. It is from real life example > > > (ImageMagick). It wants lower POSIX level, *but* wants _ISOC99_SOURCE in > > > the same time. > > > > I don't like this at all. The meaning of _ANSI_SOURCE is that the > > source is exclusively written in C89 with no BSD, POSIX, or XSI > > extentions. Similarly, I was intending _C99_SOURCE to be used without > > any POSIX. Programs looking for C99+POSIX functions should specify > > POSIX.1-2001, which incorporates both of these. > > What to do, if, say, C99 program want to use some POSIX functions from > lower (and not from higher) POSIX standard? I think this is pretty rare. POSIX provides application writers with lots of time to transition away from deprecated interfaces. What functions are missing if you change _POSIX_C_SOURCE to 200112L and remove _ISOC99_SOURCE from the code you posted? Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 9:36:48 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7F0E237B401; Tue, 11 Mar 2003 09:36:47 -0800 (PST) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6892643FBF; Tue, 11 Mar 2003 09:36:46 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: from khavrinen.lcs.mit.edu (localhost.ipv6.lcs.mit.edu [IPv6:::1]) by khavrinen.lcs.mit.edu (8.12.8/8.12.8) with ESMTP id h2BHajCd062940 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 11 Mar 2003 12:36:45 -0500 (EST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.12.8/8.12.8/Submit) id h2BHaiBL062937; Tue, 11 Mar 2003 12:36:44 -0500 (EST) (envelope-from wollman) Date: Tue, 11 Mar 2003 12:36:44 -0500 (EST) From: Garrett Wollman Message-Id: <200303111736.h2BHaiBL062937@khavrinen.lcs.mit.edu> To: "Andrey A. Chernov" Cc: Mike Barcroft , standards@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: CFR: add widely accepted _ISOC99_SOURCE In-Reply-To: <20030311164240.GA2305@nagual.pp.ru> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org> <20030311164240.GA2305@nagual.pp.ru> Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG < said: > What to do, if, say, C99 program want to use some POSIX functions from > lower (and not from higher) POSIX standard? Programmer error. Either it's a C99 program or it's an old-POSIX program; it cannot be both. > #define _GNU_SOURCE 1 > #define _ISOC99_SOURCE 1 > #define _POSIX_C_SOURCE 199506L > #define _XOPEN_SOURCE 500 > #define _LARGEFILE64_SOURCE 1 It is requesting contradictory namespaces, and getting what it deserves. It should not define any of these. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 9:54: 7 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B559937B401; Tue, 11 Mar 2003 09:54:06 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9D6E343FBF; Tue, 11 Mar 2003 09:54:04 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.8/8.12.8) with ESMTP id h2BHs3jx004073; Tue, 11 Mar 2003 20:54:03 +0300 (MSK) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.8/8.12.6/Submit) id h2BHs3Wd004072; Tue, 11 Mar 2003 20:54:03 +0300 (MSK) (envelope-from ache) Date: Tue, 11 Mar 2003 20:54:02 +0300 From: "Andrey A. Chernov" To: Mike Barcroft Cc: standards@FreeBSD.org Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311175402.GA3885@nagual.pp.ru> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org> <20030311164240.GA2305@nagual.pp.ru> <20030311113754.C88290@espresso.bsdmike.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030311113754.C88290@espresso.bsdmike.org> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [current@ trimmed...] On Tue, Mar 11, 2003 at 11:37:54 -0500, Mike Barcroft wrote: > > What to do, if, say, C99 program want to use some POSIX functions from > > lower (and not from higher) POSIX standard? > > I think this is pretty rare. POSIX provides application writers with > lots of time to transition away from deprecated interfaces. What > functions are missing if you change _POSIX_C_SOURCE to 200112L and > remove _ISOC99_SOURCE from the code you posted? If POSIX bumped higher, it compiles cleanly, but I notice that problem with _ISOC99_SOURCE is different: 1) It seems that _ISOC99_SOURCE is Linuxism. 2) In Linux it not means _strict_ C99 environment, but means "turn on C99 extensions". In Linux it is always used _in_addition_ to _GNU_SOURCE, _BSD_SOURCE and other like. It means we can't replace our _C99_SOURCE localism with _ISOC99_SOURCE as in my patch. 3) The question is: should we even support _ISOC99_SOURCE in its current Linux form, i.e. as "turn C99 extensions on"? -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 9:58:40 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 67CAD37B401; Tue, 11 Mar 2003 09:58:39 -0800 (PST) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 37F6243F93; Tue, 11 Mar 2003 09:58:38 -0800 (PST) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.8/8.12.8) with ESMTP id h2BHwbjx004139; Tue, 11 Mar 2003 20:58:37 +0300 (MSK) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.8/8.12.6/Submit) id h2BHwacM004138; Tue, 11 Mar 2003 20:58:36 +0300 (MSK) (envelope-from ache) Date: Tue, 11 Mar 2003 20:58:36 +0300 From: "Andrey A. Chernov" To: Garrett Wollman Cc: Mike Barcroft , standards@FreeBSD.ORG Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311175835.GB3885@nagual.pp.ru> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org> <20030311164240.GA2305@nagual.pp.ru> <200303111736.h2BHaiBL062937@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200303111736.h2BHaiBL062937@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.5.1i Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [current@ trimmed...] On Tue, Mar 11, 2003 at 12:36:44 -0500, Garrett Wollman wrote: > > #define _GNU_SOURCE 1 > > #define _ISOC99_SOURCE 1 > > #define _POSIX_C_SOURCE 199506L > > #define _XOPEN_SOURCE 500 > > #define _LARGEFILE64_SOURCE 1 > > It is requesting contradictory namespaces, and getting what it > deserves. It should not define any of these. After some investigations I found that this usage is Linuxism. In Linux most of this options means not strict environment but "turn this extension on" instead. See my recent reply to Mike about should we even support _ISOC99_SOURCE as Linuxism... -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 13:49: 6 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5C2A37B401; Tue, 11 Mar 2003 13:49:05 -0800 (PST) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B43043FE0; Tue, 11 Mar 2003 13:49:05 -0800 (PST) (envelope-from des@ofug.org) Received: by flood.ping.uio.no (Postfix, from userid 2602) id 5BC4C5308; Tue, 11 Mar 2003 22:49:03 +0100 (CET) X-URL: http://www.ofug.org/~des/ X-Disclaimer: The views expressed in this message do not necessarily coincide with those of any organisation or company with which I am or have been affiliated. To: "Andrey A. Chernov" Cc: Garrett Wollman , Mike Barcroft , standards@FreeBSD.ORG Subject: Re: CFR: add widely accepted _ISOC99_SOURCE From: Dag-Erling Smorgrav Date: Tue, 11 Mar 2003 22:49:02 +0100 In-Reply-To: <20030311175835.GB3885@nagual.pp.ru> ("Andrey A. Chernov"'s message of "Tue, 11 Mar 2003 20:58:36 +0300") Message-ID: User-Agent: Gnus/5.090014 (Oort Gnus v0.14) Emacs/21.2 (i386--freebsd) References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org> <20030311164240.GA2305@nagual.pp.ru> <200303111736.h2BHaiBL062937@khavrinen.lcs.mit.edu> <20030311175835.GB3885@nagual.pp.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Andrey A. Chernov" writes: > After some investigations I found that this usage is Linuxism. In Linux > most of this options means not strict environment but "turn this extension > on" instead. See my recent reply to Mike about should we even support > _ISOC99_SOURCE as Linuxism... One more reason to dislike Linux... DES -- Dag-Erling Smorgrav - des@ofug.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Tue Mar 11 19:11: 1 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0FE6037B401 for ; Tue, 11 Mar 2003 19:11:01 -0800 (PST) Received: from espresso.bsdmike.org (espresso.bsdmike.org [65.39.129.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 85F3843F3F for ; Tue, 11 Mar 2003 19:11:00 -0800 (PST) (envelope-from mike@espresso.bsdmike.org) Received: by espresso.bsdmike.org (Postfix, from userid 1002) id 0A3949C58; Tue, 11 Mar 2003 21:57:53 -0500 (EST) Date: Tue, 11 Mar 2003 21:57:53 -0500 From: Mike Barcroft To: "Andrey A. Chernov" Cc: standards@FreeBSD.org Subject: Re: CFR: add widely accepted _ISOC99_SOURCE Message-ID: <20030311215753.G88290@espresso.bsdmike.org> References: <20030310061548.GA85361@nagual.pp.ru> <20030310104434.P70629@espresso.bsdmike.org> <20030311144501.GA364@nagual.pp.ru> <20030311104943.A88290@espresso.bsdmike.org> <20030311164240.GA2305@nagual.pp.ru> <20030311113754.C88290@espresso.bsdmike.org> <20030311175402.GA3885@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030311175402.GA3885@nagual.pp.ru>; from ache@nagual.pp.ru on Tue, Mar 11, 2003 at 08:54:02PM +0300 Organization: The FreeBSD Project Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Andrey A. Chernov writes: > 3) The question is: should we even support _ISOC99_SOURCE in its current > Linux form, i.e. as "turn C99 extensions on"? I don't think it's particularly useful, so I would say no. Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Wed Mar 12 1:17:31 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A2F8137B401 for ; Wed, 12 Mar 2003 01:17:29 -0800 (PST) Received: from perrin.int.nxad.com (internal.ext.nxad.com [69.1.70.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 354C443FDD for ; Wed, 12 Mar 2003 01:17:29 -0800 (PST) (envelope-from sean@perrin.int.nxad.com) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id E9EBD21079; Wed, 12 Mar 2003 01:16:58 -0800 (PST) Date: Wed, 12 Mar 2003 01:16:58 -0800 From: Sean Chittenden To: standards@FreeBSD.ORG Subject: environ.7 update (#include ?)... Message-ID: <20030312091658.GS79234@perrin.int.nxad.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="j6Ejlva3tMw3xXYi" Content-Disposition: inline User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0 83A6 DD99 E31F BC84 B341 X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --j6Ejlva3tMw3xXYi Content-Type: multipart/mixed; boundary="l+LxDeyHMCBjwres" Content-Disposition: inline --l+LxDeyHMCBjwres Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Simple question: should environ(7) be updated to include 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. -sc http://people.freebsd.org/~seanc/patches/#environ_include --=20 Sean Chittenden --l+LxDeyHMCBjwres Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch Index: share/man/man7/environ.7 =================================================================== RCS file: /home/ncvs/src/share/man/man7/environ.7,v retrieving revision 1.18 diff -u -r1.18 environ.7 --- share/man/man7/environ.7 7 Jun 2002 00:45:06 -0000 1.18 +++ share/man/man7/environ.7 12 Mar 2003 09:04:40 -0000 @@ -39,6 +39,8 @@ .Nm environ .Nd user environment .Sh SYNOPSIS +.In unistd.h +.Pp .Ar extern char **environ ; .Sh DESCRIPTION An array of strings called the --l+LxDeyHMCBjwres-- --j6Ejlva3tMw3xXYi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Comment: Sean Chittenden iD8DBQE+bvsK3ZnjH7yEs0ERApYxAJ99h6EK3KPHX0YjqePPZLXgW4ZrdACfQRR0 2gSyWnEe3faMtjNZVgAni+s= =FOQ8 -----END PGP SIGNATURE----- --j6Ejlva3tMw3xXYi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Wed Mar 12 3:42:48 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 23E6737B401; Wed, 12 Mar 2003 03:42:47 -0800 (PST) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8404043F3F; Wed, 12 Mar 2003 03:42:43 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id WAA18682; Wed, 12 Mar 2003 22:42:36 +1100 Date: Wed, 12 Mar 2003 22:42:35 +1100 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Sean Chittenden Cc: standards@FreeBSD.ORG Subject: Re: environ.7 update (#include ?)... In-Reply-To: <20030312091658.GS79234@perrin.int.nxad.com> Message-ID: <20030312222222.F29327@gamplex.bde.org> References: <20030312091658.GS79234@perrin.int.nxad.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, 12 Mar 2003, Sean Chittenden wrote: > Simple question: should environ(7) be updated to include 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 . 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 From owner-freebsd-standards Wed Mar 12 13:55:39 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C318937B405 for ; Wed, 12 Mar 2003 13:55:36 -0800 (PST) Received: from perrin.int.nxad.com (internal.ext.nxad.com [69.1.70.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A3F243FB1 for ; Wed, 12 Mar 2003 13:55:36 -0800 (PST) (envelope-from sean@perrin.int.nxad.com) Received: by perrin.int.nxad.com (Postfix, from userid 1001) id 1B41021075; Wed, 12 Mar 2003 13:55:04 -0800 (PST) Date: Wed, 12 Mar 2003 13:55:03 -0800 From: Sean Chittenden To: Bruce Evans Cc: standards@FreeBSD.ORG Subject: Re: environ.7 update (#include ?)... Message-ID: <20030312215503.GW79234@perrin.int.nxad.com> References: <20030312091658.GS79234@perrin.int.nxad.com> <20030312222222.F29327@gamplex.bde.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030312222222.F29327@gamplex.bde.org> User-Agent: Mutt/1.4i X-PGP-Key: finger seanc@FreeBSD.org X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0 83A6 DD99 E31F BC84 B341 X-Web-Homepage: http://sean.chittenden.org/ Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Simple question: should environ(7) be updated to include > > 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 . I know it's out of character to be in a section 7 page, but there's nothing prohibiting it. It's in stand.h and stand.h doesn't seem to be included by unistd.h (cpp unistd.h). From environ(7): DESCRIPTION An array of strings called the environment is made available by execve(2) when a process begins. execve(2) is made available via unistd.h. ::shrug:: -sc PS, Sorry I'm inclined to ask about adding something instead of letting the question fall into the abyss. Better to ask than let something fall through the cracks. -- Sean Chittenden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message From owner-freebsd-standards Fri Mar 14 10: 4: 6 2003 Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B10937B401 for ; Fri, 14 Mar 2003 10:04:05 -0800 (PST) Received: from pittgoth.com (14.zlnp1.xdsl.nauticom.net [209.195.149.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4EFEF43FB1 for ; Fri, 14 Mar 2003 10:04:04 -0800 (PST) (envelope-from trhodes@FreeBSD.org) Received: from mobile.pittgoth.com ([192.168.0.5]) by pittgoth.com (8.12.8/8.12.8) with SMTP id h2EI43V0042449 for ; Fri, 14 Mar 2003 13:04:03 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Fri, 14 Mar 2003 13:03:17 -0500 From: Tom Rhodes To: FreeBSD-standards@FreeBSD.org Subject: Can someone give me a hand? Message-Id: <20030314130317.324ee10d.trhodes@FreeBSD.org> X-Mailer: Sylpheed version 0.8.10claws (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-standards@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Greetings, Currently I'm involved with a small project to document the FreeBSD tunables, however the following tunables have no description that I've seen. I'd rather ask first, then hunt the mail archives. If anyone can give me a brief description of any tunables listed below I'll document them in the source so they display an output with sysctl -d. Thanks, -- Tom Rhodes p1003_1b.asynchronous_io: p1003_1b.mapped_files: p1003_1b.memlock: p1003_1b.memlock_range: p1003_1b.memory_protection: p1003_1b.message_passing: p1003_1b.prioritized_io: p1003_1b.priority_scheduling: p1003_1b.realtime_signals: p1003_1b.semaphores: p1003_1b.fsync: p1003_1b.shared_memory_objects: p1003_1b.synchronized_io: p1003_1b.timers: p1003_1b.aio_listio_max: p1003_1b.aio_max: p1003_1b.aio_prio_delta_max: p1003_1b.delaytimer_max: p1003_1b.mq_open_max: p1003_1b.pagesize: p1003_1b.rtsig_max: p1003_1b.sem_nsems_max: p1003_1b.sem_value_max: p1003_1b.sigqueue_max: p1003_1b.timer_max: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message