[filesystem] Using filesystem with std::string

Hello,
Or vice versa. When I include

What problems do you run into specifically? I have code that uses filesystem and std::string in the same source file without any issue. Jason On 04/17/2013 10:02 AM, Michael Powell wrote:
Hello,
Or vice versa. When I include
and <string>, uses of std::string fall over it seems. As long as I do not include filesystem.hpp, it's okay. Would like to use the filesystem features if possible, but I also want to keep track of some strings, possible override operator<< for various requirements (TBD). Is this a boost bug? Or what do I need to do to make it work?
I am building against a static library, multithreading AFAIK, targeting ArchLinux ARM. Building against a GCC 4.7.2 toolchain (CodeBench).
Thank you...
Regards,
Michael Powell _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

On Wed, Apr 17, 2013 at 9:09 AM, Jason Roehm
What problems do you run into specifically? I have code that uses filesystem and std::string in the same source file without any issue.
It's a mystery to me. In one module I either include
Jason
On 04/17/2013 10:02 AM, Michael Powell wrote:
Hello,
Or vice versa. When I include
and <string>, uses of std::string fall over it seems. As long as I do not include filesystem.hpp, it's okay. Would like to use the filesystem features if possible, but I also want to keep track of some strings, possible override operator<< for various requirements (TBD). Is this a boost bug? Or what do I need to do to make it work?
I am building against a static library, multithreading AFAIK, targeting ArchLinux ARM. Building against a GCC 4.7.2 toolchain (CodeBench).
Thank you...
Regards,
Michael Powell _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

On Wed, Apr 17, 2013 at 9:09 AM, Jason Roehm
wrote: What problems do you run into specifically? I have code that uses filesystem and std::string in the same source file without any issue.
It's a mystery to me. In one module I either include
and setup a path, then cannot see std::string from <string>. In another module it's just the opposite. std::string but no boost::filesystem::path. Additionally, CodeBench is telling me boost::filesystem::path could not be resolved. Also std::string could not be resolved. It's a "Semantic Error" which I take it is possibly a linker confusion?
Description Resource Path Location Type Type 'boost::filesystem::path' could not be resolved virtualdirectory.cpp /detector/filesystem/filesystem line 14 Semantic Error
Description Resource Path Location Type Type 'std::string' could not be resolved detectionlogger.h /detector/logger/logger line 42 Semantic Error
Are these compiler errors or IDE errors? C++ IDEs sometimes give false positive errors about C++ code due to incorrect configuration or bugs in the IDE's C++ parser. These issues are IDE-specific, so you are unlikely to be able to find help with them on boost-users (try your IDE vendor's mailing list/support channels instead). At the same time, such errors don't prevent you from actually compiling and running your code. If you are getting actual compiler errors, we can help you with those if you post: 1. What compiler and version you are using ("Sourcery CodeBench" isn't it, that's an IDE that will use some compiler like GCC for actual compilation). 2. A short (but complete) code example that fails to compile. 3. The compiler errors that you are getting. Regards, Nate
participants (3)
-
Jason Roehm
-
Michael Powell
-
Nathan Ridge