Date: Thu, 01 Mar 2001 14:30:50 -0700 From: Warner Losh <imp@harmony.village.org> To: "Jacques A. Vidrine" <n@nectar.com> Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/usr.bin/make arch.c main.c Message-ID: <200103012130.f21LUod51285@harmony.village.org> In-Reply-To: Your message of "Thu, 01 Mar 2001 15:05:04 CST." <20010301150504.A20983@hamlet.nectar.com> References: <20010301150504.A20983@hamlet.nectar.com> <200103011743.MAA01724@khavrinen.lcs.mit.edu> <200103010603.f2163IM00616@freefall.freebsd.org> <200103011743.MAA01724@khavrinen.lcs.mit.edu> <200103011817.f21IHZd50132@harmony.village.org> <20010301145142.A20573@hamlet.nectar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20010301150504.A20983@hamlet.nectar.com> "Jacques A. Vidrine" writes:
: I think this is SUSv2 bug. Stevens writes in 1993 that PATH_MAX does
: not include room for a null character, and his program fragments in
: APUE consistently use PATH_MAX + 1.
Garrett quoted an addendum to the standard that says id *DOES* include
the trailing NUL. But he didn't post it to the list:
{PATH_MAX}
IEEE PASC Interpretation 1003.1 #15 addressed the
inconsistency in the standard with the definition of path name
and the description of {PATH_MAX}, allowing application
writers to allocate either {PATH_MAX} or {PATH_MAX}+1
bytes. The inconsistency has been removed by correction to the
{PATH_MAX} definition to include the null character. With this
change, applications that previously allocated {PATH_MAX}
bytes will continue to succeed.
Warner
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?200103012130.f21LUod51285>