In a Perl script, what would cause double backslashes not to be interpreted correctly?

  • Thread starter Thread starter Menotti M
  • Start date Start date
M

Menotti M

Guest
I have a Perl script that is doing the following:

open(DIR, "dir /b $dir\*$file* | ");

Now, nothing has changed, and in the past, this would issue the following to the windows command line (after interpretation):

dir /b directory\*file* |

But now, when the automated script runs, it seems that the double slashes are doing right into the command line. Output looks like:

dir: cannot access e\:\directory\directory2\directory3\*file123*: No such file or directory

Any idea why the interpretation would just start failing, even though the script hasn't changed for months?

Thanks
 
Back
Top