This is the mail archive of the
cygwin-developers@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: A defect in the pathing routines
- To: cygwin developers <cygwin-developers at sourceware dot cygnus dot com>
- Subject: Re: A defect in the pathing routines
- From: Chris Faylor <cgf at cygnus dot com>
- Date: Wed, 24 May 2000 14:24:40 -0400
- References: <20000524170512.3693.qmail@web121.yahoomail.com>
- Reply-To: cygwin-developers at sourceware dot cygnus dot com
On Wed, May 24, 2000 at 10:05:12AM -0700, Earnie Boyd wrote:
>I've a small program which shows a problem in the pathing routines.
>First, the problem starts because path.cc assumes that any string
>containing a \ is a win32 path. And if it begins with \ it assumes an
>absolute win32 path. IMO, this is wrong. In the past cygwin supported
>the backslash for the cygwin path as well. I think it still should.
As I've previously stated, the change was made some time ago to make
cygwin ignore the mount table when it sees a Windows path. This is so
that people will not be confused when they specify Windows paths. Since
the use of a backslash has no meaning on UNIX I don't see this as
a terrible thing.
That means that /tmp is not necessarily equal to \tmp.
cgf