Re: Died on open command

[Chuck Fox]

[EMAIL PROTECTED] wrote:

It has nothing to do with what ActiveState did or didn't do.  The
DOS/Windows command interpreter (command.com/cmd.exe) uses '\' as the
path separator however the operating system itself is able to use '/' as
the path separator.
   

Sorry, I just tried it on my machine here (NT4), and doing

cd winnt/system32

from the C: directory gets me into the C:\winnt directory, whereas doing 

cd winnt\system32

gets me into the C:\winnt\system32 directory, as it should. I tried it
before I sent the mail.
Now perhaps the cmd.exe for Win2000 and up does what you describe. But since
opening a file with slashes in its path works in perl even on my machine,
where using slashes at the prompt doesn't work, I would say ActiveState had
something to do with it. Perhaps they just ironed out some of the
differences between the versions of cmd.exe...
Anyways, it's irrelevant, it works, so let's just use it, regardless of
who's to blame (err, thank).
J-S

_____________________________________________________
Jean-Sébastien Guay
-- Conseiller technique - Administration
-- (514) 522-9800 #4840
-- [EMAIL PROTECTED]
 

Just tried on my WindowsXP box.  I had to enclose the path in double 
quotes.  But once I did that, Windows did the right thing,

dir "\temp"
dir "/temp"
both give me the temp directory listing.  Using single quotes or 
backticks does not work.

Chuck