Date: Thu, 16 Jan 2003 07:49:13 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
cc: djgpp-workers AT delorie DOT com
Subject: Re: fstat, fd_props and inventing inodes [PATCH]
In-Reply-To: <3E2578A6.B4FEFEF5@phekda.freeserve.co.uk>
Message-ID: <Pine.SUN.3.91.1030116074638.24436A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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


On Wed, 15 Jan 2003, Richard Dawe wrote:

> > Also, if you run _fixpath on a file name in a place other than where
> > the file is actually opened, the program might be in a different
> > directory, so _fixpath will produce incorrect results.
> 
> If the file name is relative, for example? (I think this is what you mean.)

Yes, that's what I meant.  Sorry for not making it clear.

> Or do you mean something with levels of indirection, like SUBST'd drives?

Maybe that as well, I didn't think about it.  The principle is that 
_fixpath should be called when the file is opened, since that's the only 
place we are sure that all these resolutions produce the correct result.