- Boost - lists.preview.boost.org

[geometry] Boost 1.73 beta docs include broken links to Geometry Extensions
by Mateusz Loskot 19 Apr '20

19 Apr '20

Hi, I asked about it here a while ago, but without responses [1] https://lists.boost.org/Archives/boost/2020/03/248531.php We have been observing this problem since 1.70 and we have pretty much run out of ideas what is wrong with Boost.Geometry setup [2] https://github.com/boostorg/geometry/issues/585#issuecomment-605106308 The issue is still observed in the 1.73 beta docs [3] https://github.com/boostorg/geometry/issues/585#issuecomment-614263295 Could anyone help us understand [2] what is the problem with our docs? Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 1

Wrong boost.173-beta1 tag for boost.test
by Raffi Enficiaud 18 Apr '20

18 Apr '20

Hi, I just noticed that the tag "boost-1.73-beta1" points to e8b173655c207ec2286227fe17f2e1f68ce44f17 in boost.test, while master points to 9a8cdba280a9c5dc60c4781a26e055ebfe2446ea, and the content of the boost_1_73_0_b1_rc1.tar.bz2 archive is the same as master. I am expecting that the tag "boost-1.73-beta1" points to the content of the archive boost_1_73_0_b1_rc1 . Raffi

2 1

Git documentation is full of twisty passages
by Jonathan Wakely 17 Apr '20

17 Apr '20

I've once again got lost trying to find how to check out Boost from Git. I started at boost.org and (after some missteps) went to https://www.boost.org/users/download/#repository which tells me "Details of the git repositories are on the Boost wiki." https://svn.boost.org/trac/boost/wiki/ModularBoost That takes me to a page with about 20 links. Eventually I decided that the 13th one is the one I want: Getting Started with Modular Boost https://svn.boost.org/trac10/wiki/TryModBoost That takes me to a page that says: "This page is superseded by https://github.com/boostorg/boost/wiki/Getting-Started Please help migrate the rest of the old wiki !" But when I go to that page it says: "The Boost Wiki is at: https://github.com/boostorg/wiki/wiki" So I go there instead, which has nothing about Git. The "Getting Started" page has a link to "Getting Started with Modular Boost Library Development using Git" right at the very bottom, and the "Getting Started - Using Git" link in the sidebar takes me to a different page with very generic Git info (not specific to Boost), and again, near the bottom, is the "Getting Started with Modular Boost Library Development using Git" link. So I click that and ... I'm back in Trac, at https://svn.boost.org/trac10/wiki/StartModWorkflow I don't care bout Boost's use of Git Flow. I don't care about your branching policy, I want to check out the repo! It turns out that on the front page of https://github.com/boostorg/wiki/wiki I should have clicked the "Cheat Sheet" link in the sidebar: https://github.com/boostorg/wiki/wiki/Getting-Started%3A-Cheat-Sheet Could you please make that easier to find from boost.org? It seems to me that https://www.boost.org/users/download/#repository should just link straight to that cheat sheet, or to another page with the correct git submodule commands for checking out the repo.

2 3

Fwd: teeks / boost.test: some test files not found
by Raffi Enficiaud 16 Apr '20

16 Apr '20

I am cross-posting this on the dev mailing list as I would like to know how to fix this before the 1.73 deadline. Thanks and sorry for cross-posting, Raffi -------- Forwarded Message from the test gmane group Hi, On some teeks workers, I have this strange issue: teeks99-09-p-64: https://www.boost.org/development/tests/develop/developer/output/teeks99-09… The error says: .../libs/test/test/framework-ts/log-formatter-test.cpp(117): error: in "test_logs": check output.match_pattern(true) has failed: Pattern file can't be opened! which means some files used for testing, such as test/test/baseline-outputs/log-formatter-test.pattern , are not found. Those files are advertised in the Jamfile, https://github.com/boostorg/test/blob/develop/test/Jamfile.v2#L145 I guess it would be a hard error on b2 if the files were not found. What should I do such that those workers find the test files? I recently added one file to the previous 2 existing files. Thanks, Raffi

1 0

[Graph] Min Cut with float weights
by Phil Endecott 16 Apr '20

16 Apr '20

Dear Experts, I am attempting to use stoer_wagner_min_cut for the first time. Using float as the edge weight type seems to be problematic for non-trivial graphs. I think this is possibly because it adds an edge weight to the cut weight and then later subtracts the same value, but doesn't get back to exactly the previous value due to loss of precision. The errors accumulate and eventually the reported cut weight is nonsense. I am now trying with integer weights but I worry that this could suffer overflows. If my edge weights are in the range 0...W, for a graph with E edges the largest cut weight would be < W*E. But does the algorithm ever use larger values internally? Also, I'd be interested if anyone has tried to break a graph into subgraphs by recursively breaking at the min_cut until the min_cut weight is below some threshold. I have a graph with of the order of 10^4 vertices and 10^6 edges and this would be tractable if the min_cuts broke the graph into roughly equal pieces; instead, they tend to remove a small number of vertices each time, leaving almost as much work for the next recursion. So I think I want to find a cut whose weight is below a threshold and that is in some sense locally minimal and that leaves two largish subgraphs. Any ideas? Cheers, Phil.

1 0

Reminder: 1.73.0 master branch closes one week from today
by Marshall Clow 15 Apr '20

15 Apr '20

22-Apr Boost 1.73.0 closed for release ASAP Boost 1.73.0 release -- Marshall

1 0

Re: [boost] MySQL ASIO library
by Andrey Semashev 14 Apr '20

14 Apr '20

[Sending this reply to list as opposed to personal email] On Wed, Mar 4, 2020 at 3:39 PM Richard Hodges <hodges.r(a)gmail.com> wrote: > On Wed, 4 Mar 2020 at 13:25, Andrey Semashev <andrey.semashev(a)gmail.com> wrote: >> >> On Wed, Mar 4, 2020 at 1:50 PM Richard Hodges via Boost >> <boost(a)lists.boost.org> wrote: >> > >> > > Why just MySQL? >> > >> > Getting something useful released is more important than getting something >> > perfect released. >> > >> > If Ruben has a ready-to-go solution for MySQL, why not make it available to >> > users? >> >> Making it available to users is not the same as making it part of >> Boost. Boost is known for general purpose libraries, as well as more >> domain-focused solutions, but it is not a place for wrappers around >> specific other libraries. Let alone, when the said libraries already >> have C/C++ API. > > Boost also has mpi, regex, asio::ssl and python. What are these if not wrappers around common c libraries? I'm not sure about Boost.MPI, but I thought it was not a wrapper of a single library, but of a standard API that can be implemented by different libraries. Boost.Regex is not a wrapper at all; it implements regular expressions from scratch. asio::ssl is not a library but a plugin for Boost.ASIO that provides one small piece of functionality compared to the rest of the library. Boost.Python is probably closest to an exception, although it is a binding to another language (not a library), which arguably only has one C API and implementation. Yes, there is CPython, but I don't believe it offers a C API. >> > It can always be complemented or extended with Oracle, SQLite, ODBC etc etc >> > later. >> >> If the proposed library offers a stable and flexible API that can be >> backed by multiple implementations then by all means - that would be a >> very interesting proposal indeed. But the author has to demonstrate >> that the proposed user API can in fact be supported by more than one >> backend, so at least two backends need to be presented, and preferably >> with guidelines and infrastructure for adding more. > > Mpi, regex and python would dispute this arbitrary restriction. I don't think so, as per above. > Boost suffers from a lack of contribution. Is there any value in making contribution difficult? I don't think the amount of contributions by itself is the goal. There has to be value associated with the contribution. I just don't think a C++ wrapper of a specific library has enough value.

11 28

Code coverage tests
by Edward Diener 14 Apr '20

14 Apr '20

A number of libraries have code coverage/project tests in Github. I am not against such tests but I am against the idea that "failing" such a test, whatever that means, should prevent a PR from being merged into a Boost library. To me it is nonsense that a perfectly logical change to software should lead to some code coverage "failure", and that therefore the change should be deemed incorrect. I admit I do not know what the criteria are for code coverage but I do not see code coverage determining whether any change to a library is incorrect or not.

11 19

[release] Boost 1.72.0 Beta 1
by Marshall Clow 12 Apr '20

12 Apr '20

Boost release 1.73.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.73.0.beta.1/source/> The SHA256 checksums are as follows: 44f323b42c4375ab3751b67ac5ce53ba5267af20cf375be75675d8952d3cca4e ./boost_1_73_0_b1.7z 5270fa89243a3508331bd3773800de6d2f98d1f160b95e362fa8269d9cd58773 ./boost_1_73_0_b1.tar.bz2 82ffcd4a2e558a31f1ddd6a54ef6c00dae28b95c2ddee575c285544085dcb004 ./boost_1_73_0_b1.tar.gz 910b7560ee239472cc69e6a0c680dc4d9d7ea234faad807738ec98e4811c63d4 ./boost_1_73_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_73_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.73.0 Beta 1 Release Candidate 1
by Marshall Clow 10 Apr '20

10 Apr '20

The release candidates for the first 1.73.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.73.0.beta.1/source/ The release notes are not yet available. The SHA256 checksums are as follows: 44f323b42c4375ab3751b67ac5ce53ba5267af20cf375be75675d8952d3cca4e ./boost_1_73_0_b1_rc1.7z 5270fa89243a3508331bd3773800de6d2f98d1f160b95e362fa8269d9cd58773 ./boost_1_73_0_b1_rc1.tar.bz2 82ffcd4a2e558a31f1ddd6a54ef6c00dae28b95c2ddee575c285544085dcb004 ./boost_1_73_0_b1_rc1.tar.gz 910b7560ee239472cc69e6a0c680dc4d9d7ea234faad807738ec98e4811c63d4 ./boost_1_73_0_b1_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Boost Release Managers

4 6