Mail Archives: cygwin/2000/05/28/03:17:51
rmcgowan AT veritas DOT com [rmcgowan AT veritas DOT com] writes:
> The problem, as I understand it, was found when someone tried to do a make
and
> had errors, which were traced back to path names having two leading
slashes,
> which were then being interpreted as UNC paths. But these were really
local
> path names, created because there was a variable with the value "/" which
was
> prepending to another value that began with a slash, resulting in names
with
> two leading slashes. UNIX system handle this gracefully in some way,
making
> the "//" act like a single slash.
As I believe Chris mentioned in one of the earlier responses, an important
point is that in general it's only safe to assume Unix systems will treat
"//" as "/" if it occurs in the middle of a path specification, not at the
front (which can be treated in a system-specific manner). I don't believe
that
all Unix systems handle such names similarly, nor automatically make them
act
like a single slash.
So at the Cygwin DLL level, I'd rather leave the behavior as is - a
convenient
system-defined manner of handling "//" to map to a useful Windows UNC
notation,
without requiring shell quoting.
-- David
/-----------------------------------------------------------------------\
\ David Bolen \ E-mail: db3l AT fitlinxx DOT com /
| FitLinxx, Inc. \ Phone: (203) 708-5192 |
/ 860 Canal Street, Stamford, CT 06902 \ Fax: (203) 316-5150 \
\-----------------------------------------------------------------------/
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
- Raw text -