Re: [boost] Filesystem Library --- exceptions

From: Victor A. Wagner, Jr. (vawjr_at_[hidden])
Date: 2002-09-23 04:05:26

OTOH, I think that "move" ought to MOVE the file if it has to, and simply 
change it's name if that will suffice.

Diffirent strokes..........

it IS a shame that the committee saw fit to only include a what() method in 
the standard exceptions... a single int in addition would have made a lot 
of things easier, IMO.

At Monday 2002/09/23 01:49, you wrote:
> > To be concrete, suppose I call 'rename' and it throws. There are at
> > least to reasons of failure: (1) source file does not exist and (2)
> > source and destination are on different drives/filesystems. In the
> > second case I'd want to call 'copy', followed by 'remove'. However, how
> > can I detect that the second case caused the error?
>
>This kind of thing is supposed to be handled by the library user ?
>
>I was thinking that the fact of using a real "rename" feature of the
>underlying operating system, or to use a "copy+remove" functionality was of
>the domain of implementation and should not be exposed to the library user.
>
>Am I wrong ?
>
>     Mickael Pointier
>
>
>
>_______________________________________________
>Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

Victor A. Wagner Jr.      http://rudbek.com
PGP RSA fingerprint = 4D20 EBF6 0101 B069 3817 8DBF C846 E47A
PGP D-H fingerprint = 98BC 65E3 1A19 43EC 3908 65B9 F755 E6F4 63BB 9D93
The five most dangerous words in the English language:
               "There oughta be a law"