Date: Thu, 16 Jan 2003 05:19:16 -0500 From: Mike Barcroft <mike@FreeBSD.org> To: "M. Warner Losh" <imp@bsdimp.com> Cc: johan@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/stdlib realpath.3 realpath.c src/bin/realpath realpath.c Message-ID: <20030116051916.E58850@espresso.q9media.com> In-Reply-To: <20030116.005708.96919189.imp@bsdimp.com>; from imp@bsdimp.com on Thu, Jan 16, 2003 at 12:57:08AM -0700 References: <200301152122.h0FLMtdE034299@repoman.freebsd.org> <20030115183943.D58850@espresso.q9media.com> <20030116.005708.96919189.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
M. Warner Losh <imp@bsdimp.com> writes: > In message: <20030115183943.D58850@espresso.q9media.com> > Mike Barcroft <mike@FreeBSD.org> writes: > : Hmm, I thought it was more complicated than this. IIRC, PATH_MAX > : isn't necessarily available at compile-time, so it needs more > : complications to conform to POSIX in the case where PATH_MAX isn't > : defined. Portablility might not be important, in which case it > : isn't clear why we would change from MAXPATHLEN to PATH_MAX or vice > : versa. > > I made this change because PATH_MAX is more posixly correct than > MAXPATHLEN and has a better definition. It only handles the case > where PATH_MAX is a compile time constant, or when you are using gcc > extensions that allow one to allocate memory on the fly. Fair enough. Best regards, Mike Barcroft 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?20030116051916.E58850>