Re: Absolute file-path under bash (cygwin32)

[Scott Blachowicz <scott at apple dot statsci dot com>]

Hawkeye <hawkeye@tcp.com> wrote:

> o "/" already separates path components in unix names, and is illegal
>   in path components in dos names, so cygwin could always interpret it
>   as a separator.

But, some tools will take forward slashes as directory separators (e.g. I
think I've given something like "-I \\system\share/include" options to the MS
C compiler before [my memory might be a bit foggy here, but I've used "/" as
separators for constructing paths in GNU makefiles and run MS C from them
before).

> o Interpreting "\" is a little more tricky.  Maybe cygwin should interpret
>   "\" as a separator only if the name does not contain any "/"s.  Or maybe
>   it could always interpret "\" as a separator, with the assumption that
>   nobody in their right mind uses "\" in a unix file name.... Say, doesn't
>   cygwin already disallow "\" in file names?  In that case, it can always
>   interpret "\" as a separator, without losing anything.

Yeah...by the time the string gets to a file path manipulation function, why
not just treat both "/" and "\" as being equivalent separators?

But, didn't I already see a message in here that b18 will fully support DOS
paths?

Scott Blachowicz  Ph: 206/283-8802x240   Mathsoft (Data Analysis Products Div)
                                         1700 Westlake Ave N #500
scott@statsci.com                        Seattle, WA USA   98109
Scott.Blachowicz@seaslug.org
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".