Dave,
David Abrahams wrote:
Beman Dawes <[EMAIL PROTECTED]> writes:
>If I were king, the portable, generic version of windows-native >"c:/foo" would be "/c/foo" and the portable generic version of >windows-native "/foo" would be *current_path().begin()/"foo". Is >there a reason that approach was rejected?
Yes, it had five or six different problems IIRC, although some of them can be fixed by adding additional syntax. For example, the ambiguity in "/c/foo" - is it a relative path starting with a directory named "c" or a complete path to the c drive
Read as a generic path according to my system, it is not a relative path because it starts with a slash. That's simple and there should be no confusion assuming you know you're not looking at a native format..
Ok, here is the challenge
Given the following directory structure
C:\C\foo \foo
What would be the native representation for the following native paths
C:\C\foo \C\foo C:\foo
Thomas
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
