From: Keith Burton (kb_at_[hidden])
Date: 2002-09-20 02:54:12
If one uses
that is a relative path is remains a string until converted to a (
absolute ) path.
The conversion to absolute can be relative to any absolute path.
With regard to the UI , the absolute path may be unpleasant but it may
also be the saviour as it explains why the operation failed if the
current directory was not as expected when the relative path was
converted to absolute.
[mailto:boost-bounces_at_[hidden]] On Behalf Of Vladimir Prus
Sent: 19 September 2002 12:04
Subject: Re: [boost] Filesystem Library: Formal Review
Keith Burton wrote:
> I believe that the issues mentioned below can be resolved by making
> all paths absolute when constructed.
I intend this path to specify relative path to some other dir, and if
you convert it to absolute it will be just incorrect.
Even if you make absolute only paths created with system_specific
1. The path non necessary is relative to current dir, it may be relative
to some other implicit directory.
2. Absolute names won't be nice for UI. Consider
error: cannot remove file /home/ [20 directories] /a.cpp
Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk