dizzy wrote:
On Thursday 31 July 2008 03:10:24 Noah Roberts wrote:
"Class basic_directory_iterator is an important component of the library. It provides an input iterator over the contents of a directory, with the value type being class basic_path."
That seems to be correct.
It's not, in boost 1.34 (if I remember correctly) boost::filesystem::directory_iterator has become an iterator to directory_iterator_entry values rather than to path values as it was before. Implicit conversion operator to path was added (along with an "explicit" getter like .path()).
Documentation is same for both 1.34 and 1.35 - tested on 1.34.
Can you be more explicit (URLs?) where the 1.34/1.35 documentation says that directory_iterator points to a path instead of a directory_iterator_entry? Such statements need correction. Generaly I have used the "reference" documentation for boost filesystem which I do not know to have such problems.
http://www.boost.org/doc/libs/1_35_0/libs/filesystem/doc/index.htm Two-minute tutorial has the above quoted text.
This appears in both the front page and the docs for directory iterator. The find_file function doesn't actually compile if copied verbatim. Need to remove all calls to path() on the iter and replace with "*itr".
You have an older (than 1.34) boost version installed on your system if that does not compile.
Yes, I appeared to have been quite mistaken about what version I was using. This became obvious in another way...