This is the mail archive of the
mailing list for the Cygwin project.
RE: BUG: Ability to access nonexistent directories
- From: Fedin Pavel <p dot fedin at samsung dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 20 May 2013 15:53:16 +0400
- Subject: RE: BUG: Ability to access nonexistent directories
- References: <000201ce52c4$891b04c0$9b510e40$%fedin at samsung dot com> <20130517083612 dot GE21752 at calimero dot vinschen dot de> <000d01ce52dc$74e54bb0$5eafe310$%fedin at samsung dot com> <20130517102655 dot GG21752 at calimero dot vinschen dot de> <20130517145612 dot GC7087 at ednor dot casa dot cgf dot cx>
> >> Heh...
> >> So, complete emulation would cost a major performance drop, right ?
> >> Well... Can there be any setting which enables these checks ? At
> least we have one use case...
> >Not without lots of new code.
> So, maybe next Thursday?
By the way, you said it would be slow... I have an idea how to implement a
compromise solution which would not be horribly slow.
What if we check existence of intermediate paths not every time but only
when we meet thing like '..' ?
I'll explain... For example, if we would access /foo/bar/baz, testing for
/foo and /foo/bar existence would supposedly be a waste of time, because we
would get "Object not found" on the final path too. But, when processing
thing like /foo/bar/../baz, we really need to check for intermediate dirs.
But, still not every time. In this example we actually need to test only for
/foo/bar's existence. I. e. a path to which we apply '..', before stripping
the last component.
Does it make sense ?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple