2 ms·
Another difference from Unix is that Windows does not always normalize multiple consecutive backslashes or slashes to a single one. A path like "foo\\bar" (or "
by layer8 5y ago
Another difference from Unix is that Windows does not always normalize multiple consecutive backslashes or slashes to a single one. A path like "foo\\bar" (or "foo//bar") gets you "The file name is not valid" in File Open dialogs, for example.
- deleted 5y ago[deleted]
- tssva 5y agoThis isn't completely accurate. The Windows file dialog will not but the Win32 api does. Specifying a path such as foo\\bar in the shell for example will work. The exception is if the multiple slashes appear at the beginning of the path. Windows accepts UNC paths which begin with double slashes. It will not normalize multiple slashes into double slashes at the beginning of a path but any following multiple slashes will be normalized to a single slash.