RE: [boost] Design for a file system library

From: Jeff Garland (jeff_at_[hidden])
Date: 2002-02-23 11:42:56

>  >If you don't have a current working directory then the iterator will need
>
>  >to return a full path in hierarchical systems, not just a name to be able
>  >to be able to open a file.  Or am I missing something?
>
> Since directory iteration requires a path, the path to the file can always
> be composed from that path plus the returned name.

Ok, thanks I missed that....

>  >Also, don't we need a functions to distinguish between files and
>  >directories.
>  >Something like:
>  >
>  >Given a path provide a function returning a bool that indicates if the
> path
>  >is a file.
>  >
>  >Given a path provide a function returning a bool that indicates if the
> path
>  >is a directory.
>
> Yes, those are specific examples of attributes (or properties).  Dietmar
> Kühl (with refinements suggested by Jan Langer) has already suggested a
> powerful interface to get/set a large list of attributes.

But I'm assuming the specific supported attributes are going to be platform
specific?   Whereas the need to determine if the path is a file or directory
isn't platform specific given a universe of directories and files.

Jeff