Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Wed, 24 May 2000 15:32:22 -0400 To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: A defect in the pathing routines Message-ID: <20000524153222.B5043@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com References: <20000524184733 DOT 22633 DOT qmail AT web106 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000524184733.22633.qmail@web106.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, May 24, 2000 at 11:47:33AM -0700 On Wed, May 24, 2000 at 11:47:33AM -0700, Earnie Boyd wrote: >--- Chris Faylor 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. cgf