This is a known issue, and the path checkers have been removed from the path class in the TR2 proposal and the implementation of said proposal that will be in Boost 1.34 : http://boost-consulting.com/boost/libs/filesystem/doc/design.htm#Abandoned_D... The boost implementation still has the name check functions for programmers that wish to use them: http://boost-consulting.com/boost/libs/filesystem/doc/portability_guide.htm#... But "these functions are not included in the [TR2] proposal because of lack of time, and uncertainty as to their fit with the Standard Library. They can be added later if the LWG so desires." http://boost-consulting.com/boost/libs/filesystem/doc/tr2_proposal.html#Issu... ~ Scott McMurray On 3/11/07, Stefan Seefeld <seefeld@sympatico.ca> wrote:

Hi there,

for the nth time I've seen this question on IRC, without being able to provide a solution:

"i'm having trouble with boost filesystem... when I call " boost::filesystem::create_directory("/.test") ", I get the error "what(): boost::filesystem::path: invalid name ".test" in path: "/.test""... how can I create a directory hidden with .?"

Since I have run into similar issues in the past, I'm taking this complaint to the list now. Is there a solution for this issue ? Does anybody care at all ?

I find it very sad that due to this and similar issues users are turned away from boost_filesystem, as they can't use the library with *their* choice of filenames that works fine on *their* platform.

The portability guide on http://boost.org/libs/filesystem/doc/portability_guide.htm lists as rationale: "...applications which must be portable to a wide variety of platforms...". However, how may people actually care for this level of portability ? Why should an ordinary GNU/Linux (or Windows, for that matter) user care for OpenVMS compatibility ??

Thanks, Stefan

--

...ich hab' noch einen Koffer in Berlin... _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost