Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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).



Supported, 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.


Firstly 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.


But Powershell redirects < and > either don't work or can corrupt your files



A) That's only one direction, the other way doesn't work

B) Even going that direction, at times it corrupts the data


Just use Powershell, it will work as expected.


You might want to review the Xamarin bug reports as the slash alone nearly put them out of business at least three times.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: