From: Peter Dimov (pdimov_at_[hidden])
Date: 2002-03-20 11:14:03
From: "Beman Dawes" <bdawes_at_[hidden]>
> Comments would be appreciated. And of course, thanks to everyone who
> provided comments leading to the current design.
I think that is_file should not map to !is_directory, leaving the door open
for non-file, non-directory paths.
How are relative paths handled?
What is the purpose of initial_directory() if it doesn't affect relative
basic_directory_iterator probably doesn't need a destructor.
basic_directory_entry::path() says 'returns compose(...)' but there is no
compose function, or path manipulation functions in general; are they
supposed to be in a separate library?
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk