boost-filesystem

问题 I have the following issue where: std::regex behaves differently if I pass the result of boost::filesystem::path::string() vs storing the result in a intermediate string variable. The first will return a match that is truncated and which is later not accepted by std::stoull (throws invalid_argument exception) while the second works perfectly. See the following commands that explain more the issue: [nix-shell:~]$ ls -l foo total 0 -rw-r--r-- 1 amine users 0 Aug 10 16:55 008 -rw-r--r-- 1 amine

问题 I am iterating through a directory, and when an item matches some criteria, I delete it. Can I do it safely from within the loop, or to I have to save paths in an array and delete then later? I did not find a relevant information in boost::filesystem docs. 回答1: Quoting the first part of a note attached to the docs of boost::filesystem::directory_iterator (emphasis is my own): Programs performing directory iteration may wish to test if the path obtained by dereferencing a directory iterator

问题 How can I use the Boost library to change the permissions of a file to read-only? There are some questions that I have already seen, such as this and this, but I still don't know how to do it, I have tried doing boost::filesystem::wpath path = L"abc.txt"; if( boost::filesystem::exists( path ) && boost::filesystem::is_regular_file( path ) ) { boost::filesystem::file_status s = boost::filesystem::status( path ); /* here I need to set file permissitons to READ ONLY for `path` file */ } Any ideas

问题 I want to copy a file from directory to another, but my program always aborts for some reasons.Has anyone done this this before could tell me what was wrong? And how could I catch exceptions was thrown by copy_file , I checked boost site, but I could not find any relevant information about exception. path user_path( "C:\\My Folder" ); boost::filesystem::create_directory( user_path ); path file( "C:\\Another\\file.txt" ); boost::filesystem::copy_file( file, user_path ); Thanks, 回答1: You have

问题 I am trying to move a file from a location to another using boost::filesystem . I used boost::filesystem::rename function but when I try to do that I have the following error. terminate called after throwing an instance of 'boost::filesystem::filesystem_error' what(): boost::filesystem::rename: Invalid cross-device link: "./file_A.csv", "/opt/data/file_B.csv" Aborted (core dumped) I understood that the problem is that I am trying to move a file from one folder into another mounted on a

问题 As explained in the documentation, the expected output of the following is: boost::filesystem::path filePath1 = "/home/user/"; cout << filePath1.parent_path() << endl; // outputs "/home/user" boost::filesystem::path filePath2 = "/home/user"; cout << filePath2.parent_path() << endl; // outputs "/home" The question is, how do you deal with this? That is, if I accept a path as an argument, I don't want the user to care whether or not it should have a trailing slash. It seems like the easiest

问题 I am getting consistent segfaults with almost any operation I am trying to perform with boost path. ( Edit: It appears that all segfaulting functions are related to current_path() ) Sample program: #include <boost/filesystem/operations.hpp> #include <boost/filesystem/path.hpp> #include <iostream> using namespace std; using namespace boost::filesystem; using namespace boost::system; int main(int argc, const char * argv[]) { error_code err; auto p = path("hello/../world"); cout << p.string() <<

问题 From boost/filesystem/path.hpp: # ifdef BOOST_WINDOWS_API const std::string string() const { [...] } # else // BOOST_POSIX_API // string_type is std::string, so there is no conversion const std::string& string() const { return m_pathname; } [...] # endif For wstring() it is exactly the other way around - returning by reference on Windows and by value on POSIX. Is there an interesting reason for that? 回答1: On Windows, path stores a wstring , since the only way to handle Unicode-encoded paths

问题 There have been several questions about getting experimental/filesystem to compile in the latest versions of GCC and Clang: experimental::filesystem linker error But now filesystem has been accepted into c++17 so no more need for experimental or the -lstdc++fs flag, right? Wrong I cannot even #include <filesystem> on the head version of either clang++ or g++ when I try on: http://melpon.org/wandbox Is there still some other argument I need? -lstdc++fs just gives me the experimental version,

问题 I am iterating through all files in a directory recursively using the following: try { for ( bf::recursive_directory_iterator end, dir("./"); dir != end; ++dir ) { const bf::path &p = dir->path(); if(bf::is_regular_file(p)) { std::cout << "File found: " << p.string() << std::endl; } } } catch (const bf::filesystem_error& ex) { std::cerr << ex.what() << '\n'; } But this includes hidden files and files in hidden directories. How do I filter out these files? If needed I can limit myself to