attachment set

lcarreon@… — Wed, 02 Feb 2011 22:28:44 GMT

attachment → test_path.cpp

status changed; resolution set

anonymous — Fri, 04 Feb 2011 16:59:53 GMT

status new → closed
resolution → wontfix

This was a real head scratcher!

Your test program outputs quotes around the generic_string example but not around the native example. That confuses the other issues.

native() returns const string_type&. On posix, string_type is std::string, so no problem. Windows, string_type is std::wstring, so outputting it to std::cout should result in a compile time error. But...

Your test program is sloppy about namespaces:

using namespace std; using namespace boost::filesystem;

On Windows, that lets the class path conversion from wstring to kick in via ADL, resulting in a path temporary which is then output to cout via operator <<.

Operator << with a path correctly places quotes around the output string, resulting in the output you are seeing on Windows.

While it might be nice to poison path::operator<<(), that isn't really a bug in class path so I'm closing this as "won't fix".

--Beman

lcarreon@… — Fri, 04 Feb 2011 23:37:28 GMT

What confused me to use the native() function in my test program is the fact that on Windows the string() function insisted on displaying in generic format. Even the native() function did the same unless I invoked the make_preferred() function on the path. Thank you for your explanation, I'm switching my test program back to using the string() function.

Boost C++ Libraries: Ticket #5152: Inconsistent behavior of path.native() function

attachment set

status changed; resolution set