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

Trouble Updating Boost to run OpenFOAM
by Blair Climenhaga 10 Jun '16

10 Jun '16

Hello Everyone, I have recently begun using OpenFOAM which requires boost for some of its functions, however upon installing OpenFOAM it appears that some of the needed Boost contents are not in my usr/include/boost such as the directories container, move, intrusive, core and many others. I have attempted to update boost in multiple ways so that these directories are added to the boost directory however I have had no success. The two types of attempts I have made are listed below. 1. Using … [View More]

4 12

[boost] [thread] thread handling question
by Markus Pieper 09 Jun '16

09 Jun '16

Hi, this may be a very dumb question… My boost version is 1.56.0. In my program I use a database logging technique. To avoid blocking the main thread, I coded this: int main() { while(bDoCalculations == true) { // calculate some stuff m_Logger->doLogging(); } } void CLoggingData::doLogging() { std::vector<float>* Result; // fill Result boost::thread (&… [View More]

4 6

Another query on Boost DLL Library
by Leo Carreon 09 Jun '16

09 Jun '16

Hi, When using the factory method when creating a plugin, is it possible to pass an argument to the factory method? If yes, how? Kinds regards, Leo

1 0

Re: [Boost-users] Query on Boost DLL Library
by Leo Carreon 09 Jun '16

09 Jun '16

After a bit more reading of the documentation, my understanding is std::shared_ptr can be used but not std::experimental::filesystem because boost::filesystem is an argument to boost::dll::import_alias. In light of this, can I request a revision to the Boost DLL Library. Can boost::filesystem be replaced with either std::experimental::filesystem or std::filesystem. whichever is available on the version of the compiler being used? The reason for this is so that there is only one version of … [View More]

1 0

Query on Boost DLL Library
by Leo Carreon 09 Jun '16

09 Jun '16

Hi, In Boost DLL Library factory method example it uses boost::shared_ptr and boost::filesystem, can these be replaced by std::shared_ptr and std::experimental::filesystem? Kind regards, Leo

1 0

Re: [Boost-users] [boost] RFC : About forking a C++11 standard library and adapt it to C++98 compilers
by Vicente J. Botet Escriba 07 Jun '16

07 Jun '16

Le 06/06/2016 à 11:16, Joseph Van Riper a écrit : > On Thu, Jun 2, 2016 at 6:09 PM Vicente J. Botet Escriba < > vicente.botet(a)wanadoo.fr> wrote: > >> Hi, >> >> Some of us have to work yet with C++98 compiler at work (due to well >> know reasons) and this for a long time. This is a reality. >> >> I was wondering about forking a public domain C++11/14/17 standard >> library and adapt it to C++98 compilers. This library could be seen as &… [View More]gt;> another TR1, an extension of the C++03 standard library. >> >> Does this make any sens? Would this project be of interest for the >> Boost/C++ community? >> > Yes. At least for what we do where I work. > > The cyber-security field works with very old machines, either for forensics > (people forget they have some old machine until it gets hacked and some old > process that always "just worked" stops working), teaching (teaching old, > outmoded techniques helps to illustrate cyber security problems without > giving people tools for modern exploitation), or competitions. > > I kind of hate having to work with clunky, antediluvian C++ compilers that > magnify the level of woe required to deal with old machinery. Especially > while the rest of the C++ world moves on to the spiffy-shiny features found > in the later compilers. Having at least a library that helps us use some > of those nifty features can help us use our skills on more modern projects > when we move on to another job, while easing the efforts required to do our > work. A library wouldn't change your compiler ;-), but it could change the way you program :). > > Anyway, if you find that this will be useful to you at your work we will >> need your participation. Would you be interested in working on it? > > Hmmm... am I even knowledgeable enough? > > While I may find myself learning quite a lot about C++ by studying the > boost code people write, I am also humbled by what I see there. I fear I > am only beginning to dip into some of the intermediate meta-programming > techniques that seem to confer tremendous power to this language. > > as a Boost community project? >> outside Boost, as an independent project? >> > Hmmm... > > The boost 'brand' confers a certain gravitas. If you wish to maintain this > gravitas in the new library, I'd say keep the boost brand, but require the > same rigor. We have a License issue, so it couldn't be a Boost library :( Vicente P.S. Please, contact me privately if you are interested. [View Less]

1 0

[BGL] breadth_first_search with distance record and predecessors?
by The Maschine 06 Jun '16

06 Jun '16

Hi all, Im trying to cover the dijkstra_shortest_paths call I usually do with a BFS. Id like to get back the predecessors so I can rebuild the paths and the distance to each vertex. The dijkstra_shortest_paths work for me fine! I tried a couple of BFS calls but I always get errors. What am I missing? std::vector<Vertex> predecessors(boost::num_vertices(m_ugraph)); // To store parents std::vector<Weight> distances(boost::num_vertices(m_ugraph), std::… [View More]

1 0

Boost.Fiber mini-review May 23 - June 1: review report
by Nat Goodspeed 06 Jun '16

06 Jun '16

The Boost.Fiber mini-review is now closed. Results: Bjorn Reese: YES Niall Douglas (private): YES Agustín K-ballo Bergé: YES Niall Douglas reminds me that in a previous mini-review he already voted to accept the Fiber library. Unless he stated that he had changed his mind, it would be reasonable to carry forward that "yes" vote. However, he did reaffirm his previous stance. In that spirit, let me remind the community of another couple previous positive votes: Eugene Yakubovich Antony … [View More]

3 3

Boost fusion problem
by Jess Morecroft 05 Jun '16

05 Jun '16

Hi guys, We're trying out the latest version of Boost (1.61, migrating from 1.55) and have some code calling the fusion library that now doesn't compile and it's not obvious (to me at least) why. I've created a simple program (below) to demonstrate the issue. As per the compile/run section below, this compiles and runs with Boost 1.55, not with 1.61. If anyone has any idea or pointers to what is wrong here I'd really appreciate it. Sorry if this isn't the right forum for this kind of issue … [View More]too - if so please let me know how best to seek help on this. Regards Jess ******************** main.cpp #include <boost/fusion/algorithm/iteration/for_each.hpp> #include <boost/fusion/view/zip_view.hpp> #include <boost/fusion/tuple.hpp> #include <iostream> #include <string> struct Helper { template<typename Arg> void operator()(const Arg& arg) const { std::cout << boost::fusion::get<0>(arg) << std::endl; std::cout << boost::fusion::get<1>(arg) << std::endl; } }; int main() { const int myint(123); const double mydub(456.0); const std::string mystr("blah"); const bool mybool(false); typedef boost::fusion::tuple<const int&, const double&> Tuple1; typedef boost::fusion::tuple<const std::string&, const bool&> Tuple2; typedef boost::fusion::tuple<const Tuple1&, const Tuple2&> Tuple3; Helper helper; boost::fusion::for_each( boost::fusion::zip_view<Tuple3>( Tuple3(Tuple1(myint, mydub), Tuple2(mystr, mybool))), helper); return 0; } ******************** compile/run tests jess@flathead:~$ g++ --version g++ (Ubuntu 5.3.1-14ubuntu2) 5.3.1 20160413 Copyright (C) 2015 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. (boost 1.55) jess@flathead:~$ g++ -std=c++14 main.cpp jess@flathead:~$ ./a.out 123 blah 456 0 (boost 1.61) jess@flathead:~$ g++ -std=c++14 main.cpp In file included from /usr/local/include/boost/fusion/container/vector/vector10.hpp:25:0, from /usr/local/include/boost/fusion/view/transform_view/transform_view.hpp:22, from /usr/local/include/boost/fusion/algorithm/transformation/transform.hpp:11, from /usr/local/include/boost/fusion/view/zip_view/detail/begin_impl.hpp:14, from /usr/local/include/boost/fusion/view/zip_view/zip_view.hpp:16, from /usr/local/include/boost/fusion/view/zip_view.hpp:12, from main.cpp:2: /usr/local/include/boost/fusion/container/vector/vector.hpp: In instantiation of ‘constexpr boost::fusion::vector_detail::vector_data<std::integer_sequence<long unsigned int, _Idx ...>, T ...>::vector_data(boost::fusion::vector_detail::each_elem, U&& ...) [with U = {const boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>&}; long unsigned int ...I = {0ul, 1ul}; T = {const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&}]’: /usr/local/include/boost/fusion/container/vector/vector.hpp:305:97: required from ‘boost::fusion::vector<T>::vector(U&& ...) [with U = {const boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>&}; T = {const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&}]’ /usr/local/include/boost/fusion/view/zip_view/zip_view.hpp:128:30: required from ‘constexpr boost::fusion::zip_view<Sequences>::zip_view(const Sequences&) [with Sequences = boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>]’ main.cpp:32:64: required from here /usr/local/include/boost/fusion/container/vector/vector.hpp:230:52: error: mismatched argument pack lengths while expanding ‘boost::fusion::vector_detail::store<I, T>’ : store<I, T>(std::forward<U>(var))... ^ /usr/local/include/boost/fusion/container/vector/vector.hpp: In instantiation of ‘constexpr boost::fusion::vector_detail::store<<anonymous>, T>::store() [with long unsigned int <anonymous> = 0ul; T = const boost::fusion::tuple<const int&, const double&>&]’: /usr/local/include/boost/fusion/container/vector/vector.hpp:230:52: required from ‘constexpr boost::fusion::vector_detail::vector_data<std::integer_sequence<long unsigned int, _Idx ...>, T ...>::vector_data(boost::fusion::vector_detail::each_elem, U&& ...) [with U = {const boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>&}; long unsigned int ...I = {0ul, 1ul}; T = {const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&}]’ /usr/local/include/boost/fusion/container/vector/vector.hpp:305:97: required from ‘boost::fusion::vector<T>::vector(U&& ...) [with U = {const boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>&}; T = {const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&}]’ /usr/local/include/boost/fusion/view/zip_view/zip_view.hpp:128:30: required from ‘constexpr boost::fusion::zip_view<Sequences>::zip_view(const Sequences&) [with Sequences = boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>]’ main.cpp:32:64: required from here /usr/local/include/boost/fusion/container/vector/vector.hpp:137:24: error: value-initialization of reference type ‘const boost::fusion::tuple<const int&, const double&>&’ : elem() // value-initialized explicitly ^ /usr/local/include/boost/fusion/container/vector/vector.hpp: In instantiation of ‘constexpr boost::fusion::vector_detail::store<<anonymous>, T>::store() [with long unsigned int <anonymous> = 1ul; T = const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&]’: /usr/local/include/boost/fusion/container/vector/vector.hpp:230:52: required from ‘constexpr boost::fusion::vector_detail::vector_data<std::integer_sequence<long unsigned int, _Idx ...>, T ...>::vector_data(boost::fusion::vector_detail::each_elem, U&& ...) [with U = {const boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>&}; long unsigned int ...I = {0ul, 1ul}; T = {const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&}]’ /usr/local/include/boost/fusion/container/vector/vector.hpp:305:97: required from ‘boost::fusion::vector<T>::vector(U&& ...) [with U = {const boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>&}; T = {const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&}]’ /usr/local/include/boost/fusion/view/zip_view/zip_view.hpp:128:30: required from ‘constexpr boost::fusion::zip_view<Sequences>::zip_view(const Sequences&) [with Sequences = boost::fusion::tuple<const boost::fusion::tuple<const int&, const double&>&, const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&>]’ main.cpp:32:64: required from here /usr/local/include/boost/fusion/container/vector/vector.hpp:137:24: error: value-initialization of reference type ‘const boost::fusion::tuple<const std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, const bool&>&’ [View Less]

2 3

Re: [Boost-users] [boost] RFC : About forking a C++11 standard library and adapt it to C++98 compilers
by Vicente J. Botet Escriba 03 Jun '16

03 Jun '16

Le 03/06/2016 à 01:35, Edward Diener a écrit : > On 6/2/2016 6:09 PM, Vicente J. Botet Escriba wrote: >> Hi, >> >> Some of us have to work yet with C++98 compiler at work (due to well >> know reasons) and this for a long time. This is a reality. >> >> I was wondering about forking a public domain C++11/14/17 standard >> library and adapt it to C++98 compilers. This library could be seen as >> another TR1, an extension of the C++03 standard … [View More]

1 0

RFC : About forking a C++11 standard library and adapt it to C++98 compilers
by Vicente J. Botet Escriba 03 Jun '16

03 Jun '16

Hi, Some of us have to work yet with C++98 compiler at work (due to well know reasons) and this for a long time. This is a reality. I was wondering about forking a public domain C++11/14/17 standard library and adapt it to C++98 compilers. This library could be seen as another TR1, an extension of the C++03 standard library. Does this make any sens? Would this project be of interest for the Boost/C++ community? I have not a clear idea of the cost of doing this work, how it should be … [View More]

2 2

[build] error: target { link%link.do-link-recursively-chrono/stopwatches-headers. } has no type
by Nat Goodspeed 02 Jun '16

02 Jun '16

Steven, what do these errors mean, and how can I fix them? https://travis-ci.org/BorisSchaeling/boost-process/builds/134823441 This travis script is trying to embed the candidate Boost.Process library in a boost_1_61_0 tarball tree and build libs/process/test. But I must admit I've been stumped by similar errors several times before. /home/travis/build/BorisSchaeling/boost-process/boost_1_61_0/tools/build/src/build/generators.jam:1102: in ensure-type from module generators error: target { … [View More]

2 1

Linker error when using time_from_string
by nick.snels＠telenet.be 02 Jun '16

02 Jun '16

The following code gives an error for the time_from_string function (from_time_t works just fine): using namespace boost::posix_time; ptime epoch = from_time_t(0); ptime other = time_from_string("2011-08-09 17:27:00.000000"); The error is: main.obj:-1: error: LNK2019: unresolved external symbol "public: static class boost::shared_ptr<class std::map<class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >,unsigned short,struct std::less&… [View More]

1 0

installing on a local 2 core system
by Salvador Aguiñaga 30 May '16

30 May '16

> Installing on small system I want to use for temporary development, I get the following error. > > >parallel-bgl-0.7.0/boost/property_map/property_map.hpp:16:37: fatal error: boost/pending/cstddef.hpp: No such file or directory > compilation terminated > > I've configured the system: > >"sudo apt-get install build-essential" > > And successfully installed the openmpi: "openmpi-1.10.2.tar.bz2" > > But when I get to: > /parallel-bgl-0.7.0/build/… [View More]

1 0

[proto] non-proto objects as terminals
by Igor R 30 May '16

30 May '16

I would like to use instances of a non-proto class as proto terminals for all purposes. To enable this functionality, I use is_terminal metafunction that I pass to BOOST_PROTO_DEFINE_OPERATORS(). This actually defines the operators, so the following expression makes an expression tree, as expected: non_proto_obj * proto_obj; However, I cannot do this: non_proto_obj = proto_obj; Or this: non_proto_obj[proto_obj]; While the opposite does compile: proto_obj = non_proto_obj; proto_obj[… [View More]

1 0

Boost.Fiber mini-review May 23 - June 1
by Nat Goodspeed 30 May '16

30 May '16

Hi all, The Boost.Fiber candidate library by Oliver Kowalke begins a mini-review today, Monday May 23, which will close Wednesday June 1. It was last reviewed in September 2015; the verdict at that time was "not yet." Oliver has been working steadily to address review comments and to improve the library in other ways, and has brought the library back for mini-review. The updated documentation is here: http://olk.github.io/libs/fiber/doc/html/index.html The code is on the master branch of … [View More]this repository: https://github.com/olk/boost-fiber/tree/master I believe it is Oliver's intention to respond to review feedback on the develop branch, leaving the master branch stable during the review. I will monitor reviews and discussion on both the boost-users@ list and the boost@ developers' list. Please include at least "fiber" and "review" in the subject line of your mail, e.g. by replying to this message. (Please reply to only ONE list, however.) I will also check the Boost Library Incubator for Fiber reviews: http://rrsd.com/blincubator.com/bi_library/fiber/?gform_post_id=859 though I check that less frequently than email. Please do remember to state in your review whether you think the library should be accepted as a Boost library. Thank you for your interest and your feedback! ----------------------------------------------------- Here follows a synopsis of issues raised during the September 2015 review: Cross-thread fiber migration: Evidently the community strongly desires the ability to transfer a suspended fiber from one thread to another. Now supported, with documentation. Cross-thread migration support implies a requirement to document the thread safety requirements of the customization API. Addressed. Standard required timing specifications: meet (30.2.4 Timing specifications [thread.req.timing]). Addressed. Adapt one or more existing test suites for thread facilities to validate the correctness of the Fiber library's synchronization constructs. The requester clarified in private mail that I misstated his suggestion: he wanted Oliver to review one or more such test suites to discover the kinds of issues that can arise with thread synchronization constructs. He has professed himself satisfied with the current state of the Fiber library's synchronization constructs. std::chrono support: ensure that wait_until() can accept any supported time_point specialization. Addressed. C++11 compatibility. Addressed. Document that this_fiber::yield() (et al.) are valid from main(), or in general from a thread function, as well as from explicitly-launched fibers. Addressed. Make shared_state lock requirements explicit: for example, make mark_ready_and_notify_() accept a std::unique_lock<>& (or &&) to force its caller to provide one. Addressed. Avoid holding mutex during condition_variable::notify_*() calls. Addressed. packaged_task must not decay-copy its task arguments. Addressed. Align fibers::async() signature, result description and invoke_helper implementation with std::async(). Avoid returning std::move(...). Addressed. Wait list implementation: try an intrusive linked list of fiber_context objects. Addressed. Avoid sleeping thread when no fibers are ready -- block on external event. Better handling of waiting tasks (decentralized wait queues?). Addressed. Optimization to resume awakened fiber on the thread that awakens it. Hooks provided. Template redundancy: eliminate duplication between specializations for T, T& and void. The future, shared_future, shared_state, promise and task_object templates were specifically cited. Addressed. Leverage predicate-based condition::wait() overload internally. Addressed. Nested schedulers: make schedulers be schedulable entities themselves. Not implemented. Improve robustness of `promise' handling in Asynchronous Callbacks documentation. Avoid overconfident remarks about it. Addressed. Fix Note overstating the requirements on condition_variable::wait(). Addressed. [View Less]

1 2

[test] how to test std::pair with BOOST_TEST
by Tan, Tom (Shanghai) 29 May '16

29 May '16

The following snippet does not compile with VS2015 and boost 1.61. What should the correct way to do it? Thanks. // compile with cl.exe /EHSc #define BOOST_TEST_MODULE pair #include <boost/test/included/unit_test.hpp> std::pair<uint32_t, uint32_t> v() { return std::make_pair(0, 0); } BOOST_AUTO_TEST_CASE(range) { BOOST_TEST(std::make_pair(0, 0) == v()); } Here's the error message: C:\3rd\boost_1_61_0\boost/test/tools/assertion.hpp(163): error C2678: binary '==': no … [View More]operator found which takes a left-hand operand of type 'std::pair<int,int>' (or there is no acceptable conversion) C:\3rd\boost_1_61_0\boost/function/function_base.hpp(740): note: could be 'bool boost::operator ==(boost::detail::function::useless_clear_type *,const boost::function_base &)' C:\3rd\boost_1_61_0\boost/function/function_base.hpp(728): note: or 'bool boost::operator ==(const boost::function_base &,boost::detail::function::useless_clear_type *)' C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\exception(329): note: or 'bool std::operator ==(const std::exception_ptr &,const std::exception_ptr &) throw()' [found using argument-dependent lookup] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\exception(334): note: or 'bool std::operator ==(std::nullptr_t,const std::exception_ptr &) throw()' [found using argument-dependent lookup] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\exception(339): note: or 'bool std::operator ==(const std::exception_ptr &,std::nullptr_t) throw()' [found using argument-dependent lookup] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\system_error(365): note: or 'bool std::operator ==(const std::error_code &,const std::error_code &) noexcept' [found using argument-dependent lookup] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\system_error(373): note: or 'bool std::operator ==(const std::error_code &,const std::error_condition &) noexcept' [found using argument-dependent lookup] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\system_error(381): note: or 'bool std::operator ==(const std::error_condition &,const std::error_code &) noexcept' [found using argument-dependent lookup] C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\INCLUDE\system_error(389): note: or 'bool std::operator ==(const std::error_condition &,const std::error_condition &) noexcept' [found using argument-dependent lookup] C:\3rd\boost_1_61_0\boost/function/function_base.hpp(799): note: or 'bool boost::operator ==<T>(Functor,const boost::function_base &)' with [ T=std::pair<int,int>, Functor=std::pair<int,int> ] C:\3rd\boost_1_61_0\boost/function/function_base.hpp(790): note: or 'bool boost::operator ==<T>(const boost::function_base &,Functor)' with [ T=std::pair<uint32_t,uint32_t>, Functor=std::pair<uint32_t,uint32_t> ] C:\3rd\boost_1_61_0\boost/test/tools/assertion.hpp(163): note: while trying to match the argument list '(std::pair<int,int>, std::pair<uint32_t,uint32_t>)' C:\3rd\boost_1_61_0\boost/test/tools/assertion.hpp(326): note: see reference to class template instantiation 'boost::test_tools::assertion::op::EQ<ValType,T,void>' being compiled with [ ValType=std::pair<int,int>, T=std::pair<uint32_t,uint32_t> ] s.cpp(14): note: see reference to class template instantiation 'boost::test_tools::assertion::binary_expr<ExprType,std::pair<uint32_t,uint32_t>,boost::test_tools::assertion::op::EQ<ValType,T,void>>' being compiled with [ ExprType=boost::test_tools::assertion::value_expr<std::pair<int,int>>, ValType=std::pair<int,int>, T=std::pair<uint32_t,uint32_t> ] C:\3rd\boost_1_61_0\boost/test/tools/assertion.hpp(377): warning C4624: 'boost::test_tools::assertion::binary_expr<ExprType,std::pair<uint32_t,uint32_t>,boost::test_tools::assertion::op::EQ<ValType,T,void>>': destructor was implicitly defined as deleted with [ ExprType=boost::test_tools::assertion::value_expr<std::pair<int,int>>, ValType=std::pair<int,int>, T=std::pair<uint32_t,uint32_t> ] [View Less]

4 4

Call for Papers for Meeting C++ 2016 ends on Friday night!
by Jens Weller 25 May '16

25 May '16

Hello Boost Community! a short reminder, that the deadline is coming up for submitting your talk to this years Meeting C++ conference! Meeting C++ 2016 Page: http://meetingcpp.com/index.php/mcpp2016.html Talk submission page: https://meetingcpp.com/mcpp/submittalk/ thanks, Jens Weller

1 0

File-mapped shared memory access through Boost interprocess is slow on some HPC file-systems due to mmap
by Scott Ritchie 24 May '16

24 May '16

Hi all, I'm wondering if there is some way to use the Boost interprocess library without the use of mmap for file I/O? I have developed an R-language package that uses another third party package (bigmemory) to access objects in shared memory when parallelising R across multiple cores. This third party package uses the Boost interprocess library to make these file-backed shared memory objects available to R. This worked perfectly, until I tested my package on a multi-node cluster. After some … [View More]

2 1

[Parallel Boost Graph Library] General Questions and Redistribution Questions
by Jun Kudo 24 May '16

24 May '16

Hi everyone, I've been playing around with the Parallel Boost Graph Library in hopes of using it for a distributed mesh with redistribution capabilities. Unfortunately, I've been having a lot of issues and I was hoping to get some clarification from the community on some points. I am trying to construct a distributed graph that represents a mesh. The idealized plan is to use this library to create a mesh class that allows for the easy introduction of new vertices and edges as well as … [View More]

1 0

Rebooting Boost: Call for Lightning Talks @ CppCon
by Niall Douglas 23 May '16

23 May '16

At C++ Now a number of informal meetings showed there to be frustrations with the current ecosystem around the Boost C++ Libraries (to paraphrase a founder of Boost, "Boost is supposed to serve *the entire C++ community; it isn't Boost's goal to serve Boost's community*". Recent and recurrent boost-dev discussions have raised the lack of cmake based tooling; lack of ABI management and the consequent ODR violation when mixing Boost versions in the same process; the anti-social behaviour … [View More]of Boost towards library end users, new ideas, new blood and the wider C++ community; and the chronic lack of maintenance of up to half the Boost libraries. One question which needs to be answered is whether a clean reboot of Boost from the first principles of proving high quality C++ libraries well suited for use with the latest C++ standard is viable. This new collection of C++ libraries would be started completely from scratch (even if some existing libraries were ported into the new organisation), so ANYTHING is possible. All we need is a critical mass of library developers willing to collaborate on developing a shared infrastructure mutually beneficial to all participants, whether library developer or library end user. To that end of discovering if this critical mass is there, five minute lightning talk topics are requested for CppCon this September on this topic: "What design pattern, practice or idiom should a standards aspiring collection of C++ 14/17 libraries share?" Please keep each talk topic focused on a single design pattern, practice or idiom (see suggested talk format below). Each speaker may submit up to THREE talk topics (not all may be accepted if there are a lack of slots, so please rank them in order of preference). Please send your talk topics to me privately by email, only if sufficient numbers present to fill a session will your name and your talk topic be shared with the CppCon Programme Committee. We'll try to arrange a short panel session at the end so attendees can ask questions of the speakers. After the lightning talk we'll arrange a restaurant so all the speakers and any interested attendees can dine together, followed by a night in a Bellevue bar. If after the dust has settled it is felt there is a critical mass sufficient to reboot a brand shiny new edition of Boost, we'll start development! I should *stress* that it is up to the CppCon Programme Committee whether these lightning talks are approved or not. I'll just copy and paste your proposed talk to the CppCon PC as-is. If insufficient lightning talk topics are received by me to fill a 60 minute session, I'll withdraw this talk proposal from CppCon. Suggested talk format ================ Five minutes is not much time, so here is a suggested lightning talk outline: 1. A current widely practiced library design pattern (show example). 2. The problems it generates for library users or maintainers. 3. Your proposed alternative design pattern (show example). 4. The problems the alternative design pattern fixes. 5. Any mockup, prototype or even live demo (!) of the alternative design pattern in action. Suggested talk themes might be documentation, packaging, distribution, testing, tooling, quality assessment, barriers to entry, governance, strategy, important gaps in the standard libraries, automation and deprecation/removal policies. Here is an example of such a lightning talk: 1. Current design pattern: Library v1.00: namespace boost { namespace lib { void foo(size_t, char); } } User code: boost::lib::foo(100, 'n'); 2. Problem: Library v1.01: namespace boost { namespace lib { void foo(char, size_t); } } User code: boost::lib::foo(100, 'n'); // oh oh! 3. Alternative: Library v1.00: namespace boost { namespace lib { inline namespace v100 { void foo(size_t, char); } } } #define BOOST_LIB_NAMESPACE_V100 boost::lib::v100 Library v1.01: namespace boost { namespace lib { inline namespace v101 { void foo(char, size_t); } } } #define BOOST_LIB_NAMESPACE_V101 boost::lib::v101 User code: // Mount v100 of Boost.Lib into "lib" namespace lib=BOOST_LIB_NAMESPACE_V100; lib::foo(100, 'n'); // ABI stable! No ODR violation possible! 4. Problems fixed: a) Mixing incompatible versions of individual Boost libraries in the same process (or even translation unit) is now safe. b) Libraries can now depend on other libraries without worrying about breaking code which depends on them which uses a different version of the same dependency. This greatly helps reduce change ripple effects. c) Forward compatibility or alternative implementation shims are now very easy to implement e.g. library users can externally configure either Boost.Filesystem or std::experimental::filesystem for your library to use, your code simply refers to _some_ Filesystem TS implementation e.g. namespace filesystem = FILESYSTEM_TS_IMPLEMENTATION; filesystem::path mypath; -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/ [View Less]

7 7

How to write one property page .props to select the right x86 or x64 Boost libraries folder automatically using Visual Studio
by Paul A. Bristow 22 May '16

22 May '16

I have downloaded the shiny new release boost_1_61_0_b1 and am trying to set up so that I can test a lot of Boost-ish console applications using both 32 and 64-bit. This is easier with bjam, but I'd like to use the Visual studio IDE too. I'd like a single property page that can be placed in the same folder as my .sln file and added to each and every project. (or better, made the default for all projects). I have a I:\boost_1_61_0_b1; as the include directory, and that is common to all … [View More]

5 5

Windows 10 and VC14, fixing C2117 error when using Asio.
by Andrew Maclean 21 May '16

21 May '16

If you find that when using Asio in Windows 10 with the Windows 10 SDK and Visual Studio 2015 you get lots of C2177 errors in winnt.h and sdkdkver.h then this should fix it: Essentially, just add: #define WINVER 0x0A00 #define _WIN32_WINNT 0x0A00 before any header that includes SDKDDKVer.h either directly or indirectly. If using CMake, then in the CMakeLists.txt file just add these lines: if(WIN32) add_definitions(-DWINVER=0x0A00) add_definitions(-D_WIN32_WINNT=0x0A00) endif() The fix … [View More]

1 0

[test] Standalone use with multiple translation units?
by Adam Nielsen 20 May '16

20 May '16

Hi all, I am currently using Boost Test for my test code, however it is always an extreme headache trying to get Boost available on the target platforms I'm using. At the moment due to some environment restrictions it is just not possible to use a recent version of Boost, and since the Test library broke backwards compatibility with 1.59, my code will no longer compile on versions earlier than 1.59. So I am looking to see whether I can avoid the need to compile the full Boost, and just pull … [View More]

2 2

[boost::compute] [OS X 10.11.5] [GeForce GT 750M] Segmentation fault
by Prashant 20 May '16

20 May '16

Hi, Example code to sort a vector on GPU (GeForce GT 750M) generates SEGV. However, it runs fine on Iris Pro (Intel(R) Core(TM) i7-4850HQ CPU). Having said that, it works as long as size of vector being sorted is small(<2 million). The code throws an exception if the size of the vector is less 9 million. Exception: boost/1_61_0/include/boost/compute/command_queue.hpp(453): Throw in function boost::compute::event boost::compute::command_queue::enqueue_write_buffer(const … [View More]boost::compute::buffer &, size_t, size_t, const void *, const boost::compute::wait_list &) Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector <boost::compute::opencl_error> > std::exception::what: Invalid Value Another observation: if the size of vector is 50 million the sorting works fine, though the timings are worse than Iris Pro. Regards, Prashant ----------------------------Cut here------------------------------------- #include <iostream> #include <vector> #include <algorithm> #include <boost/foreach.hpp> #include <boost/compute/core.hpp> #include <boost/compute/platform.hpp> #include <boost/compute/algorithm.hpp> #include <boost/compute/container/vector.hpp> #include <boost/compute/functional/math.hpp> #include <boost/compute/types/builtin.hpp> #include <boost/compute/function.hpp> #include <boost/chrono/include.hpp> #include <boost/exception/all.hpp> namespace compute = boost::compute; int main(int argc, char* argv[]) { if (argc != 2) { std::cout << "Usage: " << argv[0] << " <size> " << std::endl; return 0; } // generate random data on the host std::vector<float> host_vector(atoi(argv[1])); std::generate(host_vector.begin(), host_vector.end(), rand); std::cout << "===============CPU==================\n"; for (size_t k=0; k<5; k++) { std::vector<float> host_copy_vector(host_vector); auto start = std::chrono::high_resolution_clock::now(); std::sort(host_copy_vector.begin(), host_copy_vector.end()); auto duration = std::chrono::duration_cast<std::chrono::milliseconds> (std::chrono::high_resolution_clock::now() - start); std::cout << "time: iteration ("<< k << ") : " << duration.count() << " ms" << std::endl; } std::vector<compute::platform> platforms = compute::system::platforms(); for(size_t i = 0; i < platforms.size(); i++){ const compute::platform &platform = platforms[i]; std::cout << "Platform '" << platform.name() << "'" << std::endl; std::vector<compute::device> devices = platform.devices(); for(size_t j = 0; j < devices.size(); j++){ const compute::device &device = devices[j]; std::string type; if(device.type() & compute::device::gpu) type = "GPU Device"; else if(device.type() & compute::device::cpu) type = "CPU Device"; else if(device.type() & compute::device::accelerator) type = "Accelerator Device"; else type = "Unknown Device"; if (type != "GPU Device") { std::cout << "Ignoring non GPU devices.\n"; continue; } std::cout << "====\n"; std::cout << " " << type << ": " << device.name() << std::endl; std::cout << "====\n"; compute::context context(device); compute::command_queue queue(context, device); for (size_t k=0; k<5; k++) { compute::vector<float> device_vector(host_vector.size(), context); // copy data from the host to the device compute::copy( host_vector.begin(), host_vector.end(), device_vector.begin(), queue ); auto start = std::chrono::high_resolution_clock::now(); try { compute::sort(device_vector.begin(), device_vector.end(), queue); } catch (boost::exception & e) { std::cerr << diagnostic_information(e); break; } auto duration = std::chrono::duration_cast<std::chrono::milliseconds> (std::chrono::high_resolution_clock::now() - start); std::cout << "time: iteration ("<< k << ") : " << duration.count() << " ms" << std::endl; } std::cout << "====\n"; } } return 0; } [View Less]

2 2