Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E4830C4.6AD557DB@phekda.freeserve.co.uk>
Date: Mon, 10 Feb 2003 23:07:48 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: Take on __solve_symlinks()
References: <10302091811 DOT AA17131 AT clio DOT rice DOT edu> <3E483065 DOT 3000208 AT mif DOT vu DOT lt>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Laurynas Biveinis wrote:
> 
> Charles Sandmann wrote:
> > 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.
> 
> Thanks a lot. I guess this acquits __solve_symlinks of Rick's concerns,
> doesn't it?

No, not really. It still doesn't work for the cases where ".."s go above the
root directory. So either findfirst (& findnext, I guess) or __solve_symlinks
needs to be fixed. But does the fix belong in findfirst or __solve_symlinks?

We could "fix" findfirst & findnext to cope with excess ".."s on DOS.

> Rick, are there any other bugs left in __solve_symlinks?

No, I don't think so.

Thanks, bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]