- Boost-users - lists.preview.boost.org

Sean Parent to Keynote C++Now 2016
by Jon Kalb 22 Mar '16

22 Mar '16

Boost Users, C++Now is announcing that the keynote speaker for our tenth conference will be the keynote that started us off, Sean Parent. http://cppnow.org/2016-conference/announcements/2016/03/22/keynote-announced .html Jon

1 0

windows 10 support in boost
by Hinrich Aue 22 Mar '16

22 Mar '16

Hello, can anybody tell me if boost supports windows 10? And from which version? Hinrich Hinrich Aue Sr. Software Engineer Kofax Development GmbH Wentzinger Strasse 19 79106 Freiburg Germany Tel: +49 761 452 69 57234 Fax: +49 761 452 69 58734 Hinrich.Aue(a)kofax.com blog<http://www.kofax.com/blog/> | twitter<https://twitter.com/Kofax> | linkedin<https://www.linkedin.com/company/kofax> | facebook<https://www.facebook.com/kofax.inc> | talent network<http://www.jobs.net/jobs/Kofax-Inc/join> ________________________________ This communication is only for the use of the intended recipient. It may contain confidential or proprietary information. If you are not the intended recipient or have received this communication in error, please notify the sender via phone and destroy this communication immediately. Kofax Development GmbH Sitz der Gesellschaft: Freiburg i. Brg. Registergericht: Amtsgericht Freiburg i.Br. Registernummer: HRB 7007 Gesch?ftsf?hrer: Bradford Weller, Christian Hefner, Daniel Geiger

3 2

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

boost-mpi - Serious performance degradation with OpenMPI 1.10.1
by Nolen, Steven Douglas 16 Mar '16

16 Mar '16

My project has been using boost's mpi interface for a number of years and have recently encountered a significant performance obstacle moving to openmpi 1.10.1. We are seeing a factor of 7-10x slowdown in the communication portion of our calculation. Our communication patterns are mostly governed by all-to-one reductions and some all-to-all reductions. Colleagues who call mpi directly have not seen this behavior. We would be willing to work with someone to find a solution. Steve Nolen LANL

3 3

Using Boost.Geometry with Clang/LLVM & VC14
by degski 16 Mar '16

16 Mar '16

GGL does not compile with the combo of Clang/LLVM (http://llvm.org/builds/) and VC14 out of the box. There seem to be comflicts in the resolution of old MSVC bugs and Clang. On windows __clang__ is defined at the same time as _MSVC_VER. Undefining the macro _MSVC_VER before #include <boost/geometry/geometry.hpp> does however solve the problem (in my use case): file: boost/geometry.hpp // Boost.Geometry (aka GGL, Generic Geometry Library) // Copyright (c) 2007-2011 Barend Gehrels, Amsterdam, the Netherlands. // Copyright (c) 2008-2011 Bruno Lalande, Paris, France. // Copyright (c) 2009-2011 Mateusz Loskot, London, UK. // Parts of Boost.Geometry are redesigned from Geodan's Geographic Library // (geolib/GGL), copyright (c) 1995-2010 Geodan, Amsterdam, the Netherlands. // Use, modification and distribution is subject to the Boost Software License, // Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at // http://www.boost.org/LICENSE_1_0.txt) #ifndef BOOST_GEOMETRY_HPP #define BOOST_GEOMETRY_HPP #if defined(__clang__) && defined(_MSC_VER) #define __BOOST_GEOMETRY_MSVC_CLANG_WORKAROUND__ _MSC_VER #undef _MSC_VER #endif #include <boost/geometry/geometry.hpp> #if defined(__clang__) && defined(__BOOST_GEOMETRY_MSVC_CLANG_WORKAROUND__) #define _MSC_VER __BOOST_GEOMETRY_MSVC_CLANG_WORKAROUND__ #undef __BOOST_GEOMETRY_MSVC_CLANG_WORKAROUND__ #endif #endif // BOOST_GEOMETRY_HPP I've run into similar problems before (cannot remember where) with other boost libraries (which I hacked in other ways). Clang/LLVM with MSVC (and the IDE) works extremely well for a while now. The advantages of Clang/LLVM are well known, no need to spell them out It produces far faster code (almost twice as fast on simple matrix multiplication f.e.. It also gives the best of two worlds as it supports Clang and GCC extensions on Windows (calculated goto), while maintaining (although with a suppressable warning) M$ extensions as well, f.e. in-class template specialization. Clang/LLVM (3.9.0 as it stands) is much faster than Clang/CL2 (CodeGen) (3.7.0). I would herewith like to request the development team to integrate Clang/LLVM on Windows as another supported platform. Have good day to you all, degski -- (\___/) (+'.'+) (")_(") This is Bunny. Copy and paste Bunny into your signature to help him gain world domination!

3 5

Warning message using Boost.Atomic char pointer with GCC 4.8
by Isaac To 16 Mar '16

16 Mar '16

Hi all, It looks like Boost.Atomic (in Boost 1.60) uses constructs that GCC 4.8 (in CentOS 7) really dislike. With the following simple test program... #include <boost/atomic.hpp> int main() { boost::atomic<const char*> p1("abc"), p2; p2 = p1.load(); } What I see is: $ g++ -std=c++11 -I ~/opt/1/include t.cpp In file included from /home/foo/opt/1/include/boost/atomic/detail/atomic_template.hpp:25:0, from /home/foo/opt/1/include/boost/atomic/atomic.hpp:22, from /home/foo/opt/1/include/boost/atomic.hpp:12, from t.cpp:1: /home/foo/opt/1/include/boost/atomic/detail/bitwise_cast.hpp: In instantiation of ‘To boost::atomics::detail::bitwise_cast(const From&) [with To = long unsigned int; From = const char*]’: /home/foo/opt/1/include/boost/atomic/detail/atomic_template.hpp:426:139: required from ‘boost::atomics::detail::base_atomic<T*, void*>::base_atomic(T* const&) [with T = const char; boost::atomics::detail::base_atomic<T*, void*>::value_type = const char*]’ /home/foo/opt/1/include/boost/atomic/detail/atomic_template.hpp:686:101: required from ‘constexpr boost::atomics::atomic<T>::atomic(boost::atomics::atomic<T>::value_arg_type) [with T = const char*; boost::atomics::atomic<T>::value_arg_type = const char*]’ t.cpp:4:40: required from here /home/foo/opt/1/include/boost/atomic/detail/bitwise_cast.hpp:45:5: warning: casting ‘const char* const’ to ‘const char&’ does not dereference pointer [enabled by default] ); ^ The offending code is boost/atomic/detail/bitwise_cast.hpp:45, looking like this: &reinterpret_cast< const char& >(from) Here "from" is of type From = const char*. The code needs to find the address storing the pointer. It reinterprets the pointer as a const char reference, where address is to be found. In actual production code I use -Werror, so this stops the compiler from producing an executable. Most other warnings caused by Boost can be opted out, but apparently not this particular one. Should this be considered too funny a use of the C++ language to be considered a bug? For now I change the const char* to const void* with extra reinterpret_cast's, which the compiler won't complain about. Regards, Isaac

1 0

[Fit] function object variables and ADL
by Vicente J. Botet Escriba 14 Mar '16

14 Mar '16

Hi, Fit library make use of constexpr function object. These function objects don't work well when the user is requiring ADL and the same symbol is used. Next follows an example namespace N1 { struct F1 { void operator()(int) const {} }; constexpr F1 f; } namespace N2 { struct A{}; void f(A) {} } namespace N3 { struct A{}; void f(A) {} } The following find N3::f(A) { N3::A a; f(a); // calls N3::f(A) } Adding another namespace that doesn't introduce a better match works yet { N3::A a; using namespace N2; f(a); // calls N3::f(A) } However a namespace that contains a function object with the smae name even if overload doesn't match make the code ill-formed { N3::A a; using namespace N1; f(a); // compile fails } : error: reference to 'f' is ambiguous f(a); ^ : note: candidate found by name lookup is 'N1::f' constexpr F1 f; ^ : note: candidate found by name lookup is 'N3::f' void f(A) {} boost::fit contains a lot of such a function objects variables, so this means that the user should be careful while introducing the namespace boost::fit, as ADL will not be used for a lot of symbols. This is not something specific to Fit library, Hana and range-v3 make use of a lot of such global function objects. A good stryle will be to use Fit/Hana function objects always qualified with their respective namespapce or an alias. I believe it will be worth adding something in the documentation preventing the users of this case. Best, Vicente

1 0

iostreams: streambuf class fails to compile on type check
by Dan Bloomquist 14 Mar '16

14 Mar '16

I'm trying to insert my own stream buffer into a boost stream. Here is the code <http://hostcode.sourceforge.net/view/5044> At the top are two arbitrary streambuf derived classes I copied from the web that are said to work with the std::stream. They don't work either. My work is in the rtf namespace. In main there is a test with my device, file_source, and std::ifstream derived, they all work. Then I've tried the likes of: rtf::basic_stream< char, char_array_buffer > io_4( input ); rtf::basic_stream< char, outbuf > io_4( input ); and the one I want to work: rtf::basic_stream< char, rtf::rtf_stream_buffer > io_4( input ); they all fail at: { BOOST_STATIC_ASSERT(is_std_io<T>::value); } line 66 in concept_adapter.hpp. All the classes are derived from std::basic_streambuf which is on the list #ifndef BOOST_IOSTREAMS_NO_STREAM_TEMPLATES And I could not find it defined with agent ransack So, I seem to be missing something fundamental and just don't know what it could be. Thanks. Dan.

2 2

errors in polymorphic_iarchive_route.hpp:155 (boost version 1.60)
by Stack User 14 Mar '16

14 Mar '16

I get the following error when compiling code that uses boost version 1.60: In function `boost::archive::detail::polymorphic_iarchive_route<boost::archive::naked_binary_iarchive>::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)': /usr/include/boost/archive/detail/polymorphic_iarchive_route.hpp:155: undefined reference to `boost::archive::basic_binary_iprimitive<boost::archive::naked_binary_iarchive, char, std::char_traits<char> >::load(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&)' Seems like the error is coming from polymorphic_iarchive_route.hpp at line 155: virtual void load(std::string & t){ ArchiveImplementation::load(t); } Can anybody point to a solution for this error? Thanks,

2 1

[Fit] formal review ends today, 13th March.
by Vicente J. Botet Escriba 13 Mar '16

13 Mar '16

Hi, The formal review of Paul Fultz II's Fit library ends today, 13th March. If you had not time to do the review and you plan to do it, please let us know so that we see if the review can be extended. Up to now we had 3 formal review (2 for conditional acceptance and 1 against, not now). I have not done a review myself, but I have created a lot of issues on Github. Best regards, 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 We await your feedback!

1 0

boost karma qi: skipper concept
by Matwey V. Kornilov 13 Mar '16

13 Mar '16

Hello, I don't fully understand skip parser concepts. I would like to parse key-value list in bash style, like the following: KEY1=VAL1 KEY2="V A L 2" The pairs are separated by one or more space symbols. What is the supposed way to parse such constructions? 1. -(pair % (+space)) 2. *pair with skip=space 3. anything else?

1 0

[INTERPROCESS] Message queues with hex names - in Windows
by Davies, John 11 Mar '16

11 Mar '16

I'm refactoring some code that has a pretty good suite of unit tests. Or at least I think it does, since I wrote them<g>. I have a process that dispatches messages to one or more other processes that have their own message queues. It's just a switchboard. The refactored code works, and runs much faster than the test code I had written before. Much faster. And passes the unit tests. But in the process I see a bunch of stuff in the boost-interprocess folder with long hex names. They get cleaned up when the tests are done. It seems the long hex names come when I'm destructing the queues. So is it part of garbage collection? It only concerns me because other times I saw names like that it was because I was trying to make two input queues with the same name. Thanks, John ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

2 1

Trouble building boost with Visual Studio 2010 (32 vs 64 bit issue)
by David Aldrich 09 Mar '16

09 Mar '16

Hi I am trying to build Boost 1.60 with Visual Studio 2010 Professional on Windows 10. I use the command: b2 toolset=msvc-10.0 --with-python link=shared and get the following error: python34.lib(python34.dll) : fatal error LNK1112: module machine type 'x64' conflicts with target machine type 'X86' I guess this means I have a conflict of 32-bit and 64-bit libraries. I want to target 32-bit (X86). Do I need to install a 32-bit version of Python? I wonder if that can co-exist with the current version of Python? Best regards David

3 2

Boost python - pointers
by Daniel Burchardt 09 Mar '16

09 Mar '16

Hi, I have problem with pointer in function return. My code: using namespace boost::python; v8::Platform* InitializePlatform() { v8::Platform* platform = v8::platform::CreateDefaultPlatform(); return platform; } BOOST_PYTHON_MODULE(hello) { def("InitializePlatform", InitializePlatform, return_value_policy<manage_new_object>()); } Python code: import hello x = hello.InitializePlatform() Building is ok, but when i try call InitializePlatform i have error: Segmentation fault gdb: (gdb) run test.py Starting program: /usr/bin/python test.py [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x7ffff45b8700 (LWP 21739)] Program received signal SIGSEGV, Segmentation fault. 0x00007ffff4924640 in __dynamic_cast () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6

1 0

numeric_cast<float> throws for double infinity
by Dmitry Volosnykh 09 Mar '16

09 Mar '16

When I try to cast variable of type double (which is equal to std::numeric_limits<double>::inifinity()) to float I get exception: std::bad_cast: bad numeric conversion: positive overflow. I expected to get std::numeric_limits<float>::inifinity(). The same is true for negative infinity. Is it intended behavior or bug? In case this should be considered as bug, maybe it was fixed in more recent versions of Boost? PS. I am using stock Boost 1.54 on Ubuntu 14.04 Regrads, Dmitry.

1 0

Re: [Boost-users] [boost] [Fit] formal review starts today
by Paul Fultz II 09 Mar '16

09 Mar '16

On Monday, March 7, 2016 at 2:52:09 AM UTC-6, Edward Diener wrote: > > On 3/7/2016 12:15 AM, Paul Fultz II wrote: > > > > > > On Sunday, March 6, 2016 at 9:42:19 PM UTC-6, Edward Diener wrote: > >> > >> On 3/3/2016 6:43 AM, Vicente J. Botet Escriba wrote: > >>> 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. > >> > >> These are some comments/queries about the Fit documentation. > >> > >> Introduction > >> > >> The introduction says that Fit "provides utilities for functions and > >> function objects." But it seems as if Fit works only with lambda > >> functions and function objects. > > > > > > Fit works with any generalized Callable: > > > > http://en.cppreference.com/w/cpp/concept/Callable > > Please document this. A generalized Callable is a much bigger set of > functionality than just lambda functions and function objects. > > > > > > >> The term 'function' normally encompasses > >> a much larger definition in C++ which includes global functions, static > >> functions, member functions, and lambda functions. > > > > > > Which is what Callable encompasses, but I used "function" since more > > people are familiar with that than Callable. > > A 'function' and a Callable in C++ are two entirely different things. > Use the one that is precise and don't worry what people are familiar > with. Explain what a Callable is early on ( I know you explain it later > ) if you feel that people do not know what it means. > > > > > > >> Fit needs to be more > >> precise in what it says it works with. It repeatedly refers to function > >> objects and lambda functions as 'functions'. I think this vagueness of > >> terminality is really confusing in the documentation. > >> > > > > Perhaps, I should refer to the Callable concept early on then. > > See above. > > > > > > >> > >> Quick Start:Function Objects > >> > >> "We can make it behave like a regular function if we construct the > class > >> as a global variable." > >> > >> What about a non-global > >> > >> sum_f sum = sum_f(); > >> > >> makes 'sum' not behave like a regular function other than the fact that > >> the variable 'sum' may eventually go out of scope ? > >> > > > > In C++, a regular function is always global, there is no such thing as > local > > function(sans gcc extensions). > > My point is that the non-global 'sum' in my example above behaves just > as much like a regular function as your global 'sum'. You may want to > promote the idea of global function objects but I think that this is > personally a bad idea. IMO global variables of any kind are to be avoided. It is quite common in several modern C++ libraries to declare functions as global objects. There are many advantages to this. Why do you believe it should be avoided? Especially since it has the same effect as a free function. DO you believe free function should be avoided as well? > > > > > > > >> > >> Quick Start:Lambdas > >> > >> Why do we need both BOOST_FIT_STATIC_LAMBDA and > >> BOOST_FIT_STATIC_LAMBDA_FUNCTION ? I would seem that > >> BOOST_FIT_STATIC_LAMBDA_FUNCTION would be adequate and > >> BOOST_FIT_STATIC_LAMBDA is just redundant, mimicking lambda syntax to > no > >> purpose. > >> > > > > BOOST_FIT_STATIC_LAMBDA_FUNCTION and BOOST_FIT_STATIC_FUNCTION both > define a > > function at global scope, and can only be used at global scope, whereas > > BOOST_FIT_STATIC_LAMBDA can be used to constexpr initialize local > variables > > as > > well. > > It might be good to add that when the end-user first encounters > BOOST_FIT_STATIC_LAMBDA, because the name does not suggest > initialization of local objects. Furthermore I cannot imagine why one > would want to use it to initialize a local object, Really? You just said that you would prefer avoiding global functions. > so you might want to > explain the benefit of doing so as opposed to the normal syntax for > creating a lambda function. > Maybe the quick start guide isn't the place for this in the first place. > > > In fact, BOOST_FIT_LIFT uses this since it is not always clear what > > context the user might call BOOST_FIT_LIFT. > > > > > >> > >> Quick Start:Overloading > >> > >> The overloading adaptors show two or more lambda functions. Can they > >> also work with function objects ? Or a mix of lambda functions and > >> function objects ? In fact all the reamining Quick Start topics show > >> examples with lambda functions. Do they also work with function objects > ? > >> > > > > Yes it can be used with function objects. I probably should show an > example > > of > > that as well. I used the lambdas because of the terseness of them. > > Evidently the adaptors can be used with any Callable. I think you should > make that point very strongly and show that in examples also. > Agreed. > > > > > > >> > >> Quick Start:Variadic > >> > >> I do not understand what 'We can also make this print function > varidiac, > >> so it prints every argument passed into it.' means ? > >> > > > > I'll try to explain that better, but basically it will print each > argument, > > so: > > > > print("hello", 5); // Will print "hello" and 5 > > I wouldn't associate that with the word 'Variadic' but I do think you > need to explain that more clearly. > I always understood variadic to mean taking a variable number of arguments. What do you understand variadic to mean? > > > > > > >> > >> I do not think the Quick Start explains very much since it is dealing > >> with adaptors of which we know almost nothing and the explanation for > >> these adaptors and what they actually do is very terse. > > > > > > Probably can expand the explanation of adaptors a little more. > > Good idea. What do adaptors create ? They create a function. > Different function objects I would > imagine ? In that case how about the explanation that adaptors take > Callables as input and generate function object types that adapt the > original functionality of one or more Callables to some other purpose. > The examples are already show taking Callables. Are you suggesting I show an example taking a member function or something? > > > > >> > >> In the 'Signatures' section of the Overview I read: > >> > >> "All the functions are global function objects except where an explicit > >> template parameter is required." I honestly don't know what this is > >> supposed to mean. Does this refer to when function objects are referred > >> to as parameters to the adaptors, functions, and utilities of the > library > >> ? > >> > > > > I don't understand what you are asking. It means that the function is > > written > > like this in the documentation: > > > > template<class IntegralConstant> > > constexpr auto if_(IntegralConstant); > > > > But its actually a function object like this in the code: > > > > struct if_f > > { > > template<class IntegralConstant> > > constexpr auto operator()(IntegralConstant) const; > > }; > > const constexpr if_f if_ = {}; > > > > However, `if_c` is written like this in the documentation: > > > > template<bool B, class F> > > constexpr auto if_c(F); > > > > It requires the bool `B` template parameter explicity. So in the code it > is > > written as a function and not as a function object. > > I don't understand to what you are referring when you say 'function'. > Are you talking about adaptors in your library, functions in your > library, or what ? I am talking about all functions that are defined in the library, that includes adaptors as well. I am not sure how to make that clearer. > Please try to understand that your use of the word > 'function' is very broad but that the word 'function' in C++ has a much > narrower meaning. > By function, I mean something like in the example: template<class IntegralConstant> constexpr auto if_(IntegralConstant); I think everyone agrees that is a function in C++.

5 5

Command Line Options Questions
by Jon Lederman 09 Mar '16

09 Mar '16

Hi, I have two questions re: the boost command line options library: 1) I am compiling a dynamic library that links to the boost command line options library as a shared library. When I try to unload the dynamic library, I find that it isn’t properly unloaded and the boost library seems to be causing the issue. I did find that things were helped somewhat when I linked to the boost static libraries. However, it still feels unstable. Are there any particular things I should know about in this context in terms of how my makefile should be linking to boost? Or are there other things I should look at. 2) When using program options, I am getting the following error. For some reason this seemed to work with the dynamic libraries (or it may be a coincidence). Am I required to implement the << and >> operators? It had been compiling previously and stopped. After googling this issue there seems to be a lot of confusion. Any help would be greatly appreciated. in file included from /usr/include/boost/any.hpp:27:0, from /usr/include/boost/program_options/value_semantic.hpp:12, from /usr/include/boost/program_options/options_description.hpp:13, from /usr/include/boost/program_options.hpp:15, from /usr/local/src/freeswitch/src/mod/applications/mod_sc_dsp/mod_sc_dsp.cpp:23: /usr/include/boost/lexical_cast.hpp: In instantiation of 'struct boost::detail::deduce_target_char_impl<boost::detail::deduce_character_type_later<dsp_type> >': /usr/include/boost/lexical_cast.hpp:415:89: required from 'struct boost::detail::deduce_target_char<dsp_type>' /usr/include/boost/lexical_cast.hpp:674:92: required from 'struct boost::detail::lexical_cast_stream_traits<std::basic_string<char>, dsp_type>' /usr/include/boost/lexical_cast.hpp:2363:19: required from 'static Target boost::detail::lexical_cast_do_cast<Target, Source>::lexical_cast_impl(const Source&) [with Target = dsp_type; Source = std::basic_string<char>]' /usr/include/boost/lexical_cast.hpp:2543:50: required from 'Target boost::lexical_cast(const Source&) [with Target = dsp_type; Source = std::basic_string<char>]' /usr/include/boost/program_options/detail/value_semantic.hpp:89:38: required from 'void boost::program_options::validate(boost::any&, const std::vector<std::basic_string<charT> >&, T*, long int) [with T = dsp_type; charT = char]' /usr/include/boost/program_options/detail/value_semantic.hpp:170:55: required from 'void boost::program_options::typed_value<T, charT>::xparse(boost::any&, const std::vector<std::basic_string<charT> >&) const [with T = dsp_type; charT = char]' /usr/local/src/freeswitch/src/mod/applications/mod_sc_dsp/mod_sc_dsp.cpp:484:1: required from here /usr/include/boost/lexical_cast.hpp:388:13: error: static assertion failed: Target type is neither std::istream`able nor std::wistream`able BOOST_STATIC_ASSERT_MSG((result_t::value || boost::has_right_shift<std::basic_istream<wchar_t>, T >::value), desc.add_options() ("help", "Generates help message") ("dsp_type", po::value<dsp_type>(&params.dsp_type)->required(), “") where dsp_type is this: struct dsp_type { dsp_type() {} dsp_type(std::string const& val): value(val) { } std::string value; }; and I have a validator defined as this: void validate(boost::any& v, std::vector<std::string> const& values, dsp_type* /* target_type */, int) { using namespace boost::program_options; //namespace po = boost::program_options; // Make sure no previous assignment to 'v' was made. validators::check_first_occurrence(v); // Extract the first string from 'values'. If there is more than // one string, it's an error, and exception will be thrown. std::string const& s = validators::get_single_string(values); if (s == "ladspa" || s == "audioweaver" || s == "gstreamer" || s == "lv2") { v = boost::any(dsp_type(s)); } else { throw validation_error(validation_error::invalid_option_value); } } /usr/local/src/freeswitch/build/modmake.rules:214: recipe for target 'mod_sc_dsp.lo' failed make[1]: *** [mod_sc_dsp.lo] Error 1

3 4

[Fit] review - ends next 13th Mars
by Vicente J. Botet Escriba 08 Mar '16

08 Mar '16

Hi, we are on the middle of the Fit review stated on 2 Mars and that ends 13th Mars. We have not received a lot of comments, only 4 or 5 people have commented and only a formal review (reject now). I understand that the documentation needs a lot of improvements, nevertheless, this review is the occasion to give as much feedback as possible. If you want to improve this library, please take the time to do a review and share your point of view. Best, Vicente

1 0

Re: [Boost-users] [boost] [Fit] formal review starts today
by Paul Fultz II 07 Mar '16

07 Mar '16

On Sunday, March 6, 2016 at 9:42:19 PM UTC-6, Edward Diener wrote: > > On 3/3/2016 6:43 AM, Vicente J. Botet Escriba wrote: > > 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. > > These are some comments/queries about the Fit documentation. > > Introduction > > The introduction says that Fit "provides utilities for functions and > function objects." But it seems as if Fit works only with lambda > functions and function objects. Fit works with any generalized Callable: http://en.cppreference.com/w/cpp/concept/Callable > The term 'function' normally encompasses > a much larger definition in C++ which includes global functions, static > functions, member functions, and lambda functions. Which is what Callable encompasses, but I used "function" since more people are familiar with that than Callable. > Fit needs to be more > precise in what it says it works with. It repeatedly refers to function > objects and lambda functions as 'functions'. I think this vagueness of > terminality is really confusing in the documentation. > Perhaps, I should refer to the Callable concept early on then. > > Quick Start:Function Objects > > "We can make it behave like a regular function if we construct the class > as a global variable." > > What about a non-global > > sum_f sum = sum_f(); > > makes 'sum' not behave like a regular function other than the fact that > the variable 'sum' may eventually go out of scope ? > In C++, a regular function is always global, there is no such thing as local function(sans gcc extensions). > > Quick Start:Lambdas > > Why do we need both BOOST_FIT_STATIC_LAMBDA and > BOOST_FIT_STATIC_LAMBDA_FUNCTION ? I would seem that > BOOST_FIT_STATIC_LAMBDA_FUNCTION would be adequate and > BOOST_FIT_STATIC_LAMBDA is just redundant, mimicking lambda syntax to no > purpose. > BOOST_FIT_STATIC_LAMBDA_FUNCTION and BOOST_FIT_STATIC_FUNCTION both define a function at global scope, and can only be used at global scope, whereas BOOST_FIT_STATIC_LAMBDA can be used to constexpr initialize local variables as well. In fact, BOOST_FIT_LIFT uses this since it is not always clear what context the user might call BOOST_FIT_LIFT. > > Quick Start:Overloading > > The overloading adaptors show two or more lambda functions. Can they > also work with function objects ? Or a mix of lambda functions and > function objects ? In fact all the reamining Quick Start topics show > examples with lambda functions. Do they also work with function objects ? > Yes it can be used with function objects. I probably should show an example of that as well. I used the lambdas because of the terseness of them. > > Quick Start:Variadic > > I do not understand what 'We can also make this print function varidiac, > so it prints every argument passed into it.' means ? > I'll try to explain that better, but basically it will print each argument, so: print("hello", 5); // Will print "hello" and 5 > > I do not think the Quick Start explains very much since it is dealing > with adaptors of which we know almost nothing and the explanation for > these adaptors and what they actually do is very terse. Probably can expand the explanation of adaptors a little more. > I realize that > is why it is called a 'Quick Start' is because it is just giving the > end-user a quick review of the sort of functionality that the library > entails, but I would much rather see a good Overview first before I look > at anything else in the documentation. > > More Examples > > The more examples section looks at useful cases for the library. Since I > haven't had an overview for the library yet it is disappointing that > this section comes before I really understand how the library is > organized with at least general functionality. I am now given a series > of some highly complicated library syntax without the least idea of why > any of this syntax should be as it is, what it means, or how it works. > That doesn't convince me to use the library at all. It just convinces me > that the library has some showy functionality which does clever things > for particular use cases which the library author wants to convince me I > am going to encounter in my own programming. > Probably more explanation about each of the components used to build the example will be helpful. > > Overview > > The overview section consists of explaining what a function adaptor, > static function adaptor, and decorator are. It also give me some notes > about the syntax of the documentation. I would call this section > 'Definitions' and "Documentation Syntax'. One thing it is not is an > overview of the Fit library as far as I can understand what an overview > is. I also note that following large scale sections deal in Adaptors, > Decorators, Functions, and Utilities. Since 'Functions' and 'Utilities' > are not "defined" in this Overview I am left to wonder if 'Functions' > and 'Utilities' just mean anything in the library which is not an > adaptor or a decorator, and what distinguishes a function from a utility. > This is a good point, the current overview should be called "Definitions". > > In the 'Signatures' section of the Overview I read: > > "All the functions are global function objects except where an explicit > template parameter is required." I honestly don't know what this is > supposed to mean. Does this refer to when function objects are referred > to as parameters to the adaptors, functions, and utilities of the library > ? > I don't understand what you are asking. It means that the function is written like this in the documentation: template<class IntegralConstant> constexpr auto if_(IntegralConstant); But its actually a function object like this in the code: struct if_f { template<class IntegralConstant> constexpr auto operator()(IntegralConstant) const; }; const constexpr if_f if_ = {}; However, `if_c` is written like this in the documentation: template<bool B, class F> constexpr auto if_c(F); It requires the bool `B` template parameter explicity. So in the code it is written as a function and not as a function object. > > The rest of the general About section is fairly straightforward. I still > have no idea of the general functional of the library and why I should > use it. I will only gain an idea of what the library does by reading the > specifics of each adaptor, decorator, function, and utility. This seems > to be the gist of the documentation to me. If I want to understand what > the library does for me in working with function objects and lambda > functions I have to read the specific documentation of each entity in > the library and then go back to the Quick Start and More Examples > sections to further understand how some of these entities are used. > > I think the library documentation would have been much better if there > were a discussion of what the adaptors, decorators, functions, and > utilities of the library were meant to do to enhance user programming > rather than give examples here and there of usage and then leave it up > to the end-user to figure out what, why, and how these entities are to > be used. Quite frankly I don't have a use for a library that does not > attempt to present itself as offering functionality that would be useful > for me in the domain in which the library operates. if I have little or > no idea of that domain I see no reason to think of using a library. > > Since Boost has a number of other libraries dealing with function > objects, most notable the Boost Phoenix library, which is a sort of > successor to the Boost Lambda library, I would think it would be > advantage to the library author to stress functionality in the Fit > library which goes beyond, improves on, or is different from the > functionality in Boost Phoenix, in order to 'sell' end-users on the use > of the Fit library in their code. I do realize that the Fit library > deals with C++11/C++14 idioms, which means that it may be difficult for > many end-users to understand, but I don't think it presents its > documentation in such a way that makes its functionality easier to > understand and I think it should do so. This does not mean that I will > vote right now for Fit to be accepted or not accepted as a Boost > library. I have to look much more carefully at the individual > functionality of the adaptors, decorators, functions, and utilities of > the library to understand what it actually does, before I can vote one > way or another. But I hope my comments and questions about the > documentation to the library will aid the library author in improving > the documentation for end users like me, who are very interested in > library enhancements to function object/lambda function functionality, > but who find the documentation difficult and limiting in certain ways. > Thanks for your feedback, and it will be very helpful in improving the documentation.

1 0

Re: [Boost-users] [boost] [Fit] formal review - should we propose some parts to Boost.Config/Boost.Core
by Vicente J. Botet Escriba 07 Mar '16

07 Mar '16

Le 06/03/2016 09:59, Andrey Semashev a écrit : > On 2016-03-06 05:21, Vicente J. Botet Escriba wrote: >> >> Others could be considered also as function.hpp, lambda.hpp and >> lift.hpp, as the macros are there to workaround some missing language >> features, but those are much more specialized (Boost.Core?) > > I don't think Boost.Core is the right place for them as this library > is for small generally useful components used by many libraries. The > components you pointed out seem too specialized to me, and Boost.Fit > looks like the right place for them. > |Andrey, I was thinking in Boost.Core as these are language-like emulation features, like e.g. addressof, enable_if, explicit_operator_bool, ignorunused, no_exception_support, noncopyanble, scoped_enum, typeinfo. IIUC, BOOST_FIT_STATIC_FUNCTION try to fix a standard Core issue (pending issue 2104 in CWG) identified by Eric Nibler, with the a solution based on proposal's Eric (http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2015/n4381.html) The library has also a macro BOOST_FIT_DECLARE_STATIC_VAR to do it for any data variable. I would like something that solves this problem in Boost. BOOST_FIT_STATIC_LAMBDA try to covers the C++17 feature constexpr lambdas. I suspect that Boost.Hana should have something like that. Louis, could you tell us how do you manage with these issues? IMO, The fiw of those issues is independent from a functional utilities library, even if Fit can not work without them.|| This is way I believe that it should be extracted and Boost.Core seems the good place to me. Best, Vicente |

3 3

Visual Studio C++ and Boost Multiprecision float128
by Michel Lamoureux 06 Mar '16

06 Mar '16

Hi, I use « Visual Studio Express 2013 for Desktop » to do my C++ programming. When I come tu use Boost Multiprecision header « float128.hpp », I get the following message : Fatal error C1189 : #error : « Sorry compiler is neither GCC, not Intel, don’t know how to configure this header. » However, when I use Boost Multiprecision header « cpp_dec_float », it works well but much slowly. I guess « float128.hpp » is faster : Am I right? Is it possible to fix « float128.hpp » to suit C++ from Visual Studio? Thank you for your answer. Michel Lamoureux Envoyé par Courrier<https://go.microsoft.com/fwlink/?LinkId=550986> pour Windows 10

2 1

[Fit] review - github issuess
by Vicente J. Botet Escriba 06 Mar '16

06 Mar '16

Hi, we have started to create some issues in https://github.com/pfultz2/Fit/issues, and sometimes there are some interesting discussion. I will try to add post on the MLs the issues that are conflicting so that other are aware of the discussion. Anyway, if you are curious you can always take a look at and participate also. If you want to receive the updates I believe that you just need to click on watch (top right). Best, Vicente

1 0

Re: [Boost-users] [boost] [Fit] formal review - should we propose some parts to Boost.Config/Boost.Core
by Glen Fernandes 06 Mar '16

06 Mar '16

On Sat, Mar 5, 2016 at 9:21 PM, Vicente J. Botet Escriba wrote: > Others could be considered also as function.hpp, lambda.hpp and lift.hpp, as > the macros are there to workaround some missing language features, but those > are much more specialized (Boost.Core?) > Boost.Core is where we move code from existing Boost libraries that enables breaking cyclic dependencies between different Boost libraries. I'm not so sure new libraries will need to (or want to) put code there. Glen

1 0

Boost.Spirit Karma: debug() alters result
by Matwey V. Kornilov 05 Mar '16

05 Mar '16

Hello, I am using boost 1.58 and I see the following. template <class Iterator> struct test_generator: karma::grammar<Iterator, std::string()> { test_generator(): test_generator::base_type(start) { using karma::ascii::string; using boost::spirit::ascii::char_; using karma::lit; using karma::buffer; using karma::debug; value2 = +(~char_(' ')); value1 = value2; value = lit('=') << value1; start = buffer[-value]; } karma::rule<Iterator, std::string()> start; karma::rule<Iterator, std::string()> value; karma::rule<Iterator, std::string()> value1; karma::rule<Iterator, std::string()> value2; }; template <class Iterator> struct test_generator2: karma::grammar<Iterator, std::string()> { test_generator2(): test_generator2::base_type(start) { using karma::ascii::string; using boost::spirit::ascii::char_; using karma::lit; using karma::buffer; using karma::debug; value2 = +(~char_(' ')); value1 = value2; value = lit('=') << value1; debug(value); start = buffer[-value]; } karma::rule<Iterator, std::string()> start; karma::rule<Iterator, std::string()> value; karma::rule<Iterator, std::string()> value1; karma::rule<Iterator, std::string()> value2; }; template<class It> bool do_generate(It it, const std::string& x) { test_generator<It> g; return karma::generate(it, g, x); } template<class It> bool do_generate2(It it, const std::string& x) { test_generator2<It> g; return karma::generate(it, g, x); } //... std::string x2,x3; do_generate(std::back_inserter(x2), std::string("")); do_generate2(std::back_inserter(x3), std::string("")); std::cerr << "|" << x2 << "|" << std::endl; std::cerr << "|" << x3 << "|" << std::endl; //... The code prints: <unnamed-rule> <try> <attributes>[[]]</attributes> </try> <fail/> </unnamed-rule> |=| || I.e. introduction of debug() alters result of the generator. Could you please explain me where I am wrong? I am stuck now.

2 3

[Fit] upcoming formal review for Boost.Fit
by Vicente J. Botet Escriba 05 Mar '16

05 Mar '16

Dear Boost community, The formal review of Paul Fultz II's Fit library starts on Wednesday, 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, variadic 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/ Note that, as Fit is a functional library, the semantic of the functions is given in the form of `equations` instead of the classic effects, returns schema. This is because most of the functions have no side effects. E.g. the semantic of the function flip is defined as |assert(flip(f)(x, y, xs...) == f(y, x, xs...));| and the semantic of compose as |assert(compose(f, g)(xs...) == f(g(xs...)));| We await your feedback! Best regards, Vicente J. Botet Escriba P.S. Paul, now it is time to freeze the version that will be reviewed. I suggest you to create a branch on which you could fix the review issues.

6 11

[Preprocessor] MSVC nonstandard macro expansion workaround?
by rleigh＠codelibre.net 04 Mar '16

04 Mar '16

Hi folks, I've been trying to get Boost.Preprocessor to run a nested for loop over two sequences to output nested switch blocks and case statements. This works fine with GCC and clang. Unfortunately it's broken with MSVC. If anyone had any thoughts on what I might need to tweak to enable the code to work with MSVC, I'd be very appreciative. Even if it's as nasty as a big ifdef with an alternative set of macros! This is the test case: -------- #include <boost/preprocessor.hpp> #include <iostream> #define LASERTYPE_VALUES (EXCIMER)(GAS)(METALVAPOR)(SOLIDSTATE)(DYE)(SEMICONDUCTOR)(FREEELECTRON)(OTHER) enum LaserType { BOOST_PP_SEQ_ENUM(LASERTYPE_VALUES) }; #define PP_SEQ_FOR_EACH_R_ID() BOOST_PP_SEQ_FOR_EACH_R #define PP_DEFER(x) x BOOST_PP_EMPTY() #define LT_NESTED(maR, maToplevelType, maNestedType) \ std::cout << "Test nested: first=" << LaserType(maToplevelType) << " second=" << LaserType(maNestedType) << " \n"; #define LT_TOPLEVEL(maR, maUnused, maType) \ std::cout << "Test toplevel: " << LaserType(maType) << " \n"; \ PP_DEFER(PP_SEQ_FOR_EACH_R_ID)()(maR, LT_NESTED, maType, LASERTYPE_VALUES); int main() { BOOST_PP_EXPAND(BOOST_PP_SEQ_FOR_EACH(LT_TOPLEVEL, %%, LASERTYPE_VALUES)); } -------- On MSVC, I get this: > cl /EHsc /I \path\to\boost-1_60 /Fe:test-pp.exe test-pp.cpp Microsoft (R) C/C++ Optimizing Compiler Version 18.00.40629 for x64 Copyright (C) Microsoft Corporation. All rights reserved. test-pp.cpp test-pp.cpp(22) : warning C4003: not enough actual parameters for macro 'BOOST_PP_VARIADIC_ELEM_3' test-pp.cpp(22) : warning C4003: not enough actual parameters for macro 'BOOST_PP_BOOL' test-pp.cpp(22) : warning C4003: not enough actual parameters for macro 'BOOST_PP_BOOL_I' test-pp.cpp(22) : warning C4003: not enough actual parameters for macro 'BOOST_PP_VARIADIC_ELEM_2' test-pp.cpp(22) : warning C4003: not enough actual parameters for macro 'BOOST_PP_DEC' test-pp.cpp(22) : warning C4003: not enough actual parameters for macro 'BOOST_PP_DEC_I' test-pp.cpp(22) : error C2065: 'BOOST_PP_SEQ_FOR_EACH_M' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_TUPLE_EAT_2' : undeclared identifier test-pp.cpp(22) : error C2065: 'LT_NESTED' : undeclared identifier test-pp.cpp(22) : error C2064: term does not evaluate to a function taking 1 arguments test-pp.cpp(22) : error C2146: syntax error : missing ';' before identifier 'BOOST_PP_IIF_BOOST_PP_BOOL_' test-pp.cpp(22) : error C3861: 'BOOST_PP_IIF_BOOST_PP_BOOL_': identifier not found test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_3' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_TUPLE_EAT_4' : undeclared identifier test-pp.cpp(22) : error C2059: syntax error : ',' test-pp.cpp(22) : error C3861: 'BOOST_PP_EXPAND': identifier not found test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_4' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_5' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_6' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_7' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_8' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_9' : undeclared identifier test-pp.cpp(22) : error C2065: 'BOOST_PP_FOR_10' : undeclared identifier I've spent hours tweaking the testcase to try to make this work, but so far without success. It doesn't help that I don't fully understand what specifically is broken with the MSVC preprocessor, or how to work around whatever is behaving in a non-stanadard way. Many thanks, Roger

5 5

PBGL in shared memory
by Ярослав 04 Mar '16

04 Mar '16

Hi guys, I need to write some graph parallel algorithms and I decided to use boost graph library for this. There are also PBGL. So my question is, is PBGL works great in shared memory environment. My algorithms will be used in a competition, so I know that it will be launched on a single machine, but with quite high number of cores. Is it worth to use sequential BGL with OpenMP or something, PBGL can handle shared memory and prevent overhead from copying data from one process space to another (as I get it is using MPI)?

2 1

Turning Boost.Multi-Index ordered_non_unique index into ordered_unique one, with custom comparator
by Dominique Devienne 03 Mar '16

03 Mar '16

I would like to support a slightly unusual use-case. We have a class with a integer member, and a BMI container for instances of this class. That member is supposed to be unique, *except* for a special "invalid" value (-1), which several instances can use. Right now, we use an ordered_non_unique index, because of the -1's, but that leaves the door open for other duplicate "valid" values, which should be forbidden. So my question is whether one can index this member uniquely, thanks to a custom comparator, such that the comparator does not violate the usual strict-weak-ordering requirement of ordered containers? I'm thinking kinda like SQL NULLs, which don't compare equal to each other, i.e. in this case -1 would never equal another -1, and use another arbitrary (but stable) ordering specifically for those -1's. This assumes though I can know which instance the int member is part of, i.e. will the comparator get the integer by value or reference, and if a reference, is that a reference to the "internal" element, such that the arbitrary order can be the address of the element for example? Or to avoid element movement in case of reallocs in the container, can the comparator access an iterator to project it into another random-access index of the same container, to use that index's integer-index as the arbitrary order? I'd appreciate some feedback/insights into the above. Thanks, --DD

4 7

Boost.Spirit Karma: Alternative generator
by Matwey V. Kornilov 03 Mar '16

03 Mar '16

Hello, I am construction karma::rule<OutputIterator, std::string()> which I would like to be either a string or quoted string if the string contains spaces. Now I think that the rule should be something like: rule = (&true[...] << string) | (lit("\"") << string << lit("\"")); but I've failed to write proper semantic action. How could I obtain std::string object reference to write something like: (obj.find(" ") == std::string::npos) ? Or maybe is there a better way to do the same?

2 2

[gsoc16] An update on GSoC 2016 contingency plans
by Niall Douglas 03 Mar '16

03 Mar '16

Dear Boost, We've been collecting a list of veteran Summer of Code students where "veteran" means students whom have previously done a Google Summer of Code for Boost. It /may/ be possible for us to acquire enough funding from a number of contributors to tide over ongoing GSoC projects this summer during our year off from Google funding for veteran students only. The stipend to the student would be the same as with Google, $5,500. The mentor stipend would likely need to be waived under any substitute programme. We would therefore appreciate an update from student and/or mentor as to whether they were intending to submit a continuing GSoC this summer and would be willing to continue work on their Boost library under any funding we find. If we have forgotten any students or projects, please get in touch. Extant ongoing summer of code projects known to us are (please send corrections of any mistakes): * Boost Document, mentored by Antony Polukhin. https://anuragxel.github.io/boost-document/ Student: Anurag Ghosh Status: Not peer reviewed * Boost.Compute, mentored by Kyle Lutz. https://boostorg.github.io/compute/ Student: Jakub Szuppe Status: Official Boost library * Boost.Hana, mentored by Joel Falcou. https://boostorg.github.io/hana/ Student: Louis Dionne Status: Official Boost library * Boost.Http, mentored by Bjorn Reese. https://boostgsoc14.github.io/boost.http/ Student: Vinícius dos Santos Oliveira Status: One peer review held * Boost.Fixed-Point, mentored by Paul Bristow. https://github.com/BoostGSoC15/fixed_point Student: Nikhar Agrawal Status: Not peer reviewed We are aware of the following Boost libraries who have strong but new-to-Boost potential student candidates in the pipeline for summer of code 2016: * Boost.odeint, mentored by Karsten Ahnert and Mario Mulansky There is even less chance we can find funding for these, but if any of the veteran students or mentors has to suddenly pull out before the summer, we would substitute one of these projects instead. Therefore, if mentors had a really excellent student lined up for 2016, please let us know. None of the above should be read that summer of code 2016 is going ahead. We just need some hard numbers with which to lobby for funding. We will get back to the community as soon as we know more. We need all this information requested above back BEFORE this weekend as we will be making use of the Jacksonville ISO WG21 meeting currently happening to grab the right people to ask them for donations from their corporate bodies. If YOUR corporate org would be willing to help sponsor a summer of code student, either partially or in full, PLEASE get in touch. Donations to Boost are tax deductible for US taxpayers. Thank you all very much in advance! Niall --- Boost C++ Libraries Google Summer of Code 2016 admin https://svn.boost.org/trac/boost/wiki/SoC2016

2 1

boost::asio::read_until Segmentation Fault & Third Party Signal Handler
by Craig, Tom 01 Mar '16

01 Mar '16

My Linux application sis using bool::asio::read_until() to read data from a socket. The application also uses commercial, 3rd party hardware. Occasionally my program crashes due to a SIGSEGV violation. The core dump stack trace is shown below. It indicates that the 3rd party signal handler is invoked while my thread is waiting for socket I/O, and that the crash is occurring during signal handler execution. While I recognize that this is an issue with the 3rd party vendor (and I am currently engaged in discussions with them), I'm wondering if my usage of boost is incorrect, or if there is something that I should be doing differently in performing socket I/O? I am using boost v1.43. [cid:image001.png@01D17303.98B2DD10] E. Thomas Craig Principal Software Engineer SWIFT Division KLA-Tencor Corporation 408-875-7909 (work) 650-799-4787 (cell)

3 3

Boost.Spirit. Karma: Kleene star with space separator
by Matwey V. Kornilov 01 Mar '16

01 Mar '16

Hello There is an example of usage Keele star with Karma generator: http://www.boost.org/doc/libs/1_60_0/libs/spirit/doc/html/spirit/karma/refe… std::vector<double> v; v.push_back(1.0); v.push_back(2.0); v.push_back(3.0); test_generator_attr_delim("1.0 2.0 3.0 ", *double_, space, v); How could the remaining space be omitted? Is (double_ % space) supposed to be used instead for such cases?

2 3

Re: [Boost-users] [boost] [Fit] upcoming formal review for Boost.Fit
by Paul Fultz II 29 Feb '16

29 Feb '16

On Sunday, February 28, 2016 at 5:28:39 PM UTC-6, Edward Diener wrote: > > On 2/28/2016 4:23 PM, paul Fultz wrote: > > > > > > > > > > On Sunday, February 28, 2016 12:23 PM, Edward Diener < > eldi...(a)tropicsoft.com <javascript:>> wrote: > > > > > >> > >> > >> On 2/27/2016 11:16 AM, Vicente J. Botet Escriba wrote: > >>> Dear Boost community, > >>> > >>> The formal review of Paul Fultz II's Fit library starts on Wednesday, > 2nd March and ends on 13th March. > >> > >> How do I generate the docs or run the tests for my local copy of Fit ? > > > >> > > > > You can build and run the tests by building the check target. For those > > unfamiliar with cmake, first configure the build directory with cmake: > > > > mkdir build > > cd build > > cmake .. > > cd .. > > > > Next build the check target using the native build system(such as make > or > > msbuild). CMake can call the native build system to build the target > 'check', > > like so: > > > > cmake --build build --config Release --target check > > > > Also, the library can be installed by invoking the 'install' target. > > Why is the CMakeLists.txt not in the 'test' subdirectory, since it > appears from your explanation that the file is used for the tests ? > Its used to install the library as well. > > > > > The documentation needs to be built using mkdocs. You can install mkdocs > and > > the boost theme with pip like this: > > > > pip install mkdocs mkdocs-boost > > > > Then to build the documentation, first `setup.py` must be run to extract > the > > documentation and examples from the source code, then `mkdocs` can be > invoked, > > like this: > > > > python setup.py > > mkdocs build -t boost > > > > And the documentation will be in the 'doc/html' directory. > > Please add these explanations to Fit as you are not using Boost build to > build the doc or run the tests. > I will add them. Also, I tried to add an initial Jamfile to build and run the tests as well. I just modified the Jamfile from other boost libraries. However, I haven't figured out how to run the tests yet using bjam to test my Jamfile. I get "error: Did not find Jamfile.jam or Jamroot.jam in any parent directory". I am not sure how I am supposed to run the tests. > > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost >

2 4

[gsoc16] Boost rejected as GSoC 2016 org
by Niall Douglas 29 Feb '16

29 Feb '16

Dear Boost, It is with a heavy heart I write to say that Boost was rejected as an org for Google Summer of Code 2016 by Google. We had our application submitted in time, it was reviewed by three members of the Boost leadership, our ideas list had six solid ideas with an especially solid seventh on the way, we were in very good standing with Google and there was no reason to expect rejection. We have asked for clarification as to why we were rejected, and we shall try to improve our application next year to improve our chances. We recognise that many students and mentors will be extremely disappointed by this news. We share in that disappointment, and all we can say is please try again next year. For those students and mentors who are continuing a previous GSoC on an existing Boost library, there may be a possibility that Boost may be able to fund those continuations this year. Each case will be approached by the steering committee on a case by case basis, and be aware that the standard required for funding by Boost is considerably above that of Google's with an accompanying high and detailed standard of funding application to the steering committee. Contact us privately if you want to know more. On other news we had been expecting to announce today that Bryce Adelstein Lelbach has generously agreed to take over as secondary GSoC admin from Boris Schäling who has served Boost GSoC for something like four years now, so he has definitely earned himself a rest! Our thanks to Boris for his service, and welcome Bryce to the team! Finally, I'd like to thank Jon Kalb who moved heaven and earth as he always does to get the GSoC application submitted in time. Yours, Niall Douglas -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

1 0

C++Now Student/Volunteers Call for Applications
by Jon Kalb 29 Feb '16

29 Feb '16

The Call for Applications for Student/Volunteers for C++Now 2016 (AKA BoostCon X) has been released: http://cppnow.org/2016-conference/announcements/2016/02/23/student-volunteer -program-accepting-applications.html The application submission deadline is March 16th. We are looking for students with a strong interest in C++. The opportunity is open to student of any level or any field of study. Jon Kalb Chair, C++Now 2016

1 0

Re: [Boost-users] Boost.Context stack growing inwards
by Thomas Ziegenhagen 29 Feb '16

29 Feb '16

Hi again, just noticed that the make_fcontext() documentation says that it expects the stack pointer to be at the end or at the beginning, depending on the architecture. So please re-read my last mail as a feature request: If Boost.Context is a platform-independent context switching library, please make its stack pointer parameter also platform-independent. Rationale: Booost.Context knows best on which platform it runs. If the API is supposed to work the same on all supported systems, its parameter should do so, too. Other than that: Sorry for wasting your time. Bye, Thomas

3 2

Boost.Context stack growing inwards
by Thomas Ziegenhagen 29 Feb '16

29 Feb '16

Hi there, I get regular crashes when using Boost.Context after just a few calls to make_fcontext(). I built a minimal example as follows: ---- #include <iostream> #include <vector> #include <boost/context/all.hpp> struct Context { boost::context::fcontext_t c_outside, c_inside; }; Context gContext = { nullptr, nullptr }; void DoIt( intptr_t /*pt*/) { uint8_t test[64]; memset( test, 0xaf, sizeof( test)); std::cout << "DoIt(), Point 1" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); std::cout << "DoIt(), Point 2" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); std::cout << "DoIt(), Point 3" << std::endl; boost::context::jump_fcontext( &gContext.c_inside, gContext.c_outside, 0, true); } int main() { const size_t StackSize = 16384; std::vector<uint8_t> stack( StackSize, 0xf1); gContext.c_inside = boost::context::make_fcontext( stack.data() + 256, stack.size() - 512, DoIt); std::cout << "main(), Point 1" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 2" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 3" << std::endl; boost::context::jump_fcontext( &gContext.c_outside, gContext.c_inside, 0, true); std::cout << "main(), Point 4" << std::endl; return 0; } ------ This notable thing is that I provide a stack with additional 256 bytes of safety borders. And it turns out: the provided memory is overwritten way beyond the beginning. The actual designated area is not touched at all, but instead the area before the beginning is overwritten. The only thing I found in the documentation is this: "sp Member: Pointer to the beginning of the stack (depending of the architecture the stack grows downwards or upwards)." which hints that on some system the stack might grow to negative addresses. But up to now I thought that boost.context knows which direction is correct, and adjusts the given pointer accordingly. But apparently it doesn't. Or the environment underwent a drastic change. Here it is Windows 10 64bit, Visual Studio 2015. For readers remembering my last mails: I have verified this also with an "classic" boost build using this command line: b2.exe -a --reconfigure variant=debug,release link=static runtime-link=static --with-context So I'm pretty sure it's not a build issue. Question: is this a bug? Probably not, I'm surely not the first to use Boost.Context, so I wonder what the correct way is to handle this issue. So what do I do about this? Thanks in advance Bye, Thomas

1 0

Boost.Spirit Karma: how to store generator?
by Matwey V. Kornilov 28 Feb '16

28 Feb '16

Hello, After reading Karma tutorial, I still don't understand whether there a way to store generator except auto my_generator = ... I would like to generate text representation for many similar objects and I think that it is worth to use single generate object and pass it to generate_delimited() by const reference. Are there such things like qi::rule<> and qi::grammar for Karma?

2 1

[ sorting_view ] -do not sort arrays, sort iterators instead
by Boris Kats 27 Feb '16

27 Feb '16

The sorting procedure is one of the most usable routine in programming.And all sorting template functions have the same signature:template< class RandomIt, class Compare >void sort( RandomIt first, RandomIt last, Compare comp );with conditions: the type of dereferenced RandomIt must meet the requirements of MoveAssignable and MoveConstructible.It is clear that in the sorting process a lot of records are moving in the memory andwhen these records have a big size, these movements, together with calling constructors, can be very expensive.Solution.The proposed template function sorting_view is free of that problem - the sorting procedureis working (and moving) on tiny objects - iterators. As result of that procedure,the initial array of records is remaining intact; however provided std::vector<int> viewallows indirect access to the sorted array. On many occasions user does not need the sortedarray at all and he/she has a luxury to iterate through sorted and unsorted arrays simultaneously.In case of real needs of sorted array, it can be obtained via other template function apply_view with exactly 2*N movements of the records, where N is the size of initial array.For getting sorted view of arrays of user's defined records the appropriate Compare template function should be supplied.Happy sorting, Boris Kats.

1 0

Help: Errors compiling SESHAT project
by C. Ichongiri 26 Feb '16

26 Feb '16

Hey there, I've been at this for days now and can't seem to find anything to help with this: I got the project at https://github.com/falvaro/seshat and followed the instructions exactly as-is: - Got the *Boost* headers - Have got *g++ *compiler ( versions 5.2, 4.9, 4.7, 4.5, 4.3) and my default *clang++* *- Makefile *is present *P.S.* I'm on *OS X Mavericks*; Used *MacPorts* to install all above gcc versions *except *5.2, which was manually done following this tutorial: https://solarianprogrammer.com/2015/05/01/compiling-gcc-5-mac-os-x/#comment… However, when I attempt to compile it, I get the following errors (attached in the Textfile below). A screenshot image also attached shows the filesystem and path I am working with, from where the error file was created. Honestly, I'm at my wits end now, especially with my being new to C++. ANY helpful insight into this would be MOST APPRECIATED. Much thanks in advance, chiich.

1 0

Build Boost.Context with Visual Studio
by Thomas Ziegenhagen 26 Feb '16

26 Feb '16

Hi there, I'm building the required portions of Boost myself, along with all my other projects. It turned out that even the smallest compiler setting changes lead to strange crashes, some of which only occured on 5% of the client's systems, so I will not use externally built boost libraries anymore. So now I'm building the parts of boost which I require, which works fine so far. The trouble starts when I tried to use Boost.Context. It also contains ASM code, which I now need to build in Visual Studio 2015. VS2015 does not have builtin Asm support, for x64 it never had. So I'm invoking the Microsoft assembler as a custom build step. Command line is as follows: ml64 /Fo path/to/obj/file.obj /c path/to/source/jump_x86_64_ms_pe_masm.asm Documentation is as scarce as usual, but I figured from the filename that jump_x86_64_ms_pe_masm.asm is the correct file for Microsoft Visual Studio, x64. But assembling failed, and to add insult to injury, the error messages are lost somewhere in the output piping process. The complete output reads like this: ------ 1>------ Erstellen gestartet: Projekt: boost, Konfiguration: Debug x64 ------ 1> Microsoft (R) Macro Assembler (x64) Version 14.00.23506.0 1> Copyright (C) Microsoft Corporation. All rights reserved. 1> 1> Assembling: C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(80)ied size 1>: error A2008 : syntax error : FRAME 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(81)ied size 1>CUSTOMBUILD : warning A4020: directive ignored outside a procedure 1> C:\Projekte\DeadPlanet\SourceExt\boost\context\asm\jump_x86_64_ms_pe_masm.asm(215 1>CUSTOMBUILD : fatal error A1010: unmatched block nesting : jump_fcontext ------ Please note that the actual error messages are overwritten by the filename - I can only guess at what buffer magic happens there, but I'm pretty sure it's not intended. But that's just a funny anecdote. My actual question is: how do I build Boost.Context in Visual Studio? Is there maybe some way to see the effective command line when building using Boost.Jam? Is this even the right ASM file for x86_64, Visual Studio? Thanks in advance! Bye, Thomas

4 5

Spherical Bessel function (nu, x as real) implementation
by campagne 26 Feb '16

26 Feb '16

Dear developpers, 1) Does you use this reference to compute Spherical Bessel Functions for real argument? Accurate recursive generation of spherical Bessel and Neumann functions for a large range of indices E. Gillman <http://scitation.aip.org/content/contributor/AU0510272>^1 and H. R. Fiebig <http://scitation.aip.org/search?value1=H.+R.+Fiebig&option1=author&option91…>Comput. Phys. 2, 62(1988); http://dx.doi.org/10.1063/1.168296 2) is there a way to speed up the computation of j_nu(x) if one wants 10 digits accuracy for instance? Best regards J.E

2 1

[ASIO] Resolver question
by Davies, John 25 Feb '16

25 Feb '16

I have some pretty simple UPD code. (It has to be simple, I'm new at ASIO) boost::asio::ip::udp::resolver::query query(boost::asio::ip::udp::v4(), addr, port); m_receiverEndpoint = *m_resolver.resolve(query); If my address is 192.168.1.112 everything works If my address is 192.168.001.112 it doesn't work and throws an exception about not finding the host. It's not a big deal, but it sure took me a long time to track down. Is there some sort of Boost magic I can do to convert the bad address into a good address? Thanks, John ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

6 11

Boost Thread Compile Issue
by Len Za 25 Feb '16

25 Feb '16

When simply including into C++ project and attempting to compile causes the following compile error: Environment: - Visual Studio 2010 Pro (Project Configuration: DLL project) - boost v1.60.0 C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(99): error C2146: syntax error : missing ';' before identifier 'curr' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(81) : while compiling class template member function 'boost::posix_time::ptime boost::date_time::microsec_clock<time_type>::create_time(boost::date_time::microsec_clock<time_type>::time_converter)' with [ time_type=boost::posix_time::ptime ] C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/thread/thread_time.hpp(22) : see reference to class template instantiation 'boost::date_time::microsec_clock<time_type>' being compiled with [ time_type=boost::posix_time::ptime ] C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(99): error C2065: 'curr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(100): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(100): error C2065: 'curr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(101): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(101): error C2227: left of '->tm_year' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(102): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(102): error C2227: left of '->tm_mon' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(103): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(103): error C2227: left of '->tm_mday' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(111): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(111): error C2227: left of '->tm_hour' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(112): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(112): error C2227: left of '->tm_min' must point to class/struct/union/generic type type is ''unknown-type'' C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(113): error C2065: 'curr_ptr' : undeclared identifier C:\src\SDK\Boost\boost_1_60_0\boost_1_60_0\boost/date_time/microsec_time_clock.hpp(113): error C2227: left of '->tm_sec' must point to class/struct/union/generic type type is ''unknown-type''

1 0

(no subject)
by Виктория Доможакова 24 Feb '16

24 Feb '16

Hello. I have template class. I want to serialize it. But I don't know how. template <class T> class AverDayVisTask : public DrawTask, public AverDayVisMathTask <T> { public: // some functions private: friend class boost::serialization::access; //! boost::serialize template <class Archive> void serialize(Archive& ar, const unsigned int /*version*/) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(DrawTask); ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(AverDayVisMathTask<T>); //<----- error } }; // class AverDayVisTask BOOST_CLASS_VERSION(AverDayVisTask<SphericalModel>, 1); BOOST_CLASS_VERSION(AverDayVisTask<SphericalNutModel>, 1); BOOST_CLASS_VERSION(AverDayVisTask<WGS84Model>, 1); BOOST_CLASS_IMPLEMENTATION(AverDayVisTask<SphericalModel>, boost::serialization::object_class_info); BOOST_CLASS_IMPLEMENTATION(AverDayVisTask<SphericalNutModel>, boost::serialization::object_class_info); BOOST_CLASS_IMPLEMENTATION(AverDayVisTask<WGS84Model>, boost::serialization::object_class_info); How fix my problem? -- Виктория Доможакова

2 1

[graph] abort algorithm execution from a visitor
by Frank Tetzel 23 Feb '16

23 Feb '16

Hi all, i played around with the bfs example calculating distances to all vertices. Now i just want to calculate the distance between two vertices, so i want to stop when the target vertex is visited. If i understood the visitor concept correctly it's not really possible to change the behaviour of the algorithm from a visitor. Does anybody know of any workaround to do early exit? Do i have to implement a new algorithm for this? In a different thread on this list Paolo Bolzoni wrote that he aborts in a custom visitor by throwing an exception. Is this the only way? I'm using bfs here and not dijkstra because i have uniform edge weights. Btw, if someone could fix the documentation that would be really nice: http://www.boost.org/doc/libs/1_60_0/libs/graph/doc/bfs_visitor.html The code snippet there did not work for me. I had to wrap make_bfs_visitor() in visitor() like it is done in examples/bfs.cpp too. Regards, Frank

2 2

Boost 1.60 Raspberry Pi lockfree::queue compilation error
by Alexander Simpson 23 Feb '16

23 Feb '16

Hello, I’m trying to compile a project that makes use of boost::lockfree::queue on a Raspberry Pi 2 running Jessie. I built version 1.60 of Boost myself (apt-get was out of date) with sudo ./bjam install. I’m not cross-compiling. When I attempt to compile a project that uses the boost library I get the error listed below (where boostreader.cpp is the file written by me). I found a patch suggested two years ago here (https://svn.boost.org/trac/boost/ticket/9041 <https://svn.boost.org/trac/boost/ticket/9041>) but the changes in that patch seem to have already applied in 1.60, so I’m at a loss as to what to do. Assistance would be greatly appreciated. Alexander Simpson Error message: In function `boost::lockfree::detail::freelist_stack<boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::node, std::allocator<boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::node> >::~freelist_stack()': main.cpp:(.text._ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED2Ev[_ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED5Ev]+0x18): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED2Ev[_ZN5boost8lockfree6detail14freelist_stackINS0_5queueIiNS_9parameter5void_ES5_S5_E4nodeESaIS7_EED5Ev]+0x24): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.o: In function `boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::queue(unsigned int)': main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x6c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x78): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xb0): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xbc): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xd8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0xe4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x148): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x170): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x1ec): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x1f8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x224): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC2Ej[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_EC5Ej]+0x230): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.o: In function `boost::lockfree::queue<int, boost::parameter::void_, boost::parameter::void_, boost::parameter::void_>::~queue()': main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x58): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x64): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x90): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x9c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0xc8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0xd4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x128): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x134): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x164): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x170): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x180): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x18c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1c8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1d4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1e8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x1f4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x218): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x224): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x260): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x26c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x278): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' main.cpp:(.text._ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED2Ev[_ZN5boost8lockfree5queueIiNS_9parameter5void_ES3_S3_ED5Ev]+0x284): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.o: In function `BoostReader::run()': boostreader.cpp:(.text+0x84): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x90): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0xb8): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0xc4): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0xf0): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0xfc): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x11c): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x128): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x1ac): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x1dc): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x204): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x210): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x264): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x288): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()' boostreader.cpp:(.text+0x438): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::scoped_lock(void const volatile*)' boostreader.cpp:(.text+0x454): undefined reference to `boost::atomics::detail::lockpool::scoped_lock::~scoped_lock()'

2 1

boost 1.54: problem with building documentation.
by Paul K 22 Feb '16

22 Feb '16

Hallo people. I need to have documentation in man pages format on my ubuntu 14.04. Unfortunatelly, I fail with this task. The following are the steps I've performed. In step 11 I do "../b2" instead "../b2 man" just to highlight that the problem is not related to building the man pages. Of course "../b2 man" fails as well Could You please help me with it? 1. install following packages for man pages build. lubuntu.14.04$ sudo apt-get install xsltproc lubuntu.14.04$ sudo apt-get install doxygen 2. lubuntu.14.04$ dpkg --list | grep libboost-all ii libboost-all-dev 1.54.0.1ubuntu1 i386 Boost C++ Libraries development files (ALL) (default version) 3. download boost_1_54_0.tar.bz2, unpack to ~/ 4. cd ~/boost_1_54_0 5. ./bootstrap prepares build configuration and puts it to project-config.jam. 6. ./b2 builds whole the boost libraries, but does not install them into the system. 7. lubuntu.14.04$ export BOOST_ROOT=/home/userp/boost_1_54_0 8. lubuntu.14.04$ cd ~/boost.doc/ 9. lubuntu.14.04$ ~/boost_1_54_0/tools/boostbook/setup_boostbook.sh Downloading DocBook XSLT Stylesheets version 1.75.2... Expanding DocBook XSLT Stylesheets into /home/userp/boost.doc/docbook-xsl-1.75.2...done. Downloading DocBook XML DTD version 4.2... Expanding DocBook XML DTD into /home/userp/boost.doc/docbook-dtd-4.2... done. Searching for xsltproc... /usr/bin/xsltproc. Searching for Doxygen... /usr/bin/doxygen. Searching for Java... /usr/bin/java. Downloading FOP distribution version 0.94... Expanding FOP distribution into /home/userp/boost.doc/fop-0.94... done. Updating Boost.Jam configuration in /home/userp/user-config.jam... done. Done! Execute "bjam --v2" in a documentation directory to generate documentation with BoostBook. If you have not already, you will need to compile Boost.Jam. 10. lubuntu.14.04$ cd ~/boost_1_54_0/doc 11. lubuntu.14.04$ ../b2 Performing configuration checks - has_icu builds : yes (cached) /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:1099: in virtual-target.register-actual-name from module virtual-target error: Duplicate name of actual target: <p../bin.v2/libs/filesystem/build/gcc-4.9.3/release/link-static>libboost_filesystem.a error: previous virtual target { gcc%gcc.archive-libboost_filesystem.a.STATIC_LIB { gcc%gcc.compile.c++-codecvt_error_category.o.OBJ { codecvt_error_category.cpp.CPP } } { gcc%gcc.compile.c++-operations.o.OBJ { operations.cpp.CPP } } { gcc%gcc.compile.c++-path.o.OBJ { path.cpp.CPP } } { gcc%gcc.compile.c++-path_traits.o.OBJ { path_traits.cpp.CPP } } { gcc%gcc.compile.c++-portability.o.OBJ { portability.cpp.CPP } } { gcc%gcc.compile.c++-unique_path.o.OBJ { unique_path.cpp.CPP } } { gcc%gcc.compile.c++-utf8_codecvt_facet.o.OBJ { utf8_codecvt_facet.cpp.CPP } } { gcc%gcc.compile.c++-windows_file_codecvt.o.OBJ { windows_file_codecvt.cpp.CPP } } } error: created from ../libs/filesystem/build/boost_filesystem error: another virtual target { gcc%gcc.archive-libboost_filesystem.a.STATIC_LIB { gcc%gcc.compile.c++-codecvt_error_category.o.OBJ { codecvt_error_category.cpp.CPP } } { gcc%gcc.compile.c++-operations.o.OBJ { operations.cpp.CPP } } { gcc%gcc.compile.c++-path.o.OBJ { path.cpp.CPP } } { gcc%gcc.compile.c++-path_traits.o.OBJ { path_traits.cpp.CPP } } { gcc%gcc.compile.c++-portability.o.OBJ { portability.cpp.CPP } } { gcc%gcc.compile.c++-unique_path.o.OBJ { unique_path.cpp.CPP } } { gcc%gcc.compile.c++-utf8_codecvt_facet.o.OBJ { utf8_codecvt_facet.cpp.CPP } } { gcc%gcc.compile.c++-windows_file_codecvt.o.OBJ { windows_file_codecvt.cpp.CPP } } } error: created from ../libs/filesystem/build/boost_filesystem error: added properties: <auto-index-internal>off <auto-index-no-duplicates>off <auto-index-section-names>on <auto-index-verbose>off <auto-index>off <format>docbook error: removed properties: <format>html /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:484: in actualize-no-scanner from module object(file-target)@3468 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3468 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:836: in actualize-sources from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@3786 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3787 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:834: in actualize-sources from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@3793 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@3794 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:815: in actualize-source-type from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:834: in actualize-sources from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:776: in class(a)action.actualize from module object(action)@7122 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:311: in actualize-action from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:493: in actualize-no-scanner from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build/virtual-target.jam:134: in class(a)virtual-target.actualize from module object(file-target)@7123 /home/userp/boost_1_54_0/tools/build/v2/build-system.jam:720: in load from module build-system /home/userp/boost_1_54_0/tools/build/v2/kernel/modules.jam:289: in import from module modules /home/userp/boost_1_54_0/tools/build/v2/kernel/bootstrap.jam:139: in boost-build from module /home/userp/boost_1_54_0/boost-build.jam:17: in module scope from module regards

1 0

boost::any constructors
by David 22 Feb '16

22 Feb '16

Hi, boost::any has a perfect forward constructor declared as: template<typename ValueType> any(ValueType&& value , typename boost::disable_if<boost::is_same<any&, ValueType> >::type* = 0 // disable if value has type `any&` , typename boost::disable_if<boost::is_const<ValueType> >::type* = 0) // disable if value has type `const ValueType&&` : content(new holder< typename decay<ValueType>::type >(static_cast<ValueType&&>(value))) {} The is_const SFINAE exclusion forces const types to the regular copy constructor: template<typename ValueType> any(const ValueType & value) : content(new holder< BOOST_DEDUCED_TYPENAME remove_cv<BOOST_DEDUCED_TYPENAME decay<const ValueType>::type>::type >(value)) {} What is different about how the regular copy constructor treats a constant value than what the perfect forward construct would do if the is_const exclusion were removed? Thanks, David

2 1

Nested BOOST_FOREACH crash
by peyman＠ausdia.com 22 Feb '16

22 Feb '16

Good Day Boosters! I am experiencing sporadic crashes that look like memory problem when I have nested (2 level) BOOST_FOREACH loops. Reason I say it looks like memory problem is because slightest change will make it crash or not crash. For example, adding a simple cout would change it! I cannot provide a testcase. So I am just wondering if anybody has experienced the same, or know what could be going on. I am using Boost 1.57. Cheers, Peyman

2 1

Need help when adapting boost 1.59.0 to WinRT
by Nguyễn Trung Duy 22 Feb '16

22 Feb '16

Dear Boost team, I need your help with adapting boost 1.59 to WinRT. I am working on boost and reSIProcate. I built boost and integrated it with reSIProcate project. However, when build reflow project, I got stuck with bellow bugs. I wonder with your great experiences, could you please give me some advice. The error happens at line 96 : #if defined(BOOST_ASIO_WINDOWS_RUNTIME) const int max_addr_v4_str_len = 256; const int max_addr_v6_str_len = 256; typedef unsigned __int32 u_long_type; typedef unsigned __int16 u_short_type; struct in4_addr_type { u_long_type s_addr; }; // error at here And the logs: *\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3927: '->': trailing return type is not allowed after a non-function declarator (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3484: syntax error: expected '->' before the return type (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3613: missing return type after '->' ('int' assumed) (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(96): error C3646: 'S_addr': unknown override specifier (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3927: '->': trailing return type is not allowed after a non-function declarator (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3484: syntax error: expected '->' before the return type (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3613: missing return type after '->' ('int' assumed) (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C3646: 'Byte': unknown override specifier (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ',' before '[' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ')' before ';' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2143: syntax error: missing ';' before ')' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/detail/socket_types.hpp(98): error C2059: syntax error: ')' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(61): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(147): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)\boost-msvc-14.0-store\boost/asio/ip/address_v4.hpp(153): error C2039: 'S_addr': is not a member of 'default::uint32' (compiling source file MediaStream.cxx)* Thanks you so much!!!! *--* *Best Regards,* *NGUYEN TRUNG DUY* *Android Developer* *Mobile*: (+84)977 46 12 23 *Skype :* trungduy150388 *Website*: http://nguyentrungduy.com/ *Blog*: http://dbox.nguyentrungduy.com/ *Github*: https://github.com/nguyentrungduy

2 2

Newbie
by Shan Wijesinghe 22 Feb '16

22 Feb '16

Hi all, I'm a new member to C++ boost and I have a fairly good knowledge in programming in C++. I'm very much excited to join this group and I need directions from the senior members on how to start myself. Please help me here. Thanks in advance. regards, DilSHAN.

6 11

Query on Boost.DLL
by Leo Carreon 21 Feb '16

21 Feb '16

Hi, I have been reading the Boost.DLL documentation. Can a single plugin support multiple API’s? If yes, when the multiple API’s are used at the same time; will there be only one instance of the plugin loaded or will there be multiple instances loaded? Regards, Leo

2 1

Boost.DLL
by Leo Carreon 21 Feb '16

21 Feb '16

Hi, Can anyone please let me know what the status of the Boost.DLL library is? Regards, Leo

2 1

[coroutine] - only std exceptions are caught from coroutines
by Tamas.Ruszkai＠leica-geosystems.com 21 Feb '16

21 Feb '16

3 4

[Interprocess] Communication between x86 and x64 issue
by Toni Neubert 19 Feb '16

19 Feb '16

I want to communicate between different platforms using boost interprocess. I am using vc12 and boost 1.58 on windows 7. My code below is a very simple example, that should work. But it doesn't for communications between different platforms... If I create it in x64 and open in win32, the process stuck at a lock at function try_based_lock in boost/int/sync/detail/common_algorithms.hpp In the other way around: win32 create, x64 open: the process crashes at name_length in segment_manager_helper.hpp while trying to find the name in index (priv_generic_find in segment_manager). #include <iostream> #include <boost/interprocess/managed_shared_memory.hpp> int main() { namespace bip = boost::interprocess; // open in WIN32, create in x64 #ifdef _WIN32 bip::managed_shared_memory msm(bip::open_only, "TestIPC"); #elsif X64 bip::shared_memory_object::remove("TestIPC"); bip::managed_shared_memory msm(bip::create_only, "TestIPC", 4096); msm.construct<uint32_t>("Data")[1](10); #endif // Get Data and print it auto data = msm.find<uint32_t>("Data"); if (data.second == 1) { std::cout << *data.first << std::endl; } std::cin.ignore(); return 0; } Does anybody have experience in this? Thank you in advance!

3 2

Re: [Boost-users] [Serialization] This compiles; but does it work?
by Bjorn Reese 19 Feb '16

19 Feb '16

On 02/19/2016 04:20 AM, Merrill Cornish wrote: > Can anyone tell me if this will work, or do I need to implement the > serialize() function? When you are doing different things for the input and output archives then it is better to split serialization into load and save: #include <boost/filesystem/path.hpp> #include <boost/serialization/split_free.hpp> namespace boost { namespace serialization { template <typename Archive> void serialize(Archive& ar, filesystem::path& p, const unsigned int version) { split_free(ar, p, version); } template<class Archive> void save(Archive & ar, const filesystem::path& p, unsigned int version) { ar << p.string(); } template<class Archive> void load(Archive & ar, filesystem::path& p, unsigned int version) { std::string data; ar >> data; p = data; } }}

2 1

[graph] Search algorithm using quality metric rather than distance
by rleigh＠codelibre.net 19 Feb '16

19 Feb '16

I have an adjacency_list graph (shown in attached dot file). Each edge has an attached "quality metric" as a bundled property. Similar to the dijkstra_shortest_paths algorithm, I'd like to determine the optimal path. However, this algorithm sums the distance along each edge, and finds the shortest path. What I'd like to do is *multiply* the quality metric for each edge in the path, and find the largest one. A perfect path will have a quality metric of 1.0, while suboptimal paths will have values tending towards zero, and the more "bad" edges the smaller the number. I'll likely then look at the number of edges and then select the shortest of the candidates. It seems like a simple algorithm that might already be included, but I just haven't found it yet not knowing its formal name. If anyone has any suggestions, I'd be very grateful. Many thanks, Roger

5 4

[Serialization] This compiles; but does it work?
by Merrill Cornish 19 Feb '16

19 Feb '16

mGraphFile is a data member of type boost:filesystem::path, which isn't (as I understand) handled natively by Boost Serialization. I could define template<class Archive> void serialize(Archive& ar, boost::filesystem::path& p, const unsigned int version); but it is needed in only one place. Below is an excerpt from an inline serialization function that I'm already using. While it has a redundant step not needed for loading and a different redundant step not needed for storing, it would seem to do what I need. (The minor inefficiency of the redundant statements is of no concern here.) ... std::string str = mGraphFile.string(); // redundant if loading ar & BOOST_SERIALIZATION_NVP(str); mGraphFile = str; // redundant if saving ... Can anyone tell me if this will work, or do I need to implement the serialize() function? Merrill Cornish

1 0

boost::msm usage: how to set properties of target states
by spiritwalker 18 Feb '16

18 Feb '16

States in my fsm has different properties. I define a event which will invoke a transition to a target state. I want to set properties of target by event data. My choices are: 1. set properties in the action or guard: but it is still in the source state. I fill not good if i set the target state properties at the time 2. set properties in the target entry: but the value of properties have been calculated in guard on receiving the event so i should recalculated again :( Any one can give me more ideas. Thanks ! -- View this message in context: http://boost.2283326.n4.nabble.com/boost-msm-usage-how-to-set-properties-of… Sent from the Boost - Users mailing list archive at Nabble.com.

2 1

SERIALIZE: Registering derived templete classes serialized via base ptr
by Unger, Jörg 17 Feb '16

17 Feb '16

I'm trying to serialize a derived class via a base ptr using boost serialize. The example to illustrate the problem (without templates) is as follows //****************** Main.cpp ********************** #include <fstream> #include <boost/archive/text_iarchive.hpp> #include <boost/archive/text_oarchive.hpp> #include "Derived.h" int main(int argc, char* argv[]) { std::string fileName = "Out.txt"; Derived myDerived; Base* myBasePtr = &myDerived; //myDerived.foo(); // serialize it as txt std::ofstream ofs(fileName.c_str(), std::ios_base::binary ); boost::archive::text_oarchive ota ( ofs, std::ios::binary ); //ota & boost::serialization::make_nvp(std::string("directly derived").c_str(), myDerived);; ota & boost::serialization::make_nvp(std::string("via base ptr").c_str(), myBasePtr);; return 0; } //*********************************************** //*************** Base.h ************************* #pragma once #include <boost/serialization/access.hpp> #include <boost/serialization/export.hpp> class Base { friend class boost::serialization::access; public: Base(){}; virtual ~Base(){}; template<class Archive> void serialize(Archive & ar, const unsigned int version) {}; }; BOOST_CLASS_EXPORT_KEY(Base) //*********************************************** //**************** Derived.h ********************** #pragma once #include <boost/serialization/access.hpp> #include <boost/serialization/export.hpp> #include "Base.h" class Derived : public Base { friend class boost::serialization::access; public: Derived(){}; void foo(); template<class Archive> void serialize(Archive & ar, const unsigned int version); }; BOOST_CLASS_EXPORT_KEY(Derived) //*********************************************** //**************** Derived.cpp ******************** #include <boost/archive/text_oarchive.hpp> #include <boost/archive/text_iarchive.hpp> #include "Derived.h" //Derived::Derived() //{} void Derived::foo() { } // serializes the class template void Derived::serialize(boost::archive::text_oarchive & ar, const unsigned int version); template void Derived::serialize(boost::archive::text_iarchive & ar, const unsigned int version); template<class Archive> void Derived::serialize(Archive & ar, const unsigned int version) { ar & BOOST_SERIALIZATION_BASE_OBJECT_NVP(Base); } BOOST_CLASS_EXPORT_IMPLEMENT(Derived) //*********************************************** When compiling the above code and linking the object files, everything works fine. When I combine everything in a library (in this example it is essentially only Derived.o) and link the main file with the library, I get an error what(): unregistered class - derived class not registered or exported The problem seems to be that the registration in the linked library is not activated. The problem is simplified here, because in our implementation, the derived class is essentially a template class that does not have any cpp-files. We have just added another otherwise empty cpp file with the registration of all possible instantiations of the class. There are several possibilities to solve the problem · The macro BOOST_CLASS_EXPORT_IMPLEMENT(Derived) could be moved to the main.cpp. This workaround is not my preferred options, since the registration has to be done in every main file we want to use the library for. · The macro BOOST_CLASS_EXPORT_IMPLEMENT(Derived) could be moved to the Base.cpp (the constructor for the base class has to be implemented in this file as well). This is another option, but this requires the header files of the derived classes to be included in Base.cpp, which is not convenient either. · Serialize one object of the derived class before serialization through the pointer, but that's only a workaround. (see the commented line in Main.cpp) · Call the foo method in Main.cpp. Surprisingly, this does not depend on whether the foo function is implemented in Derived.cpp, but also if it is called in Main.cpp. Surprisingly, if "myDerived.foo();" in Main.cpp is uncommented the program works fine, which is something I do not understand. It seems that the registration is only performed, if one of the functions in this cpp file is actually called, or am I wrong? · Implement the constructor of Derived in Derived.cpp. This approach works fine for the current example (somehow similar to the previous solution). However, in our case, Derived is a template and thus the constructor can't be implemented in the cpp file. · Another option is to always link the main file with the library and the object file Derived.o, but this is also not a convenient option. · Finally, a manual registration with register_type is possible. This could be moved to a separate subroutine that is always called in different main files. What is the recommended way of registering derived template classes that are serialized through a base ptr within a library. Best regards, Jörg F. Unger

2 1

[Timer] unresolved external symbol boost::chrono::time_point
by Aman Wardak 17 Feb '16

17 Feb '16

Env: Win7 32-bit running in VirtualBox on Macbook Pro Compiler: MS Visual Studio 14 It's my first time working with Boost. I've followed the instructions here: http://www.boost.org/doc/libs/1_60_0/more/getting_started/windows.html I've compiled Boost successfully: ============================ The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: C:\Users\IEUser\Documents\boost_1_60_0 The following directory should be added to linker library paths: C:\Users\IEUser\Documents\boost_1_60_0\stage\lib ============================================== I've added the above paths in Visual Studio and was able to run the test in step 6 of the instructions linked above to verify my environment is set up correctly. MY PROBLEM: I'm trying to compile the very first sample code at this link: http://www.boost.org/doc/libs/1_60_0/libs/timer/doc/cpu_timers.html I get the following error: ------ Build started: Project: BoostExample, Configuration: Debug Win32 ------ Source.cpp libboost_timer-vc140-mt-gd-1_60.lib(cpu_timer.obj) : error LNK2019: unresolved external symbol "public: static class boost::chrono::time_point<class boost::chrono::steady_clock,class boost::chrono::duration<__int64,class boost::ratio<1,1000000000> > > __cdecl boost::chrono::steady_clock::now(void)" (?now@steady_clock @chrono@boost@@SA?AV?$time_point@Vsteady_clock@chrono@boost@@V?$duration@ _JV?$ratio@$00$0DLJKMKAA@@boost@@@23@@23@XZ) referenced in function __catch$??1auto_cpu_timer@timer@boost@@QAE@XZ$0 C:\Users\IEUser\Documents\Visual Studio 2015\Projects\CS2370\Debug\BoostExample.exe : fatal error LNK1120: 1 unresolved externals ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ========== Thanks, Aman

1 0

[Test] BOOST_CHECK_EXCEPTION error message still vague
by Merrill Cornish 17 Feb '16

17 Feb '16

In BOOST_1_59_0, I complained that the error message from BOOST_CHECK_EXCEPTION was indecipherable. In BOOST_1_60_0, things improved a lot. But it still leave you hanging. I use the function fail_msg() as the predicate argument to BOOST_CHECK_EXCEPTION. If it finds a specified substring in the exception message, it returns true. Otherwise, it returns false. Below is an error message from BOOST_CHECK_EXCEPTION when the predicate returned false: exception "std::runtime_error" raised as expected: validation on the raised exception through predicate "fail_msg" The first clause says my code raised the expected exception class. That part of the message is clear and unambiguous. The second clause, however, is a non-sequitur. It seems to only acknowledge that there was a predicate named "fail_msg" without saying whether it returned true or false. Overall, the whole message doesn't say whether BOOST_CHECK_EXCEPTION passed or failed. Since a message was output, the user can assume things did not go well, but it seems like the message could be more explicit. Merrill Cornish

2 2

multiprecision max and et_on
by Daniel Brake 16 Feb '16

16 Feb '16

Hi Boost, I would like to be able to use the Eigen linear algebra library with Boost.Multiprecision with et_on. However, as noted here: https://svn.boost.org/trac/boost/ticket/11149 for max, et_on isn't compatible out of the box. Aside from writing my own little overload for max for the particular form being produced in my line of code from within Eigen, does anyone have a fix for enabling max with expression templates on? MWE: { using mpfr = boost::multiprecision::mpfr_float; // et_on by default, which is what i want using std::max; mpfr a(1), b(2), c(4); auto q = b*b+c; mpfr r = max(a,q); } Thanks a lot, Daniel

1 0

[GIL] Why doesn't pixel assignment color-convert?
by Stonewall Ballard 16 Feb '16

16 Feb '16

I've just started using boost.gil, though I've been looking at it for a while. It seems odd to me that assignment doesn't do an implicit color_convert() when the pixels are of different types. Instead, it just copies matching channels. That's the wrong thing to do when assigning an rgba pixel to an rgb pixel, since the former is straight and the latter is premultiplied. It also seems wrong that you can assign an rgba pixel to an rgb pixel, but not vice-versa. It looks like this is caused by pixels_are_compatible in gil_concept.hpp, where it fails to check that both pixels have the same number of channels. Instead, it matches channels of the output pixel against the input pixel, ignoring any extra input pixel channels. It also ignores scoped_channel_value usage. This seems like an error waiting to happen. Comments? - Stoney

1 0

ASIO: add work and remove immed., will ignore further handler_requests???
by aj neu 16 Feb '16

16 Feb '16

Hi, below is some code where boost::asio::io_service::work is added, and then immediately removed. After that, I call async_wait on a steady_timer, but it does not work: io.run() RETURNS IMMEDIATELY, and IGNORES the async_wait. Is this intended? (I was rather surprised, because I thought that the async_wait would schedule new work, but it does not work). If I cange the code-line #define WEIRD_BEHAVIOUR to #undef WEIRD_BEHAVIOUR then I have my expected behaviour. Thanks, ajneu #include <iostream> #include <chrono> #include <experimental/optional> #include <boost/asio.hpp> #include <boost/asio/steady_timer.hpp> #define WEIRD_BEHAVIOUR int main() { boost::asio::io_service io; std::experimental::optional<boost::asio::io_service::work> work; #ifdef WEIRD_BEHAVIOUR work.emplace(io); work = std::experimental::nullopt; #endif boost::asio::steady_timer timer(io, std::chrono::milliseconds{1000}); timer.async_wait([](const boost::system::error_code &ec) { std::cout << ((!ec) ? "done" : "err") << std::endl; }); io.run(); }

1 0

Writing a stratum client using boost:asio
by Jan Willem Penterman 11 Feb '16

11 Feb '16

Hi, I'm trying to write a stratum client for a cryptocurrency mining application. The mining application connects to a stratum server to receive new work to mine on and submit solutions. The stratum protocol is a simple TCP based line protocol with JSON payload. Documentation here: https://mining.bitcoin.cz/help/#!/manual/stratum-protocol I've chosen to use boost::asio, as boost is already heavily used in the fork of the project I'm building the miner for. But I'm having difficulties to understand why my current implementation doesn't work. The basic flow is as follows: 1. connect to the server. this works 2. send subscribe method. this also works 3. authorize worker(s). doesn't work. 4. stratum server should start pushing new work periodically. doesn't work. 5. submit solution when found. not implemented yet. Without authorization, the server should still start pushing work. So I've skipped step 3 for now. The source code as I have it now is available here: https://github.com/Genoil/cpp-ethereum/blob/stratum/libstratum/ The output I get from this is as follows: i 12:19:14|<unknown> Connected to stratum server coinotron.com : 3344 i 12:19:15|<unknown> {"error": null, "id": 1, "result": [["mining.notify", "91d0025c5ea54509977e3475d065169e"], "080016D0", 4]} i 12:19:15|<unknown> Subscribed i 12:19:15|<unknown> { "id": null, "method": "mining.set_difficulty", "params": [32768]} i 12:19:15|<unknown> mining.set_difficulty i 12:19:15|<unknown> {"params": ["31065", "0xc09361c52e9dddd141040cc79c52eaed382e92c1dd350324c040482a4c4ac0fa","0x5a46dd85298b0beff65ccf3006c4b5d2f7fa6ca8a5885a7f2132714fe7a48602","0x0000000200000000000000000000000000000000000000000000000000000000", true], "id": null, "method": "mining.notify"} i 12:19:15|<unknown> mining.notify >From this I can conclude that the subscription call works. Then at the end of handleResponse, I simply queue up a new async_read_until to wait for the next line of JSON to come in from the server. This also kind of works, but the idea is that after a few seconds, new work should come in as a "mining.notify". This never happens. Can anybody explain what I'm doing wrong? Regarding the mining.authorize call on line 113. I've understood from the documentation that I can send that whenever I want, so I tried to do this immediately after the subscribe method returned. But if I do this, it a) doesn't return and b) all lines after "Subscribed" don't come in any longer. This is the second problem I'm trying to figure out. I'm using this as reference, but my Python is even worse than my C++ https://github.com/slush0/stratum-mining-proxy But when I run the binaries connecting to the same host (coinotron.com:3344), I do get new work coming in... Thanks for having a look at this.

1 0

[ASIO] Newbie question - Bidirectional communication example
by Davies, John 11 Feb '16

11 Feb '16

For a simple explanation I have two processes that run on the same computer. Process 1 sends messages to Process 2 by putting the messages into an Interprocess message queue that Process 2 created. Process 2 sends messages to Process 1 by putting the messages into an Interprocess message queue that Process 1 created. The messages can be sent at any time and are not in response to each other. Very symmetrical. Now I want to put Process 1 and Process 2 on separate computers. My intent is to transfer the messages over TCP to the opposite computer without changing Process 1 or 2. So I thought I'd create two connector programs. Connector 1 creates a message queue that pretends to be the Process 2 message queue. When it gets a message, it send it over TCP the Connector 2. Connector 2 gets the message and puts it into the real Process 2 message queue. And the reverse if Process 2 has an outgoing message. I just can't find a good example to steal from. Everything I can find are more like Process 1 makes a request and Process 2 responds. So I think I have a fundamental misunderstanding of how ASIO works. ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

2 1

[Test] Funny Business with vector::at() out-of-range
by Merrill Cornish 11 Feb '16

11 Feb '16

I posted a question a couple of days ago: "Throws 'Escaping' both BOOST_CHECK_THROW and try{}". I found that BOOST_CHECK_EXCEPTION which is working for me elsewhere fails the same way. So, an out-of-range std::vector::at() seems to be the common element. In the definition of at(), the out-of-range response is handled by __throw_out_of_range_fmt(). When I looked up that one, I found void __throw_out_of_range_fmt(const char*, ...) __attribute__((__noreturn__)) __attribute__((__format__(__gnu_printf__, 1, 2))); in functexcept.h. To my admittedly less-than-expert eye, there doesn't seem to be an actual throw() here. On the other hand, the entire file are entries like this for various exceptions. There are a lot of Google hits for __throw_out_of_range_fmt, but they are for unresolved references in links, apparently caused by mixed version of libraries and object. Everything I've got is compiled linked for MinGW 64-bit, GCC 5.3.0, 64-bit --std=C++14, BOOST 1_60_1 64-bit so I get none of those errors. The problem I'm seeing with my test code is that wrapping a try{} around BOOST_CHECK_THROW shows that [1] the body of the try doesn't complete; but at the same time [2] not even a catch(...) can catch the presumed throw--as if a throw isn't actually being done. So, where did the throw go? Merrill Cornish

2 1

[TEST] Throws "Escaping" both BOOST_CHECK_THROW and try{}
by Merrill Cornish 11 Feb '16

11 Feb '16

I'm running Windows 10, 64-bit; MinGW 64-bit; GCC 5.3 64-bit; and BOOST 1_60_1 Here is the relevant test code: [319] BOOST_CHECK_THROW(throw std::out_of_range("BOOST_CK_THROW test"), std::out_of_range); [320] try { [321] std::cerr << "arcsSize()" << std::endl; [322] empty1.arcsSize(Operand::DEFAULT_ARC_SET+1); [323] std::cerr << "arcsSize() did not throw" << std::endl; [324] }//try [325] catch (const std::out_of_range& ex) [326] { std::cerr << "out_of_range caught=|" << ex.what() << "|" << std::endl; } [327] catch (...) { std::cerr << "something else caught" << std::endl; } [328] [329] BOOST_CHECK_THROW(empty1.arcsSize(Operand::DEFAULT_ARC_SET+1), std::out_of_range); The original code was just the last line, line [329]. [319]-[327] was added in an attempt to characterize the problem. The error [329] got by itself was: terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 1) >= this->size() (which is 1) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. SIGABRT intercepted; converted to exit(EXIT_FAILURE). arcSize() is implemented with std::vector::at() and the index is out-of-range, so it's supposed to throw std::out_of_range. That's what was detected, so why did it terminate the program? (The last line comes from my SIGABRT handler. Without it, the test executable ends up locked and can't be deleted.) Adding in all of the test lines shown above gives; [319] Operand_Test.cpp(319): info: check 'exception "std::out_of_range" raised as expected' has passed [321] arcsSize() terminate called after throwing an instance of 'std::out_of_range' what(): vector::_M_range_check: __n (which is 1) >= this->size() (which is 1) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. SIGABRT intercepted; converted to exit(EXIT_FAILURE). Notice the explicit throw in line [319] is detected and handled properly. However, the arcSize() call from inside the try block throws, but is not caught by even catch(...) {}. Can anyone help me see what's going on here? Merrill Cornish

2 6

[Container] Regarding Trac #11957, static_vector::max_size() is higher than the capacity
by Gagan Kumar 10 Feb '16

10 Feb '16

I tried a simple fix for https://svn.boost.org/trac/boost/ticket/11957 here https://github.com/boostorg/container/pull/37/files . Can someone please review it. Regards,Gagan Kumar

1 0

Boost Variant Type Interfaces
by Ali Nakipoglu 09 Feb '16

09 Feb '16

Hi, In our project we are using boost, boost.variant very extensively. We was using methods provided by the library to interface with Variant types. Mainly : get<T>( variant ) for accessing stored values and variant.which() == Index for checking currently stored type. Overtime we realized we can improve this as : variant.getT() for accessing stored values much more nicer to write and variant.isT() or variant.which() == WHICH_T for checking currently stored type which does not depend on order of template paramters in the Variant definition. Also in some cases we wanted to be able to add type specific methods for example in our case we are using subscript operator to access recursively stored Variants variant[ "a" ].isT() or variant[ 0 ].asT() We generalized this solution for our project and published at https://github.com/FictionIO/WrappedVariant I would like to hear your comments. Do you think its a correct approach or useful? Any suggestions are welcome! Kind Regards, Ali

1 0

[Multiprecision] Runtime assertion failure with clang++3.6.0 but not g++4.9.2
by mbw_bst＠mailbox.org 09 Feb '16

09 Feb '16

Dear all, this is my first post on this mailing list, so hopefully this will all be by the book. Executing the following minimal working example, which is supposed to calculate "3! == 6" via (1) a template function (2) a class template and save the result in a boost::multiprecision::mpz_int, results in unexpected behavior for clang++3.6.0, with the version of my boost library being 1.59.0. The program displays the correct result using g++4.9.2 however: #include <iostream> #include <boost/multiprecision/gmp.hpp> namespace bm = boost::multiprecision; template <std::size_t N> bm::mpz_int factorial() { return N * factorial<N-1>(); } template<> bm::mpz_int factorial<0>() { return 1; } template <std::size_t N> struct factorial2 { static const bm::mpz_int value; }; template<std::size_t N> const bm::mpz_int factorial2<N>::value = N * factorial2<N-1>::value; template<> struct factorial2<0> { static const bm::mpz_int value; }; const bm::mpz_int factorial2<0>::value = 1; int main () { std::cout << factorial<3>() << '\n'; std::cout << factorial2<3>::value << '\n'; return 0; } The output for clang, having been compiled via clang++ -std=c++14 -stdlib=libc++ -DNDEBUG -o main main.cpp -lgmp will result in: 6 0 However, omitting the NDEBUG flag will trigger an assertion failure: main: /usr/include/boost/multiprecision/gmp.hpp:1296: const mpz_t &boost::multiprecision::backends::gmp_int::data() const: Assertion `m_data[0]._mp_d' failed. Aborted (core dumped) Compiling the same program with g++4.9.2 (with or without "-DNDEBUG") yields the expected result: 6 6 What did I miss? Can this behavior indeed be traced down to Boost.Multiprecision, or does it have to do with the initialization order of static const class members? Or something else? Additionally, both variants work correctly with clang when using a built-in type like 'int'. Any help in understanding the problem on hand would be greatly appreciated! Best Regards, mbw

3 5

Re: [Boost-users] [Multiprecision] Runtime assertion failure with clang++3.6.0 but not g++4.9.2
by mbw_bst＠mailbox.org 09 Feb '16

09 Feb '16

Hello again and thanks for your replies! Taking the following two statements into account: > For type int, the values are computed recursively at compile time, for a > user-defined-type the values are computed at runtime and you hit > initialization-order issues. > Seems to be that Multiprecision relies on static data that haven't > (necessarily) been initialized before your own static members. Works > fine > if the members are made non-static: Does that mean that, since a) boost::multiprecision::number<gmp_int> is not constexpr enabled, and b) static initialization can't happen at compile-time for user-defined types, that there is no way for me to initialize a variable of this type at compile-time? Does b) follow logically from a) ? I (believe to have) confirmed runtime-initialization by running valgrind, which showed the presence of dynamic memory allocations (and also jumps depending on uninitialized variables, which probably corresponds to the assertion failure). I am mentioning this because initially my little test program looked somewhat like this: #include <iostream> #include <vector> #include <boost/multiprecision/gmp.hpp> namespace bm = boost::multiprecision; template<std::size_t N> struct factorial { static const bm::mpz_int value; static void add_values(std::vector<bm::mpz_int>& vec) { factorial<N-1>::add_values(vec); vec.push_back(value); } }; template<std::size_t N> const bm::mpz_int factorial<N>::value = N * factorial<N-1>::value; template<> struct factorial<std::size_t{0}> { static const bm::mpz_int value; static void add_values(std::vector<bm::mpz_int>& vec) { vec.push_back(value); } }; const bm::mpz_int factorial<0>::value = 1; int main () { std::vector<bm::mpz_int> fac_table{}; factorial<10'000>::add_values(fac_table); std::cout << "Enter a number between 0 and 10'000 to calculate factorial:"; std::size_t number; std::cin >> number; std::cout << '\n' << number << "! == " << fac_table[number] << '\n'; return 0; } This still includes the "unsafe" static initialization of a user-defined type. However it compiles and runs via g++ -ansi -std=c++14 -O3 -Wall -Wextra -pedantic -static -save-temps -ftemplate-depth-50000 -DNDEBUG -o main main.cpp -lgmp -pthread This was what made me believe in the compile-time computation of the factorials in the first place, since using this version, valgrind does not show any dynamic memory allocation at all. On the other hand, I don't understand what's going on here really, especially since std::vector<> is supposed to allocate memory at run-time. Now I'm not sure whether the last example has anything to do with Boost.Multiprecision anymore, so while it would really make my day if you could help me better understand this, I will understand if this is not the right place to ask these questions. Thanks again for your replies so far, they have been of great help! Cheers, Max

2 1

[gsoc16] ATTN: Project ideas deadline 19th Feb
by Niall Douglas 07 Feb '16

07 Feb '16

Tomorrow 8th February the application period for Google Summer of Code 2016 begins, and yet we have just *one* idea on the ideas page: https://svn.boost.org/trac/boost/wiki/SoC2016 We need *plenty* more if we are to be approved again this year as a Google Summer of Code org, the deadline for which is the 19th February. So if you have some project ideas and think you could mentor a student this summer, *please* consider adding a project idea to the ideas list or stepping forward with a list of Boost libraries or topics you'd be willing to mentor. Our thanks in advance. --- Boost C++ Libraries Google Summer of Code 2016 admin https://svn.boost.org/trac/boost/wiki/SoC2016

1 0

download from sourceforge?
by Dan Bloomquist 07 Feb '16

07 Feb '16

I followed the link form boost.org and then through sourceforge. But sourceforge directed me to: <http://downloadbud.com/?adprovider=sourceforge_fwint&source=fw36_300x250-do…> The link is an executable! I've never heard of 'downloadbud'. Not a big deal for now, I'm running with 1.58. But I'd like to get the latest of spirit x3 before I ask questions on the spirit list that may not need asking. Is there another source for boost? Or, is this executable actually a safe extractor? Sourceforge handing over an exe when it should be be a package seems just wrong... Thanks, Dan.

2 5

Boost and v8
by Daniel Burchardt 06 Feb '16

06 Feb '16

Hi, I try create v8 module to python used boost and i have problem: #include <iostream> using namespace std; #include <stdio.h> #include <stdlib.h> #include <string.h> #include "include/libplatform/libplatform.h" #include "include/v8.h" using namespace v8; const char* say_hello(const char* name) { return name; } #include <boost/python/module.hpp> #include <boost/python/def.hpp> #include <boost/python/class.hpp> using namespace boost::python; BOOST_PYTHON_MODULE(hello) { class_<V8, boost::noncopyable>("V8", no_init) .def("Initialize", &V8::Initialize).staticmethod("Initialize"); def("say_hello", say_hello); } compile process is ok but when i try import hello in python i see error: /hello.so: undefined symbol: _ZN2v82V810InitializeEv Thanks for help

2 1

[MSM][MPL] Can't compile FSM with > 20 transitions (solved)
by Carlos Santos 05 Feb '16

05 Feb '16

Hi there, I am using boost v1.59 and I am having trouble in compiling a MSM state machine with more than 20 transitions. I followed the Q&A and added the following lines BEFORE any boost include: #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS #define BOOST_MPL_LIMIT_VECTOR_SIZE 30 // or whatever you need #define BOOST_MPL_LIMIT_MAP_SIZE 30 // or whatever you need but now instead of getting the previous error: error: wrong number of template arguments (21, should be 20) I get this one: /usr/local/include/boost/multi_index/tag.hpp:75:67: error: wrong number of template arguments (30, should be 20) mpl::vector<BOOST_PP_ENUM_PARAMS(BOOST_MULTI_INDEX_TAG_SIZE,T)>, I was just finishing this email when I found a solution. Adding only the following header #include "boost/mpl/vector/vector30.hpp" and explicitly declaring the transition table as a numbered mpl::vector (yep you have to count the rows...) struct transition_table : mpl::vector21< ... > solves the problem. Can you suggest me a better solution for this? Thanks! *Carlos Santos *

1 0

[Test] BOOST_CHECK_EQUAL can't compare scoped enumerations
by Merrill Cornish 05 Feb '16

05 Feb '16

I'm running Windows 10, 64-bit, MinGW64 with GCC 5.3 64-bit, and BOOST_1_60_0 64-bit. Here is the stripped down version of what's failing: enum class UsedFor { NOTIFY_INPUT, CONST_INPUT, VAR_INPUT, NOTIFY_RESULT, VAR_RESULT}; UsedFor mUse = UsedFor::NOTIFY_INPUT; BOOST_CHECK(mUse == Operand::UsedFor::NOTIFY_INPUT); // BOOST_CHECK_EQUAL(mUse, Operand::UsedFor::NOTIFY_INPUT); If BOOST_CHECK_EQUAL() is commented out, BOOST_CHECK() complies and executes without error. However, // BOOST_CHECK(mUse == Operand::UsedFor::NOTIFY_INPUT); BOOST_CHECK_EQUAL(mUse, Operand::UsedFor::NOTIFY_INPUT); If BOOST_CHECK() is comment out, BOOST_CHECK_EQUAL() gets a template barf with the general comment, " template argument deduction/substitution failed:". Here are some of the complaints: D:\Boost_1_60_0/boost/test/tools/detail/print_helper.hpp:50:14: note: cannot convert 't' (type 'const DiGSE::Operand_Class_Test_Suite::Operand_Default_Constructor_Test::test_method()::UsedFor') to type 'std::_Setw' ostr << t; ^ D:/Program Files/mingw-w64/x86_64-5.3.0-posix-seh-rt_v4-rev0/mingw64/x86_64-w64-mingw32/include/c++/iomanip:208:5: note: candidate: template<class _CharT, class _Traits> std::basic_ostream<_CharT, _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&, std::_Setprecision) operator<<(basic_ostream<_CharT, _Traits>& __os, _Setprecision __f) D:\Boost_1_60_0/boost/test/tools/detail/print_helper.hpp:50:14: note: cannot convert 't' (type 'const DiGSE::Operand_Class_Test_Suite::Operand_Default_Constructor_Test::test_method()::UsedFor') to type 'std::_Setprecision' ostr << t; ^ At this point, it seems to be complaining about every io manipulator in existence. D:\Boost_1_60_0/boost/test/tools/detail/print_helper.hpp:50:14: note: mismatched types 'const std::piecewise_linear_distribution<_RealType>' and 'const DiGSE::Operand_Class_Test_Suite::Operand_Default_Constructor_Test::test_method()::UsedFor' ostr << t; Then it gets to the point of, apparently, dragging out all of the error messages it doesn't get to use very often: mismatched types*'const std::chi_squared_distribution<_RealType>' *and 'const DiGSE::Operand_Class_Test_Suite::Operand_Default_Constructor_Test::test_method()::UsedFor' ostr << t; ^ For the time being, I can simply use the explicit == check, but it looks like there's a problem here. Merrill Cornish

2 3

[ANN] build2 - C++ build toolchain
by Boris Kolpackov 03 Feb '16

03 Feb '16

Hi, build2 is an open source, cross-platform toolchain for building and packaging C++ code. It includes a build system, package manager, and repository web interface. We've also started cppget.org, a public repository of open source C++ packages. This is the first alpha release and currently it is more of a technology preview rather than anything that is ready for production. We have tested this version on various Linux'es, Mac OS, and FreeBSD. There is no Windows support yet (but cross-compilation is supported). The project's page is: https://build2.org For those who need to see examples right away, here is the introduction: https://build2.org/build2-toolchain/doc/build2-toolchain-intro.xhtml Enjoy, Boris

1 0

BOOST_LOG_TRIVIAL destination change
by Marc Paschover 02 Feb '16

02 Feb '16

I am working on a native Excel add-in (using XLW+), and I have been using Boost.Logging to output some diagnostic information, using BOOST_LOG_TRIVIAL. I would like to see this information in the Output window of Visual Studio. It seems like I somehow need to change the destination to boost::logging::destination::dbg_window, but I haven't been able to figure out a way to do this globally. Is there a way to do this? Thanks, Marc.

1 0

Boost 1.60: boost::archive::iterators bug?
by Ernest Zaslavsky 02 Feb '16

02 Feb '16

Hi, Recently I've noticed that Base64 encoded data produced by implementation I use and implementation used by chromium project sometimes are not the same. It happened only once but it was enough for me to start worrying. The implementation is quite simple, and I guess borrowed it from somewhere, like SO or something. The code as following: using it_base64_t = bai::base64_from_binary<bai::transform_width<std::string::const_iterator, 6, 8>>; namespace bai = boost::archive::iterators; auto writePaddChars = (3 - input.length() % 3) % 3; std::string base64(it_base64_t(input.begin()), it_base64_t(input.end())); base64.append(writePaddChars, '='); simple and elegant. However, today I wrote a short test which takes a chapter from 'Alice's Adventures in Wonderland' and encodes it. As well, I used two different online encoder to encode the same text, both online encoders produce the same data. However above code produced the same code until character 1029 and then it is different from what it should be. Then later, it gets back to the same output as produced by online encoders. So my question is, any chance it is a bug in archive::iterators or it is something in the above code? Coliru is down, so, full code is here http://pastebin.com/JxMsMeV2 [Read More]<http://feeds.feedburner.com/~r/sizmek-blog/~6/1> [http://www.sizmek.com/Sizmek.png]<http://www.sizmek.com/>

1 0

Building Boost 1.60 with VS2015 - 32 bit compiler is always selected
by Tiago Gehring 01 Feb '16

01 Feb '16

Hi, I'm trying to build Boost 1.60 with Visual Studio 2015 Update 1 in 64-bit mode but it seems to be ignoring the address-model=64 parameter and always builds a 32-bit version (I called b2 from the VS2015 Native tools for x64 command prompt): -- C:\Users\Tiago\code\boost_1_60_0>*b2 --toolset=msvc-14.0 variant=release link=static threading=multi address-model=64 architecture=x86* Performing configuration checks *- 32-bit : yes* - arm : no - mips1 : no - power : no - sparc : no - x86 : yes .... C:\Users\Tiago\code\boost_1_60_0>*cl* Microsoft (R) C/C++ Optimizing Compiler *Version 19.00.23506 for x64* Copyright (C) Microsoft Corporation. All rights reserved. usage: cl [ option... ] filename... [ /link linkoption... ] --- I saw in some ond discussion mentions to explicitly select the compiler version (I also have VS2010 and VS2012 installed) and environment variables batch file (in the project-config.jam file) but this didn't help either. Any help is really appreciated. Best regards, Tiago Gehring

4 4

Re: [Boost-users] asio: implementing sock->receive like behavior eith async_read_some
by Bjorn Reese 01 Feb '16

01 Feb '16

On 01/28/2016 01:56 PM, Lloyd wrote: > I am using asio to read some data from SSL socket. asio tcp socket > implements a "receive" function, but ssl socket doesn't have an > implementation for "receive". In the code sample given below I wish to > implement this kind of behavior. > > eg > > { > ... > sock.async_read_some(...); > //continue the execution only after the above call finishes. > } Why are you using an asynchronous operation instead of simply calling ssl::stream::read_some()?

2 1

C++Now 2016 Registration is Open
by Jon Kalb 28 Jan '16

28 Jan '16

Boost Users, Registration is now open for this year¹s C++Now (put on by Boost). http://cppnow.org/2016-conference/announcements/2016/01/28/registration-is-o pen.html The conference has sold out the last three years and is expect to do say again this year. Do not put off registering. Note that session submitters should not register until they receive instructions from Marshall Clow, our conference registrar. See you in Aspen! Jon

1 0

asio: implementing sock->receive like behavior eith async_read_some
by Lloyd 28 Jan '16

28 Jan '16

Hi, I am using asio to read some data from SSL socket. asio tcp socket implements a "receive" function, but ssl socket doesn't have an implementation for "receive". In the code sample given below I wish to implement this kind of behavior. eg { ... sock.async_read_some(...); //continue the execution only after the above call finishes. } Whats the best way to do this? I tried "future" but the code blocks/dead locks some how, The I tried "spawn", but in this case also I don't know the method to wait for the coroutine to finish. Some tips are greatly appreciated. Thanks, Lloyd

1 0

[Boost.LexicalCast] problem with 1.59 in Solaris
by dariomt＠gmail.com 28 Jan '16

28 Jan '16

Trying to compile file libs/date_time/src/gregorian/greg_month.cpp I get an error related to Boost.LexicalCast. I have reduced the problem to a minimal test case: #include <string> #include <boost/lexical_cast.hpp> void f(const char* s) { std::string s1(boost::lexical_cast<std::string>(s)); } My feeling is that this compiler has problems in the specializations for boost::detail::is_stdstring and boost::detail::is_char_array_to_stdstring. If I remove all those specializations the error goes away. I assume this is not the perfect solution because I guess this will miss some optimization of lexical_cast, but at least I can compile it this way :( Is there a better solution for this? Has this problem been fixed in 1.60? Error message (full instantiation stack available if needed): "/ThirdPartyLibs/boost/1_59_0/boost/lexical_cast/try_lexical_convert.hpp", line 146: Error: Ambiguous partial specialization for boost::detail::is_char_array_to_stdstring<std::string, const char*>, boost::detail::is_char_array_to_stdstring<boost::container::basic_string<boost::detail::CharT, boost::detail::Traits, boost::detail::Alloc>, const boost::detail::CharT*> and boost::detail::is_char_array_to_stdstring<std::basic_string<boost::detail::CharT, boost::detail::Traits, boost::detail::Alloc>, const boost::detail::CharT*>. "/ThirdPartyLibs/boost/1_59_0/boost/lexical_cast.hpp", line 42: Where: While instantiating "boost::conversion::detail::try_lexical_convert<std::string, const char*>(const char*const&, std::string &)". "/ThirdPartyLibs/boost/1_59_0/boost/lexical_cast/try_lexical_convert.hpp", line 134: Error: Ambiguous partial specialization for boost::detail::is_stdstring<std::string>, boost::detail::is_stdstring<boost::container::basic_string<boost::detail::CharT, boost::detail::Traits, boost::detail::Alloc>> and boost::detail::is_stdstring<std::basic_string<boost::detail::CharT, boost::detail::Traits, boost::detail::Alloc>>. "/ThirdPartyLibs/boost/1_59_0/boost/lexical_cast.hpp", line 42: Where: While instantiating "boost::conversion::detail::try_lexical_convert<std::string, const char*>(const char*const&, std::string &)".

5 9

Regression with boost::python 1.60
by Emmanuel 28 Jan '16

28 Jan '16

Hello, I am not sure if this is the right place to do it, but I will try :-). I am having a regression in boost 1.60, I documented a small reproducer here: http://stackoverflow.com/questions/35056398/typeerror-when-iterating-over-a… Does anyone have a clue ? Cheers, Emmanuel

1 0

[Odeint] Stiff System of differential equations
by jules 25 Jan '16

25 Jan '16

Hi all, I am currently working with a very large set of differential equations; it is a disease model with 20160 classes depending on which vaccine has been admnistered, history of infection, and age. To solve this I have been using the runge_kutta_fehlber78 controlled stepper with the integrate_const function. There I need to set the absolute_error, relative_error and the step_size. My issue is that the results from the solver seems to depend highly on the step_size and whether or not an observer is provided. Since the solver is adaptive I feel like the results should not depend on step_size and they should definitely not depend on the presence of an observer. My question is why would the results be related to the step_size or the observer? How would it be possible to get the same results regardless of the step_size and the presence of an observer? Could this be related to the system being stiff and if so how would it be possible to solve it (The jacobian is too complicated to calculate because of the population dynamics)? Any help would be appreciated. Many thanks, Jules

3 5

BGL, shortest path between two nearby nodes in a huge graph
by Paolo Bolzoni 25 Jan '16

25 Jan '16

Dear list, I am a happy user of BGL, but recently I got stuck in a strange problem. I think I am missing the obvious, so I'll be happy to read the fine manual if it's the case. Just point me to the right direction. I need to find the shortest path between two nodes, for doing so I am using dijkstra with a custom visitor that stops the search (throwing an exception) when examine_vertex is called on the destination node. It worked fine, but it run strangely slow. After some profiling, it is clear that most of the time is used in the initialize_vertex function. The graph is fairly large, but the path I am looking for are fairly small (10 edges tops usually). It is possible to skip the initialize phase? Cheers, Paolo

3 5

Some help for betweenness centrality for undirected weighted graph
by Xinran Wang 25 Jan '16

25 Jan '16

Hi everyone, this is from Jason. I am a new user of Boost library. Nowadays, I am doing a research about betweenness centrality measure. I am very confused about how to use boost to calculate the betweenness centrality. I need to calculate the centrality score based on a undirected and weighted graph. The following code is what I tried to do. But this block of code can only be used for calculated for unweighted graph. Could anyone here can offer me examples? Thanks for any reply. #include <boost/graph/betweenness_centrality.hpp> #include <boost/graph/adjacency_list.hpp> #include <boost/graph/graphviz.hpp> typedef boost::property<boost::edge_weight_t, float> EdgeWeightProperty; typedef boost::adjacency_list < boost::listS, boost::vecS, boost::undirectedS, boost::no_property, EdgeWeightProperty > Graph; typedef boost::graph_traits < Graph >::vertex_descriptor vertex_descriptor; typedef boost::graph_traits < Graph >::edge_descriptor edge_descriptor; typedef std::pair<int, int> Edge; typedef std::map<Edge, int> StdEdgeIndexMap; void betweennessCentrality() { Graph g; Graph::vertex_descriptor a1 = boost::add_vertex(g); Graph::vertex_descriptor a2 = boost::add_vertex(g); Graph::vertex_descriptor a3 = boost::add_vertex(g); Graph::vertex_descriptor a4 = boost::add_vertex(g); Graph::vertex_descriptor a5 = boost::add_vertex(g); Graph::vertex_descriptor a6 = boost::add_vertex(g); Graph::vertex_descriptor a7 = boost::add_vertex(g); EdgeWeightProperty weight0 = 1; boost::add_edge(a1, a2, weight0, g); EdgeWeightProperty weight1 = 1; boost::add_edge(a1, a3, weight1, g); EdgeWeightProperty weight2 = 1; boost::add_edge(a2, a3, weight2, g); EdgeWeightProperty weight3 = 1; boost::add_edge(a3, a4, weight3, g); EdgeWeightProperty weight4 = 1; boost::add_edge(a4, a5, weight4, g); EdgeWeightProperty weight5 = 1; boost::add_edge(a5, a6, weight5, g); EdgeWeightProperty weight6 = 1; boost::add_edge(a5, a7, weight6, g); EdgeWeightProperty weight7 = 1; boost::add_edge(a6, a7, weight7, g); typedef boost::property_map< Graph, boost::vertex_index_t>::type VertexIndexMap; VertexIndexMap v_index = get(boost::vertex_index, g); std::vector< double > v_centrality_vec(boost::num_vertices(g), 0.0); boost::iterator_property_map< std::vector< double >::iterator, VertexIndexMap > v_centrality_map(v_centrality_vec.begin(), v_index); brandes_betweenness_centrality( g, v_centrality_map); }

1 0