It's so trivial to replace fronts <-> backs that no one bothers to report it, but it probably gets through beta testing unnoticed, eventually a customer notices a problem, the programmer provides a way to normalize the paths and releases a fix.
Being undocumented, it's a pitfall waiting to happen. If we at least document it, it could save the programmer a fix cycle.
Documenting might be as simple as "Under Microsoft Windows, slashes in the path returned may have fronts or backs or a mix of both, depending on circumstances", or we can force the slashes as fronts or backs (not sure which is best) and documenting that. We should probably be clear one way or the other.
[ Direct Link to Message ]
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.