3 ms·
Any source for this? I see no reason why the same character can't be used in multiple places. Parser should parse the command line until it finds a command, the
by efreak 8y ago
Any source for this? I see no reason why the same character can't be used in multiple places. Parser should parse the command line until it finds a command, then send the rest of the line to it, regardless of content...
- macintux 8y agohttps://blogs.msdn.microsoft.com/larryosterman/2005/06/24/why-is-the-dos-path-character/ https://blogs.msdn.microsoft.com/larryosterman/2005/06/24/wh... Update: this link adds the tidbit that IBM was concerned about 3rd party utilities that made assumptions about the slash. https://www.howtogeek.com/181774/why-windows-uses-backslashes-and-everything-else-uses-forward-slashes/ https://www.howtogeek.com/181774/why-windows-uses-backslashe...
- ygra 8y agoParsing would be ambiguous, though, as the built-in commands don't require a space before its first argument. So things like copy/y foo bar were (and still are) valid. With directories they would either retain their original meaning, or refer to the y program inside of the copy folder.