Instead of blaming ActiveState, it helps to actually know about the module you use and the operating system environment your script runs on. The Shell module runs commands through the "current operating system shell", which, on Windows machines nowadays is cmd.exe, which uses the forward slash ("/") as command switch indicator and not as path separator.
If you're afraid of using the well-tested modules to do file system operations from within Perl, most likely you will be able to use the backslash ("\\") as path separator on Windows machines. A far saner practice is to construct your file paths using the File::Spec module, that way you won't have to worry about the directory or file separators.
In reply to Re: ActivePERL is the devil?
by Corion
in thread ActivePERL is the devil?
by james734
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |