News for hackers. Stuff that matters.

A comment on Why Does Windows Really Use Backslash as Path Separator?. Parent comment

Re:Why Does Windows Really Use Backslash as Path Separator? by kazinator on Friday May 24, 2019 @05:46PM (#20005565)
Every Microsoft operating system going back to early versions of MS-DOS can use / as the separator.

This is not necessarily true of the "user space" of Microsoft systems. Paths are not only traversed by the "kernel", but also manipulated by applications like the Explorer shell, which may or may not like forward slashes.

[ Parent | on HN ]
Re:Why Does Windows Really Use Backslash as Path Separator? by mortehu on Friday May 24, 2019 @11:28PM (#20006934)
It's partially the opposite. Some system calls only accept backlash, but user space programs and libraries may abstract this. E.g. LoadLibrary, which is similar to execve/dlopen.
[ Parent | on HN ]
Re:Why Does Windows Really Use Backslash as Path Separator? by ChrisSD on Friday May 24, 2019 @06:04PM (#20005693)
As I recall at least some parts of the WinAPI had trouble if you used long paths (via "\\?\") and forward slash. I don't know if that's still true.
[ Parent | on HN ]
Re:Why Does Windows Really Use Backslash as Path Separator? by kazinator on Friday May 24, 2019 @06:08PM (#20005722)
Indeed. "Windows API" is very broad; it encompasses all sorts of user-space middleware, some of which could very plausibly munge paths in ignorance of forward slashes.
[ Parent | on HN ]