If you use the scalar args form of system

...
system( "command \\path\\with spaces\\file" );
...
[download]

you'll may have problems with the spaces.

If you use the list form of the system function.

...
system( '\path\to\command.exe', '\path\with spaces\file' );
...
[download]

Note the use of 's rather than "s, to avoid the need to escape the backslashes.

cmd.exe will be bypassed and the spaces in the filename won't cause a problem. However, you will need to specify the full path of the command as well.

You can also avoid the need for using short filenames by quoting the filepath.

...
system( q[command "\path\with spaces\file" ] );
...
[download]

Which allows the shell to resolve the location of the command for you and forces it to see the quoted path as a single argument.

Note though, if your in an open environment, the risk entailed in allowing your shell to do this for you.

1) Use of single quotes: This is not possible, as I am generating the path at runtime based on some env vars and I think use of single-quotes would not expand the variables inside it.

2) I am not quite comfortable using 'command', because its like relying too much on a system file's existence (for example, lets say, MS decides to change the command.com's name, though very rare it maybe. I am very reluctant to use of such tied code, unless there is some pressing need). A function like 'system' is rather more guaranteed to not change over time or gets itself (functionality) modified in versions to come, if need be.

Anyhow, thanks for the pointers!

-sureshr