is_empty and remove_all may throw even when called with error_code& argument.

[nigel.pattinson@…]

Some of the code that underpins is_empty and remove_all constructs directory_iterator objects without passing through an error_code& argument. I have spotted this in both is_empty_directory and remove_all_aux . The latter also uses operator++ on the iterator rather than calling increment, I haven't checked whether this is more widespread.

[ivan.mazovec@…]

i have same problem.

code:

boost::system::error_code e;
boost::filesystem::is_empty("/lost+found", e);

output:

unknown location(0): fatal error: in "general_case": boost::filesystem::filesystem_error: boost::filesystem::directory_iterator::construct: Permission denied: "/lost+found"