Date: Sat, 21 Sep 2002 11:58:38 +0300
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: "Mark E." <snowball3 AT softhome DOT net>
Message-Id: <4098-Sat21Sep2002115837+0300-eliz@is.elta.co.il>
X-Mailer: emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
CC: djgpp-workers AT delorie DOT com
In-reply-to: <3D8B92AB.7174.567AAC@localhost> (snowball3@softhome.net)
Subject: Re: working toward a realpath implementation
References:  <3D8B92AB DOT 7174 DOT 567AAC AT localhost>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> From: "Mark E." <snowball3 AT softhome DOT net>
> Date: Fri, 20 Sep 2002 21:27:07 -0400
> 
> An implementation of realpath would certainly help in the posix compliance 
> department.

Thanks for working on this.

> To help attain a compliant version, I've made some changes to 
> fixpath.c to make implementing realpath easier. For example, I changed 
> FILENAME_MAX to PATH_MAX.

Could you please explain how does this make realpath implementation
easier?  Enlarging the max size has a minor disadvantage: we don't
detect file names beyond 260 characters that Windows 9X filesystems
cannot handle.  So I'd like to understand the advantages before we
make the decision whether the risk is justified.

Also, if _fixpath can now set errno, perhaps we should document that
in _fixpath.txh.

Otherwise, I don't have any objections to this patch.