Re^5: Program Not Found when run from browser page

Yeah, it's true, you don't need to double the backslash if they are enclosed in single quotes or q(), however if the backslash happens to be the last character in the string, then it must be double. So, it's just easier to remember to always double it.

Incorrect: 'C:\Windows\'

Correct: 'C:\Windows\\'

Incorrect: q(C:\Windows\)

Correct: q(C:\Windows\\)

This is easier to rememeber: 'C:\\Windows\\' or "C:\\Windows\\"

Comment on Re^5: Program Not Found when run from browser page

Replies are listed 'Best First'.
Re^6: Program Not Found when run from browser page by soonix (Chancellor) on Nov 14, 2024 at 09:00 UTC
It is worth mentioning that most Windows programs (nearly all, with the notable exception of CMD.EXE and Explorer.exe) do understand forward slashes as "path separator". So, for most system functions outside of Batch "Scripts", you can use `"C:/Windows/"`. If in doubt, use e.g. catfile/catdir of File::Spec or canonpath of Path::Tiny. Update: in Stackexchange's "Retrocomputing" section someone writes the following, which coincides with my experience: All dedicated path names, like in syscalls, can be written with either slash. It's only within the command line scan of each command, that simple slashes get interpreted as switch indicators.	[reply] [d/l]

Replies are listed 'Best First'.

Re^6: Program Not Found when run from browser page
by soonix (Chancellor) on Nov 14, 2024 at 09:00 UTC

most

So, for most system functions outside of Batch "Scripts", you can use "C:/Windows/".

catdir of File::Spec

canonpath of Path::Tiny

Update: in Stackexchange's "Retrocomputing" section someone writes the following, which coincides with my experience:

All dedicated path names, like in syscalls, can be written with either slash. It's only within the command line scan of each command, that simple slashes get interpreted as switch indicators.

[reply]
[d/l]