Free Republic
Browse · Search
General/Chat
Topics · Post Article

To: cynwoody
The original sin was using backslash as the directory separator. The backslash already had a perfectly valid use: to escape special characters. To appropriate it for use as the directory separator was unacceptable.

It could just as easily be argued that the forward slash already had a perfectly valid use as a division operator and appropriating it for use as a directory separator was unacceptable.

69 posted on 07/22/2015 3:32:10 AM PDT by tacticalogic
[ Post Reply | Private Reply | To 66 | View Replies ]


To: tacticalogic
It could just as easily be argued that the forward slash already had a perfectly valid use as a division operator and appropriating it for use as a directory separator was unacceptable.

In practice, using the escape operator as the separator causes a lot more problems. That's because you use the escape operator when specifying literal strings, whereas the forward slash as the division operator never conflicts with the forward slash as the path separator.

It's interesting that in its internal APIs, Windows is perfectly happy to accept either slash as the separator. It's only at the command line level that you have to use back-slash. That's because they chose the division operator as the command line option delimiter, instead of the subtract operator, which is what Unix uses.

72 posted on 07/22/2015 2:09:09 PM PDT by cynwoody
[ Post Reply | Private Reply | To 69 | View Replies ]

Free Republic
Browse · Search
General/Chat
Topics · Post Article


FreeRepublic, LLC, PO BOX 9771, FRESNO, CA 93794
FreeRepublic.com is powered by software copyright 2000-2008 John Robinson