Subject: Re: [boost] Best Practices for Surviving the Boost Test Gauntlet?
From: Raffi Enficiaud (raffi.enficiaud_at_[hidden])
Date: 2017-08-09 22:11:36
Le 09.08.17 Ã 23:34, Vinnie Falco via Boost a Ã©crit :
> On Wed, Aug 9, 2017 at 2:15 PM, Raffi Enficiaud via Boost
> <boost_at_[hidden]> wrote:
>> Le 08.08.17 Ã 16:12, Vinnie Falco via Boost a Ã©crit :
>> It seems that you redeveloped a testing framework, and this is causing some
>> of the issues we can read there.
> Is there a link to the evidence of this so that I can come up with a fix?
I was randomly clicking on a link, like this one:
Now, I do not know if this is relevant. For preventing running the tests
on unsupported compilers, you may use b2 features, which will clear out
some of the columns:
example in project:
>> I do not know how important is this internal framework to you, but you may
>> go for another test framework and focus on the added value of your library
> Changing test frameworks means refactoring all the tests - I'm sure
> you can understand why I might be reluctant to do that right now.
When is now and when is later?
If now means boost 1.65, then yes, this is not possible. If this is
1.66, I would say it is not such a big deal.
OTOH, if later is never ...
Your call anyway :)
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk