in reply to Re: / vs. \ in Win32 (Re: Glob on Win32: porting 5.005 to 5.6)
in thread Glob on Win32: porting 5.005 to 5.6

That was the type of thing I had tested before but testing it now shows command.exe not supporting it. It appears that I am correct that command.exe supports / as a directory path separator, it just doesn't always support it:

C:\>c:/temp/cleanpath.bat Cleaning user-specific PATH: ...

Using Microsoft software, I often boggle.

        - tye (but my friends call me "Tye")
  • Comment on (tye)Re: / vs. \ in Win32 (Re: Glob on Win32: porting 5.005 to 5.6)
  • Download Code

Replies are listed 'Best First'.
Re: (tye)Re: / vs. \ in Win32 (Re: Glob on Win32: porting 5.005 to 5.6)
by tachyon (Chancellor) on Sep 04, 2001 at 19:52 UTC

    My testing was on 95, you are probably using NT/ME/2000 I suspect?

    cheers

    tachyon

    s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

      Actually, I meant to be discussing cmd.exe not command.(exe|com) and so Win95 doesn't count (since it doesn't have cmd.exe). But your testing matched my testing on both WinNT and Win2K: "./test.bat" and "temp/test.bat" didn't work. But "c:/temp/test.bat" did. So even cmd.exe doesn't support / as well as it supports \, but it does support / as a directory path separator in some cases.

              - tye (but my friends call me "Tye")

        On 95 it is even weirder, using old faithful:

        C:\>c:\temp\test C:\>REM Hello tye! C:\>c:/temp/test C:\>

        No error but no run neither!

        cheers

        tachyon

        s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print