Uh... "Except"? What does that observation have to do with anything? It was a gentle reminder that reaching for backslash is not necessary. Nowhere does it say "you can paste the same absolute path in on any system, without regard for where the files actually live".
> What does that observation have to do with anything?
About as much as the comment I replied to did, I suppose.
Since the paths were right as originally written, and since changing from backslash to forward slash doesn't remove the need to list both paths anyway, bringing up the other ways of writing the windows path seemed unnecessary.
But I was feeling charitable and thought that perhaps you read the original comment too quickly and assumed that the paths were the same except for the slash direction, which would give your comment a little more purpose, and which also gives my reply a little purpose as well.
If that wasn't the case then neither post has any purpose.
Making assumptions about the other person that set you up to argue against whatever position that entails is not what it means to be charitable. It is the opposite. It is uncharitable. (At least to the other person; it's charitable, perhaps, to you.)
> neither post has any purpose
Wrong. It has the same purpose now as it did from the beginning—reminding/alerting people to the fact that using backslashes in paths just because you're talking about Windows is not necessary.
Using one of the correct path separators for the OS isn't necessary? And someone using one of the correct path separators needs a reminder that other path separtors exist?
There was no more purpose to that than reminding someone that they could have used UNC paths, URIs, 8.3 short names, ...
> Using one of the correct path separators for the OS isn't necessary?
Using backslash specifically is unnecessary.
There's no point wasting more time here from this point onward. You either refuse to understand, or you understand and refuse to show it. It's not productive to believe that's not going to change.
