Re:Why Does Windows Really Use Backslash as Path Separator?
by drfuchs on Friday May 24, 2019 @04:50PM
(#20005165)
I always thought it was so that file names could have dates in them: BUDGET_09/12/1982.XSL
[ Parent
| on HN ]
Re:Why Does Windows Really Use Backslash as Path Separator?
by gothroach on Friday May 24, 2019 @04:52PM
(#20005191)
I don't recall a time when you could use / in Windows file or directory names.
Re:Why Does Windows Really Use Backslash as Path Separator?
by jolmg on Friday May 24, 2019 @05:01PM
(#20005262)
So Windows forbids other characters in names besides the directory separator?
EDIT: Apparently:
https://stackoverflow.com/questions/1976007/what-characters-...
Re:Why Does Windows Really Use Backslash as Path Separator?
by jonhohle on Friday May 24, 2019 @06:14PM
(#20005763)
IIRC, different APIs in Windows handle special characters for filenames differently.
This was probably around the Windows 98 timeframe, but I remember several instances when extracting zips (probably WAREZ) where the file that was written contained characters that Explorer couldn't handle correctly. It wouldn't allow moving those files to the Recycling Bin, but would typically allow renaming the portion before the extension. I had a collection of `zzzz.???` files for a long time.
Re:Why Does Windows Really Use Backslash as Path Separator?
by Sharlin on Friday May 24, 2019 @07:39PM
(#20006196)
17-character file name, what madness is that? At best you could do BUDG0912.XSL or BU091282.XSL or something.
Re:Why Does Windows Really Use Backslash as Path Separator?
by ncmncm on Friday May 24, 2019 @10:37PM
(#20006775)
We're talking about MacOS now.
It was really common back then to put dates in file names, and names could be 32 characters long. Furthermore, you didn't need an extension because every file had a separate 4-byte (binary, but usually ASCII anyway) type.