Carlo Wood <carlo@alinoe.com> writes:
I propose the following design. The aim of boost::filesystem should be to support the following coding idiom:
* The programmer should take care to only handle two types of paths in his application:
1) Complete paths 2) Relative paths
* The programmer will have to specifically tell the libary when a constructed path is 'native' and when not. A native path is accepted according to native rules and never gives any problem (exceptions) further on. A non-native path is checked according to the existing rules, which basically means that the programmer can set a default check routine that will in effect determine how portable the application will be.
I propose two design changes:
When proposing design changes, first you have to describe the problems your changes are designed to solve, or nobody will understand the motivation. -- Dave Abrahams Boost Consulting http://www.boost-consulting.com