- Boost - lists.boost.org

[graph] disjoint_sets
by James E. King III 17 Jul '18

17 Jul '18

Hello folks in the Boost.Graph team, The CMT currently maintains Boost.DisjointSets which contains a class that is only used by Boost.Graph and Boost.GraphParallel. The headers are published in "boost/pending" right now. Given the CMT has a considerable workload already I would like to discuss moving disjoint_sets into Boost.Graph, as long as it satisfies the requirements for the two repositories currently consuming it. This would be for 1.69.0. Any thoughts, objections, considerations on this (open to anyone)? Thanks, Jim

2 3

Heads up about future standards annexing new identifiers
by Marshall Clow 16 Jul '18

16 Jul '18

As facilities get added to the standard library, they need names. When this happens, it restricts what other developers can and cannot do in their programs. For example, one cannot do this and expect most anything in the standard library to work: #define allocate(T) . new T [ But you knew about that ]. What you may not have known about was that the standards committee has voted contract enforcement/checking facilities into the draft standard (which will probably be C++20). This includes attributes named: 'expects' and 'ensures'. (all lower case) I have checked all of boost, and with the possible exception of Boost.Contract, we do not have any macros with those names. But you might want to keep your eyes open. -- Marshall P.S. These are not keywords - so it's perfectly fine to have member functions with these names. Variables, too. Probably even free functions - though I haven't tried that. But macros are right out ;-) P.P.S. For people who are interested, the paper is http://wg21.link/P0542

2 1

Searching for a intrusive::avltree_algorithms/bstree_algorithms dev
by Thimothée Virgoulay 16 Jul '18

16 Jul '18

Hello I'm working with the boost library (intrusive: : avltree_algorithms/bstree_algorithms ) and I found some bugs (not sure, maybe it's me who haven't understood the algorithm logic ). I have made hotfixes , add functions and it's working. But I don't know if this change were fine or needed. So I 'm searching for someone who can exchange with me about this library. Thimothée Virgoulay, second's year master degree in Bioinformatics at Montpellier University, France.

4 3

[rational] 1.68.0 merge permission
by James E. King III 16 Jul '18

16 Jul '18

The addition of pow() for rational was identified as a problem in beta testing. It has been reverted for now, and an issue added to the github repository to revisit it after 1.68.0. There are two commits I would like to merge to master: 1. The revert of pow which caused problems 2. A CI-only change to .travis.yml that fixes codecov.io and coverity scan build jobs in light of recent security upgrades in travis CI. No production code changes, zero affect on the release build workflow. This will allow the build status to remain green for the repository as it is merged to master. Thanks, Jim

2 1

[CMT] 1.68.0 merge permission
by James E. King III 16 Jul '18

16 Jul '18

The CI builds in CMT repositories are failing since Travis CI updated their backend last week. The fix is simple and isolated in the .travis.yml file in each repository which is not part of the boost release build cycle. All repositories develop branch have been updated with the fix. I'd like to merge the fix in the CMT repositories into master to eliminate the remaining failed build indicators. Given the change is only in .travis.yml I hope that will be acceptable. Without the fix any cron job on master in these repositories will fail in codecov.io and covscan. Thanks, Jim

2 1

Invalid arguments
by randy 16 Jul '18

16 Jul '18

I’ve the following function but i get invalid arguments error , can please someone tell me where’s this invalid param or argument : int Asio_Send_Pck(int iSendt,int Lsocket,char * Lbuff,int Len) { session* iTempSession = reinterpret_cast<session*>(Lsocket); boost::asio::async_write(iTempSession->socket() , boost::asio::buffer(Lbuff, Len), boost::bind(&session::handle_write, iTempSession, boost::asio::placeholders::error, iTempSession->data, iSendt )); return 0; };

2 1

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