Date: Sun, 5 Jan 2003 20:37:31 -0800 From: "David O'Brien" <obrien@FreeBSD.org> To: Garrett Wollman <wollman@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/gen sysconf.c Message-ID: <20030106043730.GA24930@dragon.nuxi.com> In-Reply-To: <200209210214.g8L2E4Wc086892@freefall.freebsd.org> References: <200209210214.g8L2E4Wc086892@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 20, 2002 at 07:14:04PM -0700, Garrett Wollman wrote: > wollman 2002/09/20 19:14:04 PDT > > Modified files: > lib/libc/gen sysconf.c > Log: ... > Implement all of the keys from 1003.1-2001 that we can. Ensure that > the build will break if someone redefines an option constant to zero > without implementing the necessary presence-detection logic here. Would you *PLEASE* keep the manpage in sync when you make changes like this? I added 'LOGIN_NAME_MAX' to syslimits.h as the manpage totally didn't mention it. On a related note, why should 'LOGIN_NAME_MAX' be a run-time value? One of the most common use of it is "char foo[LOGIN_NAME_MAX];". Calling sysconf(3) in this context will not work. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030106043730.GA24930>