Boost logo

Boost :

Subject: Re: [boost] boost::filesystem changes since version 1.55.0
From: Armin Pies (armin.pies_at_[hidden])
Date: 2014-12-09 04:02:52

Hi Beman.

In the meantime I have found the documentation you have mentioned and it lead to my work-around I have already mentioned.

Nevertheless the documentation just states that something was changed but not that I have to adapt existing code.

These "unexpected" exceptions in the operator++ are correct ("no such file or directory") but they were not thrown before boost version 1.56.
So I have made a work-around using the increment(error_code) method, just ignoring the resulting error code.

By the way, these "new" exceptions in the operator++ have only occurred under Linux (gcc 4.8.2) but not under Windows (vc++ 12.0).



-----Ursprüngliche Nachricht-----
Von: Boost [mailto:boost-bounces_at_[hidden]] Im Auftrag von Beman Dawes
Gesendet: Montag, 8. Dezember 2014 19:40
An: Boost Developers List
Betreff: Re: [boost] boost::filesystem changes since version 1.55.0

On Fri, Dec 5, 2014 at 7:19 AM, Armin Pies <armin.pies_at_[hidden]> wrote:

> I have tried to upgrade our software from using boost 1.55.0 to 1.57.0.
> Now we're getting unexpected exceptions in our code using
> filesystem::recursive_directory_iterator.
> Checking or
> there are no
> changes concerning boost::filesystem.
> Is there somebody who can tell me what has been changed in
> boost::filesystem, versions 1.56 and 1.57, and what impact it has on
> existing code or what I have to adapt to fix our software?


1.56.0 included reorganization and fixes for recursive_directory_iterator::increment.

When you say you are getting "unexpected exceptions", do you mean exceptions you didn't expect that are correctly reporting actual errors or exceptions you didn't expect that are incorrectly reporting errors even though no error actually occurred?



Unsubscribe & other changes:

Boost list run by bdawes at, gregod at, cpdaniel at, john at