This is the mail archive of the
mailing list for the Cygwin project.
Re: Patch for path.cc
- To: "'cygwin at sourceware dot cygnus dot com'" <cygwin at sourceware dot cygnus dot com>
- Subject: Re: Patch for path.cc
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Fri, 9 Jun 2000 11:53:18 -0400
- References: <1DB8BA4BAC88D3118B2300508B5A552CD92599@mail.fitlinxx.com>
- Reply-To: cygwin at sourceware dot cygnus dot com
On Fri, Jun 09, 2000 at 11:38:30AM -0400, David Bolen wrote:
>Chris Faylor [email@example.com] writes:
>> Since we've recently made the change to cygwin to consider the
>> existence of a '\' as a Windows path, we are not going to be
>> applying this patch. Sorry.
>Is this a hard decision forever or just the near term? From my perspective,
>I think this would be a good enhancement to the current behavior. You don't
>lose the Windows path processing in what I expect is the target case (that
>of actually being handed a Windows path using \), and you work better with
>those of us using Unix-like paths but sometimes getting automated/system
>additions which result in the occasional \. In that vein it also lessens
>the potential deviation from earlier releases of the DLL.
>I'm not sure I see a downside (or a weakening of the intended Windows
>handling behavior) with this patch - is there something subtle I'm missing?
We have flushed out a few cases where there was incorrect path manipulation
with the recent change to cygwin. There is no way that a UNIX program should
be mixing '\' and '/' but it does happen in tcl and in some places in libiberty.
This is usually an indication of something being broken that is being masked
by cygwin and I am sure that these kinds of things are responsible for the
occasional random reports that we see from people who are unable to open files.
I will take this up with the cygwin-developers mailing list but I don't see
any reason to change this behavior in the near term.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org