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 Message-ID: <20000524184733.22633.qmail@web106.yahoomail.com> Date: Wed, 24 May 2000 11:47:33 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: A defect in the pathing routines To: cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- 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. Cheers, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/