From owner-cvs-all  Thu Jan 16  2:30:37 2003
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id E5E3337B401; Thu, 16 Jan 2003 02:30:35 -0800 (PST)
Received: from espresso.q9media.com (espresso.q9media.com [65.39.129.122])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 5985343F1E; Thu, 16 Jan 2003 02:30:35 -0800 (PST)
	(envelope-from mike@espresso.q9media.com)
Received: by espresso.q9media.com (Postfix, from userid 1002)
	id 56AE49C10; Thu, 16 Jan 2003 05:19:16 -0500 (EST)
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>
References: <200301152122.h0FLMtdE034299@repoman.freebsd.org> <20030115183943.D58850@espresso.q9media.com> <20030116.005708.96919189.imp@bsdimp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030116.005708.96919189.imp@bsdimp.com>; from imp@bsdimp.com on Thu, Jan 16, 2003 at 12:57:08AM -0700
Organization: The FreeBSD Project
Sender: owner-cvs-all@FreeBSD.ORG
Precedence: bulk
List-ID: <cvs-all.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20cvs-all>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20cvs-all>
X-Loop: FreeBSD.ORG

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