On Mon, Aug 22, 2005 at 06:42:36AM -0700, Brian Dessent wrote:
>Corinna Vinschen wrote:
>>I don't agree with you that /../ components are actually seldom in path
>>expressions. If you examine typical source trees, you'll find that
>>expressions as -I../../foo/bar or -L/path/to/bin/../lib are used
On Mon, Aug 22, 2005 at 06:40:54AM -0600, Eric Blake wrote:
>How often does the substring /../ actually appear in path name
>resolution?
You're asking questions and arguing without actually looking at the
source code. It doesn't only matter how often something like this
happens. It also matters
Corinna Vinschen wrote:
> I don't agree with you that /../ components are actually seldom in path
> expressions. If you examine typical source trees, you'll find that
> expressions as -I../../foo/bar or -L/path/to/bin/../lib are used quite
> often.
Indeed. Even just "gcc hello.c" has to wade th
On Aug 22 06:40, Eric Blake wrote:
> How often does the substring /../ actually appear in path name resolution?
> I don't think it is all that often, and the penalty for getting that
> corner case POSIXly correct need not affect the common case when /../ is
> not part of the path name. Besides, t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Christopher Faylor on 8/21/2005 9:17 PM:
> I really don't care about POSIX in this case because I don't care about
> slavish adherence to POSIX standards at the expense of decreasing cygwin
> performance, adding a lot of complexity, or rem
Eric Blake wrote:
Cygwin will accept the path "dir/../file" as being the same as "file",
regardless of whether "dir" exists. Apprently, someone decided that a
simple path-trimming rule would speed things up, but it is wrong. For
example, it breaks building of xedit/lisp, where "lisp/../xedit.h"
On Sun, Aug 21, 2005 at 09:58:40PM -0500, Gary R. Van Sickle wrote:
>Cgf wrote:
>
>[snip]
>
>> I think it's a pretty hard problem and I really don't care
>> about POSIX
>
>??? This must be a typo, or you wouldn't be here.
You're right. It wasn't a typo but it was too strongly stated. I
really
Cgf wrote:
[snip]
> I think it's a pretty hard problem and I really don't care
> about POSIX
??? This must be a typo, or you wouldn't be here.
--
Gary R. Van Sickle
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Do
On Sun, Aug 21, 2005 at 10:31:47PM +, Eric Blake wrote:
>>Cygwin will accept the path "dir/../file" as being the same as "file",
>>regardless of whether "dir" exists. Apprently, someone decided that a
>>simple path-trimming rule would speed things up, but it is wrong. For
>>example, it breaks
> Cygwin will accept the path "dir/../file" as being the same as "file",
> regardless of whether "dir" exists. Apprently, someone decided that a
> simple path-trimming rule would speed things up, but it is wrong. For
> example, it breaks building of xedit/lisp, where "lisp/../xedit.h" is
> not
10 matches
Mail list logo
