3 ms·
Windows supports forward-slash fine. Has for at least 25 years. No need to change / to \ or visa versa. Now obviously any Windows port would have to call Win32
by Someone1234 11y ago
Windows supports forward-slash fine. Has for at least 25 years. No need to change / to \ or visa versa.
Now obviously any Windows port would have to call Win32 APIs instead of POSIX APIs (unless you're writing for a Cygwin-like layer).
- tacos 11y agoYou might want to review the Xamarin bug reports as the slash alone nearly put them out of business at least three times.
- 2Xheadpalm 11y agoSupported, just but it's a second class citizen, for example, no tab completion of directories on the cmd prompt when using forward slash. Some commands will not except it; e.g. type c:\home\foo.txt -> cats it out type c:/home/foo.txt -> 'The syntax of this command is incorrect.' whereas cd will except either forward or backslash cd c:\home/foo cd c:/home/foo work as expected.
- pjmlp 11y agoJust use Powershell, it will work as expected.
- Someone1234 11y agoFirstly I was talking about API support. Since that is the topic at hand. Secondly, Cmd is deprecated. Powershell supports both slashes and "type c:/home/foo.txt" works perfectly.
- ktRolster 11y agoBut Powershell redirects < and > either don't work or can corrupt your files
- Someone1234 11y agoYou might find this useful: https://technet.microsoft.com/en-us/library/hh847746.aspx https://technet.microsoft.com/en-us/library/hh847746.aspx
- ktRolster 11y agoA) That's only one direction, the other way doesn't work B) Even going that direction, at times it corrupts the data