From:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<10302091811.AA17131@clio.rice.edu>
Subject:	Re: Take on __solve_symlinks()
To:	djgpp-workers AT delorie DOT com
Date:	Sun, 9 Feb 2003 12:11:09 -0600 (CST)
In-Reply-To:	<3E463619.C47BF1F3@phekda.freeserve.co.uk> from "Richard Dawe" at Feb 09, 2003 11:06:01 AM
X-Mailer:	ELM [version 2.5 PL2]
Mime-Version:	1.0
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

> Have you tried running the small findfirst test program that I posted? I think
> the difference in behaviour may be down to findfirst.

I just hunted it down (search for ./fftest.exe) - your example was:

> bash-2.04$ ./fftest.exe ../../../autoexec.bat
> ../../../autoexec.bat -> ../../../autoexec.bat
> ../../../autoexec.bat: matched
> bash-2.04$ ./fftest.exe ../../../../autoexec.bat
> ../../../../autoexec.bat -> ../../../../autoexec.bat
> ../../../../autoexec.bat: unmatched

I confirm different behavior on Win2K and Win98.  (On Win2K the second
example above will match).

Excess ../../.. will find files in the root directory on Win2K (such
as autoexec.bat) but will fail (unmatched) on Win98.  Win2K seems to
emulate a unixy type behavior of .. in root pointing to root - while
Win98 does not.

- Raw text -