Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <39459448.1C0B87AD@carlthompson.net> Date: Mon, 12 Jun 2000 18:54:16 -0700 From: Carl Thompson X-Mailer: Mozilla 4.73 [en] (X11; U; Linux 2.2.14-5.0 i686) MIME-Version: 1.0 To: John Paulson Cc: Cygwin List Subject: Re: Patch for path.cc & environ.cc References: <4 DOT 2 DOT 2 DOT 20000612181028 DOT 00b48990 AT mailhost> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit John Paulson wrote: > ... > I _can't_ be the only user of cygwin running into the problem of > mixed directory separators in pathnames. And in the position that > remedying the source of mixed slashes is way more difficult than > modifying cygwin. If I am understanding you, there must be lots of software that suffers from the same problem. Think of all that Unix code that does something like this: char datafile[MAXPATHLEN] = ""; const char* home = getenv("HOME"); if (home) strncpy(datafile, home, sizeof(datafile)); strncat(datafile, "/.GnomoVision/config", sizeof(datafile)); [ Do something with filename ] If I understand correctly, wouldn't this run afoul of the problem if the "HOME" environment variable were something like "C:\My Documents" ? Or am I not getting it? > ... > John Paulson Carl Thompson -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com