March 2016 - Boost-users - lists.boost.org

Re: [Boost-users] [boost] Boost 1.61.0 Beta 1 Release Candidate 1
by Daniel James 21 Mar '16

21 Mar '16

On 19 March 2016 at 19:38, Vladimir Prus <vladimir.prus(a)gmail.com> wrote: > > Release candidates for 1.61.0 beta 1 are now available: > > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.zip > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.tar.bz2 > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.tar.gz > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.7z I've put the documentation on the website. It's linked from the release notes: http://www.boost.org/users/history/version_1_61_0.html

2 3

Confused by boost graph descriptor invalidation
by Paolo Bolzoni 21 Mar '16

21 Mar '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear list, I have a adjacency_list with OutEdgeList and VertexList as vecS and I do need to split edges. To split an edge is to remove it, replace with two edges with a new vertex in the middle. Since I am changing the graph I want to be sure how the invalidation works and so I read the page in[1], but I am confused by the table "Summary of Descriptor and Iterator Invalidation." The text states the table summarizes which operations cause descriptors and iterators to become invalid, said so what does "OK" means? My feeling is that iterators never become invalid, is that the case? And what "EL=vecS && Directed=directedS" means? It means that you are _fine_ only if you are working with a adjcency_list with OutEdgeList as vecS and Directed=directedS or the opposite (i.e., if you are using such adjcency_list then all iterators become invalid) Yours faithfully, Paolo [1] http://www.boost.org/doc/libs/release/libs/graph/doc/adjacency_list.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJW78v4AAoJENxW6b8QprD6Aq4H/jXK9kfFy65yZzzzySsFteS6 V9PFvCyrjzgrbGojMZok3Xxz2fJBvfvomqnzEgDuFy7I1P73dkyL3gbwRoPINQpN Qu/0zqskpWf6gJjnu0/3QtSDRBQ1hvT/ZmfhfoUyh1CSQuxyH+/VQV5V4uaDxymQ /atbZWn8Ry1e4noHlS1l27FvEF+qsxOGaHsqBr1Of5KYvcdWmEqN2PJjqWF87Ev7 +sCY4/aD5rT0n+FLBa/Qk/opblbNYprjCmTgpWjKh4lnRmrHJAJNTQeKwZC+e8Hx SOqW2kAQMRW46/y+VcMnOOv+M5UOxqj0K+EgAWVLaoyAZTJzbSc2E9VQL3fB4AA= =xH7S -----END PGP SIGNATURE-----

2 1

boost linker errors
by Mark 21 Mar '16

21 Mar '16

Hi I am trying to link to a boost library, program_options, using Visual Studio 2015 and I am getting 'lnk2019 unresolved external symbol’ errors. I have built the boost libraries using b2 and built the complete libraries for msvc. The libraries are 32 bit. I have configured visual studio to point at the correct location for both the headers and the libraries, I’ve confirmed this. I am statically linking against libboost_program_options-vc140-mt-sgd-1_60.lib, though I have tried all the other variants of this library, e.g. removed the mt, the gd and the s parts of the name, without effect. I have tried all the different calling convention options in properties, I am building with the /MTd option set, though I have tried others. i have searched the internet thoroughly and cannot find a replication of my problem. Using BOOST_LIB_DIAGNOSTIC confirms that the library is being linked, I see the message in the output window. The errors I am getting are: Severity Code Description Project File Line Suppression State Error LNK2019 unresolved external symbol "void __cdecl simulate(class nemo::Simulation *,unsigned int,unsigned int,class std::basic_ostream<char,struct std::char_traits<char> > &)" (?simulate@@YAXPAVSimulation@nemo@@IIAAV?$basic_ostream@DU?$char_traits@D@std@@@std@@@Z) referenced in function _main NeMo_Test C:\Users\Development\Documents\Visual Studio 2015\Projects\NeMo_Test\NeMo_Test\main.obj 1 Error LNK2019 unresolved external symbol "long __cdecl benchmark(class nemo::Simulation *,unsigned int,unsigned int,class boost::program_options::variables_map &,unsigned int)" (?benchmark@@YAJPAVSimulation@nemo@@IIAAVvariables_map@program_options@boost@@I@Z) referenced in function _main NeMo_Test C:\Users\Development\Documents\Visual Studio 2015\Projects\NeMo_Test\NeMo_Test\main.obj 1 Error LNK2019 unresolved external symbol "class nemo::Configuration __cdecl configuration(class boost::program_options::variables_map &)" (?configuration@@YA?AVConfiguration@nemo@@AAVvariables_map@program_options@boost@@@Z) referenced in function _main NeMo_Test C:\Users\Development\Documents\Visual Studio 2015\Projects\NeMo_Test\NeMo_Test\main.obj 1 Error LNK2019 unresolved external symbol "class boost::program_options::variables_map __cdecl processOptions(int,char * * const,class boost::program_options::options_description const &)" (?processOptions@@YA?AVvariables_map@program_options@boost@@HQAPADABVoptions_description@23@@Z) referenced in function _main NeMo_Test C:\Users\Development\Documents\Visual Studio 2015\Projects\NeMo_Test\NeMo_Test\main.obj 1 Error LNK2019 unresolved external symbol "class boost::program_options::options_description __cdecl commonOptions(void)" (?commonOptions@@YA?AVoptions_description@program_options@boost@@XZ) referenced in function _main NeMo_Test C:\Users\Development\Documents\Visual Studio 2015\Projects\NeMo_Test\NeMo_Test\main.obj 1 Error LNK1120 5 unresolved externals NeMo_Test C:\Users\Development\Documents\Visual Studio 2015\Projects\NeMo_Test\Debug\NeMo_Test.exe 1 I would be very grateful if anyone could provide a clue as to what I am missing or have done wrong. Many thanks

2 2

[Fit] formal review starts today
by Vicente J. Botet Escriba 21 Mar '16

21 Mar '16

Dear Boost community, sorry for the late anounce The formal review of Paul Fultz II's Fit library starts today, 2nd March and ends on 13th March. Fit is a header-only C++11/C++14 library that provides utilities for functions and function objects. Fit is: - Modern: Fit takes advantages of modern C++11/C++14 features. It support both `constexpr` initialization and `constexpr` evaluation of functions. It takes advantage of type deduction, varidiac templates, and perfect forwarding to provide a simple and modern interface. - Relevant: Fit provides utilities for functions and does not try to implement a functional language in C++. As such, Fit solves many problems relevant to C++ programmers, including initialization of function objects and lambdas, overloading with ordering, improved return type deduction, and much more. - Lightweight: Fit builds simple lightweight abstraction on top of function objects. It does not require subscribing to an entire framework. Just use the parts you need. Fit is divided into three components: * Function Adaptors and Decorators: These enhance functions with additional capability. * Functions: These return functions that achieve a specific purpose. * Utilities: These are general utilities that are useful when defining or using functions Fit has been tested on gcc 4.6-4.9, clang 3.4-3.7, and Visual Studio 2015. For more information see: Github:https://github.com/pfultz2/Fit/tree/boost Documentation:http://pfultz2.github.io/Fit/doc/html/ We encourage your participation in this review. At a minimum, kindly state: - Whether you believe the library should be accepted into Boost * Conditions for acceptance - Your name - Your knowledge of the problem domain. You are strongly encouraged to also provide additional information: - What is your evaluation of the library's: * Design * Implementation * Documentation * Tests * Usefulness - Did you attempt to use the library? If so: * Which compiler(s) * What was the experience? Any problems? - How much effort did you put into your evaluation of the review? More information about the review process can be found here:http://www.boost.org/community/reviews.html We await your feedback! Best regards, Vicente J. Botet Escriba

6 18

[Fit] formal review is over
by Vicente J. Botet Escriba 21 Mar '16

21 Mar '16

Hi, The review of the Fit library finished yesterday 20 March. Thanks to all the people who participated in the review, as a reviewer or commenting the threads. I hope to announce the result soon ;-) Best, Vicente P.S. Of course you/we can continue with the discussion and add issues in github that would help to improve the library. For more information see: Github:https://github.com/pfultz2/Fit/tree/boost Documentation:http://pfultz2.github.io/Fit/doc/html/

1 0

Re: [Boost-users] [boost] Boost 1.61.0 Beta 1 Release Candidate 1
by Marshall Clow 20 Mar '16

20 Mar '16

On Sat, Mar 19, 2016 at 12:38 PM, Vladimir Prus <vladimir.prus(a)gmail.com> wrote: > > Release candidates for 1.61.0 beta 1 are now available: > > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.zip > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.tar.bz2 > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.tar.gz > http://boost.cowic.de/rc/boost_1_61_0_b1_rc1.7z > > 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. > Packaging: The .gz file expanded to "boost_master_3a94cde635254f92fa87e0e11ef52d08684b8225", instead of "boost_1_61_0_b1" I successfully built the libraries with Apple's clang compiler. "Apple LLVM version 7.0.2 (clang-700.1.81)" with C++03, C++11, C++14, and c++1z I was not successful building the libraries with clang ToT. Boost.Python, in particular, had compile errors. I don't know if this is a problem in Boost.Python, or in libc++. (probably libc++) I will continue to investigate. In any case, I don't think that this should hold up the beta release. -- Marshall

3 3

[Fit] formal review ends 20th March.
by Vicente J. Botet Escriba 19 Mar '16

19 Mar '16

Hi, There have been some that would be able to write a review next week-end. Others said that they had not enough time. Maybe having an additional week can help. I have not received confirmation from the review withards, but as there is no planned reviews for this week, I propose to continue with the review until 20th. Please take the time to do a review and share your point of view. Best, Vicente Fit is a header-only C++11/C++14 library that provides utilities for functions and function objects. Fit is: - Modern: Fit takes advantages of modern C++11/C++14 features. It support both `constexpr` initialization and `constexpr` evaluation of functions. It takes advantage of type deduction, varidiac templates, and perfect forwarding to provide a simple and modern interface. - Relevant: Fit provides utilities for functions and does not try to implement a functional language in C++. As such, Fit solves many problems relevant to C++ programmers, including initialization of function objects and lambdas, overloading with ordering, improved return type deduction, and much more. - Lightweight: Fit builds simple lightweight abstraction on top of function objects. It does not require subscribing to an entire framework. Just use the parts you need. Fit is divided into three components: * Function Adaptors and Decorators: These enhance functions with additional capability. * Functions: These return functions that achieve a specific purpose. * Utilities: These are general utilities that are useful when defining or using functions Fit has been tested on gcc 4.6-4.9, clang 3.4-3.7, and Visual Studio 2015. For more information see: Github:https://github.com/pfultz2/Fit/tree/boost Documentation:http://pfultz2.github.io/Fit/doc/html/ We encourage your participation in this review. At a minimum, kindly state: - Whether you believe the library should be accepted into Boost * Conditions for acceptance - Your name - Your knowledge of the problem domain. You are strongly encouraged to also provide additional information: - What is your evaluation of the library's: * Design * Implementation * Documentation * Tests * Usefulness - Did you attempt to use the library? If so: * Which compiler(s) * What was the experience? Any problems? - How much effort did you put into your evaluation of the review? More information about the review process can be found here:http://www.boost.org/community/reviews.html

1 1

Boost graph library: brandes_betweenness_centrality() usage
by Sebastian Rinke 18 Mar '16

18 Mar '16

Dear all, I have a question regarding how to use the BGL brandes_betweenness_centrality() function for calculating the vertex betweenness centrality for a directed weighted graph. Below is my small example that fails to compile: —8>— /* Create graph */ typedef property<edge_weight_t, double> EdgeWeightProperty; typedef adjacency_list< vecS, // OutEdgeList vecS, // VertexList directedS, // Directed no_property, // VertexProperties EdgeWeightProperty // EdgeProperties > Graph; Graph graph(num_vertices); /* Add edges … */ std::vector<double> v_centrality_vec(num_vertices(graph), 0.0); // Create the external vertex centrality property map iterator_property_map<std::vector<double>::iterator, identity_property_map> v_centrality_map(v_centrality_vec.begin()); brandes_betweenness_centrality(graph, v_centrality_map, weight_map(get(edge_weight, graph))); —8>— The first compilation error I get is: boost_1_58_0/boost/graph/betweenness_centrality.hpp:248:7: error: no type named 'value_type' in 'struct boost::property_traits<boost::bgl_named_params<boost::adj_list_edge_property_map<boost::directed_tag, double, double&, long unsigned int, boost::property<boost::edge_weight_t, double>, boost::edge_weight_t>, boost::edge_weight_t, boost::no_property> >' centrality_type; ^ When using the following call instead, it compiles: brandes_betweenness_centrality(graph, v_centrality_map); I would be very grateful for any help on this issue. Best regards, Sebastian

1 0

Way to Promise the io_service.run() Is Running
by Bo Zhou 16 Mar '16

16 Mar '16

Hi ! I have a program which has a following logic 1. Start the UDP listening in daemon thread 2. Send the UDP command from main thread, and wait the response, maybe from the local So the program itself might also receive the message from second step. But the problem is, on Windows, the receiving thread will be executed before the main thread starts to send message, so the behaviour is correct. On Linux that's opposite, the main thread will be in deadlock because the 1st thread is not running and 2nd step it's trying to receive something after sending the command. My question, in the main thread of my application, what could I do to detect the io_service is running ? I tried to call m_io_services.stopped() seems the state is not correct, so I'd like to know how can I wait until the event loop in 1st step is running ? Thank you very much !

2 1

[Fit] About supported C++ version
by Vicente J. Botet Escriba 16 Mar '16

16 Mar '16

Hi, I was wondering if Boost.Fit shouldn't be a library as Boost.Hana, a library that makes use of the last C++ version and avoids as much portability issues as possible. Which C++14 features will make the library simpler? Which adopted C++17 features will make the library simpler? Which other C++ features would be missing? Paul I guess that you are using a C++11 compiler and want to support this version, could you confirm? Best, Vicente

2 3