From owner-cvs-all Thu Mar 1 11:49:20 2001 Delivered-To: cvs-all@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 28C1037B719; Thu, 1 Mar 2001 11:49:14 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA03017; Thu, 1 Mar 2001 14:48:57 -0500 (EST) (envelope-from wollman) Date: Thu, 1 Mar 2001 14:48:57 -0500 (EST) From: Garrett Wollman Message-Id: <200103011948.OAA03017@khavrinen.lcs.mit.edu> To: Brian Somers Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/calendar io.c In-Reply-To: <200103011458.f21Ewrx02627@hak.lan.Awfulhak.org> References: <200103010547.f215lUw98788@freefall.freebsd.org> <200103011458.f21Ewrx02627@hak.lan.Awfulhak.org> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Does anybody (Garrett, Bruce?) know definitively which of the various > *LEN variables include NUL ? No. That's why they should not be used. Use the POSIX-standard *_MAX variables instead. > MAXHOSTNAMELEN: Hopefully this one will be in the next POSIX. The current draft spells it `255'. I have proposed {HOST_NAME_MAX} which would definitively include the terminating '\0'. > MAXNAMELEN: > intro(2) suggests that this doesn't include space for a NUL - seems > right. Use {NAME_MAX}. > MAXPATHLEN > intro(2) suggests that this does include space for a NUL - seems right. Use {PATH_MAX}. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message