May 2017 - Boost - lists.preview.boost.org

[poly_collection] throws upon insertion
by Andrzej Krzemienski 09 May '17

09 May '17

Hi, I am looking at the documentation of poly_collection. I will not be able to thoroughly review and test the library. But judging from the documentation, the problem is worth solving, and the approach to solve it is sound. I have one question/observation though. I am trying to figure out how preventing an incorrect insert() works. In the docs ( http://rawgit.com/joaquintides/poly_collection/website/doc/html/poly_collec…) it says that it will sometimes throw if it cannot determine the most derived type. In the class reference, I get: ( http://rawgit.com/joaquintides/poly_collection/website/doc/html/poly_collec… ) ``` (1) c.insert(x) (2) c.insert(it,x) Effects: If the type of the subobject of t is not registered, then if this type is T and T is acceptable, does the registration, otherwise throws. If t is not a non-const rvalue expression and the type of its subobject is not CopyConstructible, throws. Inserts an element with a subobject move constructed or copy constructed from the subobject of t: (1) at the end of the corresponding segment; (2) just before the position indicated by it, if it points to the corresponding segment, or at the end of the segment otherwise. Returns: An iterator to the newly inserted element. Complexity: Amortized constant time plus linear in the distance from the insertion position to the end of the segment. ``` And maybe it is just me, but I cannot make the sense of it. First, it refers to 't' but in the signatures we have an 'x'. Next, the first sentence has two "if"s and one "otherwise" and I do not know which "if" the "otherwise" binds to. I read it as saying: if T is derived from the interface (like class `warrior`) but is not movable (which implies that T is not "acceptable"), then the program will compile fine but will later throw an exception. Is my interpretation correct? But if so, why not refuse to compile instead? Maybe it would be better tom make the prose longer in "Effects" clause, but to make it harder for misinterpretation. Regards, &rzej;

2 3

[Boost.Test] access to boost::unit_test::framework::master_test_suite().{argc, argv} outside from BOOST_TEST
by Olaf Peter 08 May '17

08 May '17

Hello, my test program uses boost.test datasets. I've wrote a filesystem loader for the input and expected data. Now I run into the problem, that boost::unit_test::framework::master_test_suite().{argc, argv} is only setup inside the tests self. My loader isn't a test case ... I can check it by using a simple mock, like struct app_mock { app_mock(); int const argc; char** const argv; }; app_mock::app_mock() : argc(boost::unit_test::framework::master_test_suite().argc) , argv(boost::unit_test::framework::master_test_suite().argv) { } BOOST_AUTO_TEST_CASE( app_mocker ) { app_mock app; std::cout << "Count = " << app.argc << '\n'; for(int i = 0; i != app.argc; i++) std::cout << "Arg = " << app.argv[i] << '\n'; } $ my_test -- my_args Count = 2 path/to/exe my_args these works, but as mentioned: dataset_loader::dataset_loader(fs::path const& path) { app_mock app; std::cout << "ARGC = " << boost::unit_test::framework::master_test_suite().argc << '\n'; read_files(path); } is always zero. How can I read the argc/argv values? Thanks, Olaf

2 4

[gsoc17] welcome Ruoyun
by Vissarion Fisikopoulos 05 May '17

05 May '17

Hi Ruoyun, congrats and welcome! As mentioned by GSoC this is the community bonding period. So you can start reading the documentation: http://www.boost.org/doc/libs/1_64_0/libs/geometry/doc/html/index.html This wiki is also useful: https://github.com/boostorg/geometry/wiki check for example https://github.com/boostorg/geometry/wiki/Contribution-Tutorial We can also start now discussing and refining you project goals. Best, Vissarion. ---------- Forwarded message ---------- From: Google Summer of Code <summerofcode-noreply(a)google.com> Date: 4 May 2017 at 19:35 Subject: GSoC 2017: You are a mentor for Ruoyun Jing To: fisikop(a)gmail.com [image: Google Summer of Code] Congratulations, you will be spending the next few months working with Ruoyun Jing on GSoC2017 Boost.Geometry:Filtering of compare distance predicates Proposal <https://summerofcode.withgoogle.com/dashboard/organization/4839090517180416…> . Please welcome <http://write.flossmanuals.net/gsoc-mentoring/community-basics/> your student into your community and work with them to plan the milestones they will need to meet. Setting clear expectations early is one of the best ways to help your student succeed. You can read the Mentor Manual <http://write.flossmanuals.net/gsoc-mentoring/about-this-manual/> for some great tips on how to communicate with your student and make a project plan. If you have any questions please contact our Google Open Source Programs team at gsoc-support(a)google.com or email the mentors mailing list if appropriate. -Google Open Source Programs team This email was sent to fisikop(a)gmail.com. You are receiving this email because of your participation in Google Summer of Code 2017. https://summerofcode.withgoogle.com To leave the program and stop receiving all emails, you can go to your profile <https://summerofcode.withgoogle.com/dashboard/profile/> and request deletion of your program profile. For any questions, please contact gsoc-support(a)google.com. Replies to this message go to an unmonitored mailbox. © 2017 Google Inc., 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA

1 0

[1.64] [ublas] Broken/regession due to Boost.Serialization changes
by Peppard 05 May '17

05 May '17

Hi, since the 1.64 release including e.g. boost/numeric/ublas/matrix.hpp gives an error like "no member named 'make_array' in namespace 'boost::serialization'", according to the official(?) test overview (http://www.boost.org/development/tests/master/developer/numeric-ublas.html) on a lot of systems. There have been discussions on this mailing list in Nov/Dec 2016 probably at least related to this ([boost] [serialization][ublas][test] failures in serialization causing regressions) and in Feb 2017 ([boost] [serialization][uBlas] Serialization still breaking anything that uses uBlas?), also there are several pull requests on GitHub, e.g. https://github.com/boostorg/ublas/pull/46. (I assume you are aware of this already, but I wonder why there was a release with a regression like this, maybe due to a maintainer missing? How are cases like these handled?) Thanks! (Sorry if this is a double post but the list address seemed to change from @wowbagger.crest.iu.edu to @lists.boost.org so I tried again.)

3 2

[beast] 1.0.0-b35 has been merged to master
by Vinnie Falco 05 May '17

05 May '17

Beast 1.0.0-b35 has been merged to the master branch. Changes include: API Changes * New HTTP interfaces This version has a freshly written HTTP parser which improves on the performance of the previous parser. New interfaces are provided to allow incremental reading of HTTP messages and better handling for Expect: 100-continue. These are API breaking changes. Beast is a C++11 header-only HTTP and WebSocket library built on Boost.Asio, scheduled for Boost formal review starting July 1st. Official repository: https://github.com/vinniefalco/Beast Documentation: http://vinniefalco.github.io/beast/index.html Stakeholders and interested parties may review version the pull request for 1.0.0-b36 if desired, all feedback welcomed: https://github.com/vinniefalco/Beast/pull/330 Thanks!

1 0

Boost macros for Android
by Vicente J. Botet Escriba 04 May '17

04 May '17

Hi, I would like to inhibit some failing test on Android. Are there any specific BOOST macros for Android? Best, Vicente

3 3

Test - ignore
by Michael Caisse 03 May '17

03 May '17

-- Michael Caisse Ciere Consulting ciere.com

1 0

GMane reflection of Boost mailing list messages
by Edward Diener 03 May '17

03 May '17

I am a user of GMane in regard to Boost mailing lists and it appears that GMane is no longer picking up Boost mailing list changes or allowing users to respond to mailing list posts through the corresponding GMane ng. Does anyone know how to rectify this situation ? I recall that Boost might have changed who was hosting the mailing lists and I am wondering if this is the reason that GMane no longer works with Boost mailing lists. The GMane website appears to be in transition, and all links for contacting anyone at GMane have been removed. I did try to contact Lars Magne Ingebrigtsen, who has been running GMane, but I do not know if this will produce any results.

4 9

Fwd: [clang] clang-cl expansion of macros
by degski 01 May '17

01 May '17

On 16 April 2016 at 17:58, Edward Diener <eldiener(a)tropicsoft.com> wrote: > What I strongly suspect will finally happen is that clang will not fix > these emulation problems because they are too tricky and numerous to do. > Instead they will probably declare that their emulation is good enough for > the majority of preprocessor constructs and that Boost PP, which pushes the > preprocessor to its limits, is not meant to work with their flawed VC++ > emulation. I hope I am wrong about that supposition, but having spent much > time in Boost PP and Boost VMD trying to workaround VC++ non-standard > preprocessor behavior I can envision that having to code "down" to that > behavior in numerous complicated instances will be too much time consuming > work for the clang developers who have chosen to work with VC++ > preprocessor emulation. > I've successfully built boost-1.64 with VC1410 (from the developer command prompt). Trying to use boost with a project using Clang 4.0.0 (both the LLVM and C2 backends) gives me the following PP error messages: 1>------ Rebuild All started: Project: test, Configuration: Debug x64 ------ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/iterat or/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/iterat or/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/au x_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(59,7): error : too many arguments provided to function-like macro invocation 1> 2 1> ^ 1> z:\vc\x64\include\boost/preprocessor/facilities/expand.hpp(26,10): note: macro 'BOOST_PP_EXPAND_I' defined here 1> # define BOOST_PP_EXPAND_I(x) x 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/iterat or/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/iterat or/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/au x_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : expected a qualified name after 'typename' 1> BOOST_MPL_AUX_NA_SPEC2( 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(166,44): note: expanded from macro 'BOOST_MPL_AUX_NA_SPEC2' 1> #define BOOST_MPL_AUX_NA_SPEC2(i, j, name) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/na_spec.hpp(64,11): note: expanded from macro '\ 1> 1> BOOST_MPL_AUX_NA_SPEC_MAIN' 1> BOOST_MPL_PP_PARAMS(i, typename T) \ 1> ^ 1> z:\vc\x64\include\boost/mpl/aux_/preprocessor/params.hpp(58,11): note: expanded from macro 'BOOST_MPL_PP_PARAMS' 1> , BOOST_MPL_PP_AUX_PARAM_FUNC \ 1> ^ 1> In file included from test.cpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem.hpp:16: 1> In file included from z:\vc\x64\include\boost/filesystem/path.hpp:28: 1> In file included from z:\vc\x64\include\boost/iterat or/iterator_facade.hpp:12: 1> In file included from z:\vc\x64\include\boost/iterat or/interoperable.hpp:11: 1> In file included from z:\vc\x64\include\boost/mpl/or.hpp:43: 1> In file included from z:\vc\x64\include\boost/mpl/au x_/include_preprocessed.hpp:37: 1>z:\vc\x64\include\boost/mpl/aux_/preprocessed/plain/or.hpp(58,1): error : expected ',' or '>' in template-parameter-list Up till now I was using a hacked boost-1.62. So in order to see what would happen, I also built boost-1.63. Apart from a small change in type_with_alignment.hpp (adding a ckeck for _MSC_VER not to exist if __clang__ does exist in line 87), boost-1.63 compiles without a problem (no specific (relevant to the emulation) command line parameters). Is there a macro I should define or is there something else I should set/do in order to use boost-1.64 with Clang 4.0.0 on windows? Any other suggestions? degski -- "*Ihre sogenannte Religion wirkt bloß wie ein Opiat reizend, betäubend, Schmerzen aus Schwäche stillend.*" - Novalis 1798

3 13