Beman Dawes [EMAIL PROTECTED] writes:
I don't know if it was controversial, but I did bring this up during
the review and I do think its very important. The basic definition
of an absolute path should be a path that overrides the base path
during a resolve. To rephrase, 'foo' is relative
At 10:33 PM 11/26/2002, Glen Knowles wrote:
From: Beman Dawes [mailto:[EMAIL PROTECTED]]
current_directory() - returns the current directory (and drive if
windows)
That's been added, per the formal review. The actual names for it
and its sibling function will be current_path() and
Title: RE: [boost] Re: relative/absolute paths in filesystem library
From: Beman Dawes [mailto:[EMAIL PROTECTED]]
is_absolute() - true if the directory (sans drive) starts with
a / (c:/, /, /blah are absolute; c:blah, blah, ../blah are not)
That's been added too.
Hum... On multi
At 03:08 PM 11/25/2002, Justus Schwartz wrote:
* Beman Dawes [EMAIL PROTECTED] [021125 03:26]:
The branch fs_review gives a snapshot of work-in-progress. It isn't
stable
at the moment, but progress is definitely being made. I'm hoping to get
a
lot of work done on it this coming week.
i
Title: RE: [boost] Re: relative/absolute paths in filesystem library
I'm dealing with filesystem paths and urls and the way we ended up implementing it is with the following functions (we are not currently using boost::filesystem, these are from an internal library):
current_directory
At 02:15 PM 11/24/2002, Matthias Troyer wrote:
I have started using the boost filesystem library in our application
codes and encountered a problem that could be solved by adding either
of the three functions
bool is_relative() const;
bool is_absolute() const;
void make_absolute();
to the path
