Boost logo

Boost :

Subject: [boost] [SPAM] Re: Policy for breaking changes
From: Louis Dionne (ldionne.2_at_[hidden])
Date: 2017-12-04 02:26:47

Boost - Dev mailing list wrote
> Le 02/12/2017 à 22:44, Louis Dionne via Boost a écrit :
>> Hi all,
>> [...]
>> I'm looking forward to hearing other people's thoughts on the matter.
> Hi Louis,
> do you want to break the users code with your changes?
> I don't believe, you could want it.
> do you want to maintain two versions of your library?
> If yes, do you want to require that all the parts of an application uses
> the same library version?
> I suggest to don't do that, you will lost users.
> If you want to make it possible to have two version of Boost.Hana, I
> believe the best is to take a new folder and a new namespace, as
> Boost.Spirit.
> I've not do that. I did a really bad work with Boost.Thread/Chrono and
> I'm paying for it.
> [...]

I see; so there's prior experience in simply doing significant
breaking changes without preserving the older behavior in
some way (e.g. new directory), and it's not working well.
Thanks, that's exactly the kind of first hand experience I
wanted to get. I won't fall into the same trap.


Sent from:

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