Thanks. That really helps to understand what is going on. I think number 1 is better because you don't end-up testing your system and then it breaks as soon as it hits the customer site. I would actually like #3 too: using the native name_checker as default. Still number 1 seems the best alternative to build reliable software. Sebastien. On Apr 18, 2006, at 5:20 AM, Martin Wille wrote:
Walter Landry wrote:
Martin Wille wrote:
See http://boost.org/libs/filesystem/doc/path.htm#constructors and http://boost.org/libs/filesystem/doc/portability_guide.htm
Having been a user of filesystem for quite a while, I really think it is time to turn off any default checking. This is hardly the first time that we have seen this kind of non-error cause a problem.
I see two other possible improvements:
1. remove the default, requiring the user always to pass a checker. This will definitely stop the guessing among the users.
2. make the error message contain a hint that the default checker might be the wrong choice.
Regards, m Send instant messages to your online friends http:// au.messenger.yahoo.com _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/ listinfo.cgi/boost