A defect in the pathing routines

Chris Faylor cgf@cygnus.com
Wed May 24 12:32:00 GMT 2000

On Wed, May 24, 2000 at 11:47:33AM -0700, Earnie Boyd wrote:
>--- Chris Faylor <cgf@cygnus.com> wrote:
>> 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.
>I strongly disagree.  Cygwin has always made / and \ equal when
>referring to path names.  And, IMNSHO, it should continue to do so.

We have had a substantial number of customers who have been confused by
the fact that \foo does not necessarily refer to the foo directory of
the current drive.

Until I see a substantial number of complaints about the current
behavior I'm not going to think about changing it back.


More information about the Cygwin-developers mailing list