Re^2: perl windows backtick problem

I ran some quick tests...

All you've demonstrated is that the cmd.exe built-in command "dir" uses / for processing arguments, as documented

$ "C:/MinGW/msys/1.0/bin/dir.EXE" asdf
"C:/MinGW/msys/1.0/bin/dir.EXE": asdf: No such file or directory

$ "C:\MinGW/msys/1.0/bin\dir.EXE" asdf
"C:/MinGW/msys/1.0/bin/dir.EXE": asdf: No such file or directory

$ C:\MinGW/msys/1.0/bin\dir.EXE asdf
/usr/bin/dir: asdf: No such file or directory

$ C:\MinGW/msys/1.0/bin\dir.EXE\$HOME asdf
The directory name is invalid.

$ C:\MinGW/msys/1.0/bin\dir.EXE\blah.exe
The directory name is invalid.
[download]

This 8.3 naming stuff is "bad juju".

Yup, that is why there is NtfsDisable8dot3NameCreation, but it does have benefits

8.3 saves you the trouble of quoting paths in the shell, say for batch files and the like

8.3 spares you the headache of dealing with broken programs that don't quote paths they give to the shell, like legacy applications

8.3 spares you the headache of dealing with broken programs that split on whitespace

Comment on Re^2: perl windows backtick problem Download Code

Replies are listed 'Best First'.
Re^3: perl windows backtick problem by Marshall (Canon) on Sep 22, 2011 at 00:12 UTC
But the BIG disadvantage is that there is no 1->1 mapping between the NTFS name and the 8.3 name! It is not possible to uniquely map a 32 character name into an 8 character name! ABCDEFGHIJ.EXE will have a different 8.3 name on different systems depending upon what other files are in the directory. Let's see what the OP (original poster) has to say. I am curious as to the application...	[reply]
Re^4: perl windows backtick problem by Anonymous Monk on Sep 22, 2011 at 07:52 UTC
But the BIG disadvantage is that there is no HA! 8.3 is a feature to support legacy applications developed for legacy filesystem It was never supposed to be a 1-to-1-mapping or relocatable between systems, that is impossible problem	[reply]