- Boost - lists.boost.org

Boost.Signals deprecation and removal
by James E. King, III 15 Jul '18

15 Jul '18

This first implementation of signals has been deprecated since the 1.54 release. (When) are we going to remove it? It is under management of the CMT, and it has been deprecated for over 10 major releases. I would like to suggest we remove it in the Boost 1.68.0 release. - Jim

9 9

Reporting accurate code coverage
by James E. King III 13 Jul '18

13 Jul '18

General Code Coverage Tip (for everyone): Measure your coverage using branches, not lines. Branch coverage tells you how well error cases are tested and therefore a far better measure of quality than line-based. I have seen over 90% line coverage but the branch coverage is more like 60% to 70% on average over the boost CMT-managed repositories. Here's the shell script I use on travis to generate the data and feed it to codecov.io: https://github.com/jeking3/boost-ci/blob/master/ci/travis/codecov.sh The trick is to feed --rc lcov_branch_coverage=1 to the correct commands to generate and preserve the branch information. Thanks, - Jim

3 3

[boost-ci] code coverage build fix
by James E. King III 13 Jul '18

13 Jul '18

For folks using boost-ci integration, here is a fix to your .travis.yml file to enable code coverage builds to work again. I received confirmation from Travis CI that a back-end update on their end corrected some security issues which necessitates this change. https://github.com/boostorg/rational/pull/22/files In the script section of the coverage job, replace the commands: cd lcov && sudo make install with: export PATH=/tmp/lcov/bin:$PATH Thanks, Jim

1 0

[boost-ci] codecov.io integration
by James E. King III 13 Jul '18

13 Jul '18

Folks using boost-ci integration may see the code coverage builds failing. Part of the .travis.yml script includes logic to update lcov to a newer version for branch coverage to work. These build jobs are breaking due to enforcement of the sudo restriction. I am working on a way to fix this and will send out an update when I have a solution. - Jim

1 0

[Range] 1.68 master/beta MSVC compilation error with /fpermissive-
by Vinnie Falco 13 Jul '18

13 Jul '18

When compiling using /fpermissive- (enable strict conformance) I get the following compilation error: boost\boost\range\concepts.hpp(257): error C3646: 'n': unknown override specifier boost\boost\range\concepts.hpp(264): note: see reference to class template instantiation 'boost::range_detail::RandomAccessIteratorConcept<Iterator>' being compiled boost\libs\beast\include\boost\beast\core\string.hpp(87): note: see reference to class template instantiation 'boost::basic_string_view<char,std::char_traits<char>>' being compiled boost\boost\range\concepts.hpp(257): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int boost\boost\range\concepts.hpp(257): error C3646: 'n': unknown override specifier boost\boost\range\concepts.hpp(264): note: see reference to class template instantiation 'boost::range_detail::RandomAccessIteratorConcept<Iterator>' being compiled I'm using the tip of master, digest 000bd8507f8a17ada2c1fef19158e16cdeabd631 Thanks

6 14

[Boost.Serialization] Help with PR fixing a memory leak in the current version
by Alexander Grund 12 Jul '18

12 Jul '18

Hi, TLDR: I would like https://github.com/boostorg/serialization/pull/105 to be merged for the next Boost release to fix a memory leak and need someone to review this or help getting it merge-ready. Details: Some time ago I made an analysis of a crash introduced in Boost 1.65.0 in the serialization part. The details are quite complicated as the cause is static initialization/destruction order in shared libraries which may even depend on compilers (could not confirm) or standard libraries (dito, observed in all tested versions). It boils down to a violation of the expected destruction order in the case of shared libraries. I observed how 2 global instances of the same type but from different shared libs are destroyed together although the 2nd should not yet be which causes a use-after-free from another global instance. The Singletons involved did have methods to detect, whether they are active or destroyed but they were kinda optimized away in Boost 1.65 leading to a crash which makes the whole library unusable. Not understanding the root cause of the crash lead to changing the singleton to use dynamic allocation, but not freeing it which leads to the memory leak that is currently in Boost. The current state of the develop-branch changed this back to the crash situation we had before making it unsuitable for the next release. Another pair of eyes would be great to check the PR and get this finally fixed. Thanks, Alex

6 33

[rational, spirit] 1.68.0 beta 2 bug report
by James E. King III 12 Jul '18

12 Jul '18

A bug reported by someone using a version of 1.68.0 (not specified): https://github.com/qtumproject/cpp-eth-qtum/issues/31#issuecomment-404257256 Seems to have something to do with the new pow template that was added to rational. This came from an old pull request that was simplified, however it seems pow is now a template defined in the namespace boost, and seems to have caused some issues. I'd guess this is only an issue inside boost namespace (so all boost headers) and not external namespaces. Not sure at the moment if the fix should be in rational or spirit. We could instead back out the change to rational for 1.68.0 where pow() was added into namespace boost. https://github.com/boostorg/rational/pull/21 - Jim

2 1

boost/context/all.hpp missing in 1.68.0beta1
by Roger Leigh 11 Jul '18

11 Jul '18

Is this intentional, or an unintentional regression? I was using this header in the CMake component checks to verify the presence of Boost.Context, and this is now breaking. I can update it to use a different header which has been present since 1.61, but this seems like a compatibility break, hence the question. Thanks, Roger

2 1

Fwd: [Range] 1.68 master/beta MSVC compilation error with /fpermissive-
by degski 11 Jul '18

11 Jul '18

It did go off-list. ---------- Forwarded message ---------- From: degski <degski(a)gmail.com> Date: 11 July 2018 at 19:16 Subject: Re: [boost] [Range] 1.68 master/beta MSVC compilation error with /fpermissive- To: Mateusz Loskot <mateusz(a)loskot.net> On 11 July 2018 at 18:56, Mateusz Loskot <mateusz(a)loskot.net> wrote: > (was your response intentionally direct and off-list?) > No, not intentionally, but it depends on how you send the email (because I pushed reply), like on this one (it would have gone off-list again). I had to add the mailing list back in. This doesn't happen with most posts. I'm not sure what you mean, but I meant the driver that Vinnie mentioned > I'm not totally sure what Vinnie mentions. But I'm talking about this one for stable <https://releases.llvm.org/6.0.1/LLVM-6.0.1-win64.exe> and this one for (almost) trunk <http://prereleases.llvm.org/win-snapshots/LLVM-7.0.0-r336178-win64.exe>. I have the impression Vinnie is talking about Clang/C2 <https://blogs.msdn.microsoft.com/vcblog/2016/04/06/clangc2-we-need-your-adv…>, but like I said it's not clear to me, that compiler, however, is discontinued. degski --- *"If something cannot go on forever, it will stop" - Herbert Stein*

1 0

[Histogram] Status of the review schedule
by Mateusz Loskot 11 Jul '18

11 Jul '18

Hi, Following some discussion in January this year, Hans Dembinski's Histogram library was scheduled for review in March. AFAICT, no review happened. What is the current status of the proposal? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 4