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

boost.dll winapi compile error
by Elod G 17 Jan '16

17 Jan '16

Hello All, I cloned origin/master of https://github.com/boostorg/dll and copied include/ to the 1.60 release of boost to give boost.DLL a go. I am getting the following compile error when including: "boost/dll.hpp" boost\dll\detail\windows\shared_library_impl.hpp:140: error: C2039: 'get_proc_address' : is not a member of 'boost::detail::winapi' I am using VS2013. What am I missing? -- ElodG

1 0

multiprecision thread safety
by Daniel Brake 14 Jan '16

14 Jan '16

Hi Boost, I have a couple of questions regarding thread safety and Boost.Multiprecision. I am writing a library, and would like to be able to use mpfr_float (packed into my own complex class) in differing variable precisions on multiple threads simultaneously. 1. Is this supported? I looked in documentation, but didn't find comments to that end. 2. Must I manually call mpfr_free_cache when terminating threads, as recommended by the mpfr documentation? see http://www.mpfr.org/mpfr-current/mpfr.html, section 4.7 memory handling. If so, since Boost.Multiprecision claims to not change the default precision of mpfr_t, do I need to access the particular back end for the thread, and free its cache? Thanks, Daniel Brake danielthebrake(a)gmail.com

2 1

boost 1.55 asio tcp cpp03 chat_server example memory leaks
by Hung Ruo Han 14 Jan '16

14 Jan '16

Hi all i hope someone could give me a clue where to investigate... i'm running the chat_server example from boost http://www.boost.org/doc/libs/1_55_0/doc/html/boost_asio/example/cpp03/chat… on visual studio 2010, windows 10 and i downloaded boost binaries from : http://sourceforge.net/projects/boost/files/boost-binaries/1.55.0/boost_1_5… i used a script to simulate 30 tcp clients, each thread behavior basically: 1. connect to tcp server 2. start a loop 3. send a message to tcp server 4. receive a message from tcp server 5. sleep 6. back to step 2 the strange fact is when i use windows task manager to monitor the memory consumption. The numbers from columns *private working set* and *shared working set* remains "stable" for almost 18 minutes and after that the values of *private working set* starts to increase almost 5 MB by minute. So my doubts are: 1. Does anyone ever seen anything similar before? 2. What could cause this? Regards -- Hung Ruo Han <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> This email has been sent from a virus-free computer protected by Avast. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <#DDB4FAA8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

1 0

[phoenix] [clang] error assigning function object
by Nathan Ridge 12 Jan '16

12 Jan '16

Hi there, I'm experiencing a compiler error in code that tries to assign a Boost.Phoenix function object returned by invoking a phoenix::function with a std::string as one of the bound parameters. I've reduced my error to the following minimal code: #include <string> #include <boost/phoenix/core/argument.hpp> #include <boost/phoenix/function.hpp> struct S { void operator()(std::string, int) const; }; boost::phoenix::function<S> lazy; auto func1 = lazy(std::string(), boost::phoenix::placeholders::_1); auto func2 = func1; void foo() { func2 = func1; } My compiler version is clang 3.7; the error does not occur with gcc 5.1. The error also goes away if I change the type of the first argument from std::string to a different type (like int). The compiler error is shown below. Any ideas as to what is going on? Am I doing something wrong, or did I run into a bug in Phoenix? Thanks, Nate In file included from test.cpp:81: In file included from /home/nr/dev/dist/boost/include/boost/phoenix/core/argument.hpp:13: In file included from /home/nr/dev/dist/boost/include/boost/phoenix/core/actor.hpp:25: In file included from /home/nr/dev/dist/boost/include/boost/proto/make_expr.hpp:100: In file included from /home/nr/dev/dist/boost/include/boost/proto/detail/make_expr_.hpp:3: /home/nr/dev/dist/boost/include/boost/proto/detail/preprocessed/make_expr_.hpp:73:88: error: no type named 'type' in 'boost::proto::transform<boost::proto::switch_<boost::phoenix::phoenix_generator, boost::proto::tag_of<boost::proto::_> ()>, void>::result<boost::phoenix::phoenix_generator (boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>>, 2>)>' typedef typename proto_generator::template result<proto_generator(expr_type)>::type result_type; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~ /home/nr/dev/dist/boost/include/boost/proto/make_expr.hpp:180:34: note: in instantiation of template class 'boost::proto::detail::make_expr_<boost::proto::tagns_::tag::assign, boost::phoenix::phoenix_domain, boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>, void, void, void, void, void, void, void, void, void>' requested here typename detail::make_expr_< ^ /home/nr/dev/dist/boost/include/boost/phoenix/core/actor.hpp:225:36: note: in instantiation of template class 'boost::proto::result_of::make_expr<boost::proto::tagns_::tag::assign, boost::phoenix::phoenix_domain, boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>, void, void, void, void, void, void, void, void, void>' requested here typename proto::result_of::make_expr< ^ /home/nr/dev/dist/boost/include/boost/phoenix/core/actor.hpp:185:12: note: while substituting deduced template arguments into function template 'operator=' [with A0 = const boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>] struct actor ^ /home/nr/dev/dist/boost/include/boost/proto/matches.hpp:830:44: note: in instantiation of template class 'boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>>, 2>' requested here : Cases::template case_<typename Expr::proto_tag>::template impl<Expr, State, Data> ^ /home/nr/dev/dist/boost/include/boost/proto/transform/impl.hpp:238:13: note: in instantiation of template class 'boost::proto::switch_<boost::phoenix::phoenix_generator, boost::proto::tag_of<boost::proto::_> ()>::impl<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>>, 2>, int, boost::proto::envns_::empty_env>' requested here : PrimitiveTransform::template impl<Expr, empty_state, empty_env> ^ /home/nr/dev/dist/boost/include/boost/proto/transform/impl.hpp:255:9: note: in instantiation of template class 'boost::proto::detail::apply_transform<boost::phoenix::phoenix_generator (boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>>, 2>)>' requested here BOOST_PROTO_TRANSFORM_(PrimitiveTransform, X) ^ /home/nr/dev/dist/boost/include/boost/proto/transform/impl.hpp:194:48: note: expanded from macro 'BOOST_PROTO_TRANSFORM_' typedef typename boost::proto::detail::apply_transform<Sig>::result_type type; \ ^ /home/nr/dev/dist/boost/include/boost/proto/detail/preprocessed/make_expr_.hpp:73:43: note: in instantiation of template class 'boost::proto::transform<boost::proto::switch_<boost::phoenix::phoenix_generator, boost::proto::tag_of<boost::proto::_> ()>, void>::result<boost::phoenix::phoenix_generator (boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::assign, boost::proto::argsns_::list2<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>>, 2>)>' requested here typedef typename proto_generator::template result<proto_generator(expr_type)>::type result_type; ^ /home/nr/dev/dist/boost/include/boost/proto/make_expr.hpp:180:34: note: in instantiation of template class 'boost::proto::detail::make_expr_<boost::proto::tagns_::tag::assign, boost::phoenix::phoenix_domain, boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>, void, void, void, void, void, void, void, void, void>' requested here typename detail::make_expr_< ^ /home/nr/dev/dist/boost/include/boost/phoenix/core/actor.hpp:213:36: note: in instantiation of template class 'boost::proto::result_of::make_expr<boost::proto::tagns_::tag::assign, boost::phoenix::phoenix_domain, boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>, void, void, void, void, void, void, void, void, void>' requested here typename proto::result_of::make_expr< ^ test.cpp:96:8: note: while substituting deduced template arguments into function template 'operator=' [with A0 = boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::phoenix::detail::tag::function_eval, boost::proto::argsns_::list3<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<S>, 0>, boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<std::basic_string<char>>, 0>, boost::phoenix::actor<boost::proto::exprns_::basic_expr<boost::proto::tagns_::tag::terminal, boost::proto::argsns_::term<boost::phoenix::argument<1>>, 0>>>, 3>>] func2 = func1; ^ 1 error generated.

2 3

[Statechart] Implementing an internal timeout in an asynchronous state machine
by John Buonassisi 07 Jan '16

07 Jan '16

Hi there, I am looking for some advice on the best way to implement an internal timeout in an asynchronous state machine using the Boost Statechart library. My project requires an asynchronous state machine that multiple threads can queue events to. The asynchronous state machine will react to events and execute callback functions that are registered on creation of the state machine. So far, this hasn't been a problem, but I have hit a bit of a roadblock when handling timeouts. I need my asynchronous state machine class to start a timer in a certain reaction method, when this timer expires I need the scheduler to queue a timeout event. Basically, the timer will act as an interrupt, when it expires I need a timeout event to be immediately queued to the state machine event queue. Since asynchronous state machines are created and managed by a scheduler class (in my case boost::statechart::fifo_scheduler<>) how can I get the asynchronous state machine to queue a timeout event? If possible, I would like to encapsulate this timeout functionality, so client code that uses my derived asynchronous state machine does not have to deal with managing timeouts. My first thought is to have the asynchronous state machine class create a thread when the timer is started. The thread will continually check if the timer has expired and if it has, will queue a timeout event. The issue with this approach is that I would need to pass the scheduler and state machine handler to the thread function in order to queue the event. Obviously, the state machine does not have access to these objects and I am unsure if this is a safe approach. Any suggestions or help with this matter would be greatly appreciated! This is my first post to the mailing list so I hope this is the right arena for my question. Thanks, John Buonassisi

1 0

*newbie* 'BOOST_INTRUSIVE_HAS_MEMBER_FUNCTION_CALLABLE_WITH_ITERATION' : undeclared identifier
by Gregory Werner 07 Jan '16

07 Jan '16

Hi all new to the list. When trying to build a rather large project which uses boost, I get the following few lines 12 times during the build process: 7>c:\local\boost_1_60_0\boost\intrusive\detail\has_member_function_callable_with.hpp(303): error C2065: 'BOOST_INTRUSIVE_HAS_MEMBER_FUNCTION_CALLABLE_WITH_ITERATION' : undeclared identifier 7>c:\local\boost_1_60_0\boost\intrusive\detail\has_member_function_callable_with.hpp(320): error C4430: missing type specifier - int assumed. Note: C++ does not support default-int 7>c:\local\boost_1_60_0\boost\intrusive\detail\has_member_function_callable_with.hpp(320): error C2143: syntax error : missing ';' before ''template<'' Others can build this same project just fine and I can't find anything on the internet which would indicate others having problems with this file. I am using VS2010 Professional Version with SP1. My compiler and boost libraries are both 32 bit. I tried uninstalling and reinstalling everything but same errors. These are the only errors which prevent my project from successful build. Any ideas as to what could cause this? -Greg

2 1

Feedback boost conan binary packages
by Luis 07 Jan '16

07 Jan '16

Dear Boost Users, Disclaimer: I am founder and developer of conan.io C++ package manager. Please note that it is just a FOSS project, MIT license, fully decentralized, and although I'd like to promote the tool and receive feedback about it, there are already channels for that conversation in the github repos. What I'd really like is to get feedback about the Boost packages I am creating and maintaining in conan. I have generated almost 190 different binary packages for Boost versions 1.57-1.60 ( https://www.conan.io/search?q=Boost%20AND%20user:lasote) for Linux, Win, Mac and different flavours of compilers (gcc 4.7-5.3, VS12-14) and settings (Debug, Release). You can read a quick getting started on such Boost packages in: http://docs.conan.io/en/latest/examples/boost.html If someone has been able to try it, I'd like to know several things: - whether it is interesting to have pre-compiled packages or you always prefer to build from source (i.e. always using the --build option in conan). So far there are about 200 downloads of binary packages, but probably many people prefer to build from source. - It has dependencies to already existing zlib and bzip2 conan packages (can be shared or static). Are you fine with these? Any other Boost dependencies missing that you would like to automate? - It is probably the largest package so far, have you experienced slow downloads? You can report issues and feedback in the conan-boost repo: https://github.com/lasote/conan-boost/issues. Thanks very much, Luis

2 2

boost variant is not a literal type
by Robert Ramey 07 Jan '16

07 Jan '16

I want to use Boost.Variant constexpr function. In order to do this it has to be a literal type - which apparently it isn't. The rule for being a literal type are summarized here: http://en.cppreference.com/w/cpp/concept/LiteralType a boost::variant isn't default constructable so it fails to qualify. Has anyone else had this problem before and managed to solve it in a convenient way? Robert Ramey

3 7

Re: [Boost-users] boost program options
by avib369 . 06 Jan '16

06 Jan '16

With reference to boost 1.59 and program options. The following test passes on boost 1.53, but fails on boost 1.59. I need to able to handle. --arg1 10 and --arg1=10 boost 1.59 now fails on '--arg1 10', with test below with option value being empty. #include <string> #include <iostream> #include <fstream> #include <boost/test/unit_test.hpp> #include <boost/foreach.hpp> #include <boost/program_options.hpp> using namespace std; namespace po = boost::program_options; BOOST_AUTO_TEST_SUITE( BaseTestSuite ) BOOST_AUTO_TEST_CASE( test_program_options_implicit_value ) { cout << "Base:: ...test_program_options_implicit_value\n"; // Declare the supported options. po::options_description desc("Allowed options"); desc.add_options() ("help", "produce help message") ("arg1", po::value<string>()->implicit_value( string("") ), "optional arg1 description") ; { char* argv[] = { const_cast<char*>("test_program_options_implicit_value"), const_cast<char*>("--help"), const_cast<char*>("--arg1") }; po::variables_map vm; po::store(po::parse_command_line(3, argv, desc), vm); po::notify(vm); BOOST_CHECK_MESSAGE(vm.count("help"), "Expected help"); BOOST_CHECK_MESSAGE(vm.count("arg1"), "Expected arg1"); BOOST_CHECK_MESSAGE(vm["arg1"].as<string>() == "", "Expected arg1 to be empty"); } { // ****** This fails on boost 1.59 bit passes in boost 1.53 ******* char* argv[] = { const_cast<char*>("test_program_options_implicit_value"), const_cast<char*>("--arg1"), const_cast<char*>("10") }; po::variables_map vm; po::store(po::command_line_parser(3, argv, desc), vm); po::notify(vm); BOOST_CHECK_MESSAGE(vm.count("arg1"), "Expected arg1"); BOOST_CHECK_MESSAGE(vm["arg1"].as<string>() == "10", "Expected arg1 with value of 10 but found '" << vm["arg1"].as<string>() << "'"); } { char* argv[] = { const_cast<char*>("test_program_options_implicit_value"), const_cast<char*>("--arg1=11") }; po::variables_map vm; po::store(po::parse_command_line(2, argv, desc), vm); po::notify(vm); BOOST_CHECK_MESSAGE(vm.count("arg1"), "Expected arg1"); BOOST_CHECK_MESSAGE(vm["arg1"].as<string>() == "11", "Expected arg1 with value of 11 but found " << vm["arg1"].as<string>()); } } Ta, Avi

2 1

boost program_options
by avib369 . 06 Jan '16

06 Jan '16

There seems to be change/regression in boost program options. In boost/1.53. I used boost::program_options::variables_map vm; po::store( po::parse_command_line( argc, argv, desc_ , po::command_line_style::unix_style ^ po::command_line_style::allow_short), vm ); po::notify( vm ); This could handle arguments like: ./exe --help all ./exe --help summary However from boost 1.59, this no longer works, instead I have to use: ./exe --help=all ./exe --help=summary Is this a known change ? how do i get back to the old functionality ? Ta, Avi

2 1

Boost 1.60.0 breaks Boost.Log formatter on MSVC11
by Robert Rumpf 06 Jan '16

06 Jan '16

I’ve been happily using Boost.Log (and much of the rest of Boost) for years, but on upgrading to 1.60, I find that I get runtime errors on MSVC 11. I’ve tracked the problem back to a simple representative example (as provided with the Boost.Log library): http://www.boost.org/doc/libs/1_60_0/libs/log/example/doc/tutorial_fmt_stre… The problematic portion of the example is the usage of character arrays when setting up the formatter, specifically: << ": <" << "> " The code compiles fine but then throws an exception at runtime, seemingly due to uninitialized data. Removing the strings in the formatter configuration makes the error disappear. I would guess that it has something to do with xvalues going into the formatter unintentionally, but this code has functioned fine on prior versions of Boost 1.59-1.54, and I can find nothing in the release notes that points me at where the problem might be. I am compiling with BOOST_SPIRIT_USE_PHOENIX_V3. Before I start doing lots of diffs, has anyone else experienced this problem, and is there any known solution or workaround? Thanks for all of the excellent work and support, Rob

1 0

[regex] link errors on 1.60 update
by James Walker 06 Jan '16

06 Jan '16

When I tried to convert my project from Boost 1.58.0 to 1.60.0, I got some link errors. This is using Xcode 4.6.3 on Mac OS X 10.7.5. I'm compiling all the sources in libs/regex/src. Help? Undefined symbols for architecture i386: "boost::re_detail_106000::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::construct_init(boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags)", referenced from: boost::re_detail_106000::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, char const*) in BVHJointMap.o boost::re_detail_106000::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::perl_matcher(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags, char const*) in AnimationsManager.o "boost::re_detail_106000::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::find()", referenced from: bool boost::regex_search<char const*, char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >(char const*, char const*, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags) in BVHJointMap.o "boost::re_detail_106000::perl_matcher<char const*, std::allocator<boost::sub_match<char const*> >, boost::regex_traits<char, boost::cpp_regex_traits<char> > >::match()", referenced from: bool boost::regex_match<char const*, std::allocator<boost::sub_match<char const*> >, char, boost::regex_traits<char, boost::cpp_regex_traits<char> > >(char const*, char const*, boost::match_results<char const*, std::allocator<boost::sub_match<char const*> > >&, boost::basic_regex<char, boost::regex_traits<char, boost::cpp_regex_traits<char> > > const&, boost::regex_constants::_match_flags) in AnimationsManager.o

3 4

Boost 1.60.0 rc1 is now available
by Marshall Clow 05 Jan '16

05 Jan '16

Release candidate files for 1.60.0 are available at: http://boost.cowic.de/rc/ 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. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: MD5 (boost_1_60_0_rc1.7z) = 7ce7f5a4e396484da8da6b60d4ed7661 MD5 (boost_1_60_0_rc1.tar.bz2) = 65a840e1a0b13a558ff19eeb2c4f0cbe MD5 (boost_1_60_0_rc1.tar.gz) = 28f58b9a33469388302110562bdf6188 MD5 (boost_1_60_0_rc1.zip) = 0cc5b9cf9ccdf26945b225c7338b4288 Thanks! -- The release managers P.S. Release notes are here: http://www.boost.org/users/history/version_1_60_0.html

4 8

C++Now 2106 Call for Submission
by Jon Kalb 05 Jan '16

05 Jan '16

Boost Users, The Call for Submissions for C++Now 2016 (AKA BoostCon) has been released: http://cppnow.org/2016-conference/announcements/2015/11/17/call-for-submissi on.html The deadline for submitting is very near and cannot be extended, so don¹t delay your submission. The conference will be held in Aspen the week of May 9th. See you in Aspen! Jon

1 0

[boost][review][qvm] QVM formal review result
by Adam Wulkiewicz 04 Jan '16

04 Jan '16

Dear Boost community, The review period for Emil Dotchevski's QVM library has concluded. I'd like to thank everyone who participated in the discussions, esspecially those who sent formal reviews. Only four votes were casted however more people commented on issues on the mailing list. Comments received during the course of the review were generally positive, with a number of technical issues identified that need to be addressed. The review identified no fundamental problems in the design or implementation of the library that would entail rejection. The final version of the library can be fully accepted once Emil has addressed the issues identified during the review. Therefore I'm happy to say: Emil Dotchevski's Boost.QVM library is CONDITIONALLY ACCEPTED. Full report can be found here: http://lists.boost.org/Archives/boost/2016/01/227027.php Regards, Adam

2 1

[Boost::Python]
by Eugenio Bargiacchi 03 Jan '16

03 Jan '16

Hello everyone, I have a member function with signature const Matrix2D & foo const (); Which returns an internal data structure. Matrix2D is using Matrix2D = Eigen::Matrix<double, Eigen::Dynamic, Eigen::Dynamic, Eigen::RowMajor | Eigen::AutoAlign>; I have explicitly set a to_python converter for Matrix2D, and I have exported the function with a call policy of return_internal_reference. However, when this function is called from Python I get TypeError: No Python class registered for C++ class Eigen::Matrix<double, -1, -1, 1, -1, -1> This happens also if the reference is not const. At the same time, if I modify the call policy to return_value_policy<copy_const_reference>() Python can decode the matrix just fine. The same holds true if I return the Matrix2D by value. However I really need to have a reference to the matrix in order store it into other classes. How can I make Python see the data structure through the reference? The converter in case it is needed: boost::python::list toPythonList(const double * data, size_t num) { boost::python::list list; for (size_t i = 0; i < num; ++i) list.append(data[i]); return list;} struct Matrix2DToPython{ static PyObject* convert(Matrix2D const & m) { boost::python::list list; for (int i = 0; i < m.rows(); ++i) { list.append(toPythonList(m.row(i).data(), m.cols())); } return boost::python::incref(list.ptr()); }}; Thanks, Eugenio

1 0

[units] Adding two absolute units
by Itzik 03 Jan '16

03 Jan '16

Hello, <obligatory appreciation on first post> I started using Boost just for boost::units and I find new ways boost can help me almost every day. So thanks for the great stuff! </obligatory appreciation on first post> My question to the board is why two absolute quantities (si::temperature (K) in my case) can't be summed in boost::units? I realized that this is a rule enforced by-design (gmane.comp.lib.boost.user/71747), and I understand that it is probably not a very common case, but I wanted my code to solve a simple formula which requires adding up two absolute temperatures (quantity<absolute<temperature>>). Each temperature represents an Inlet temperature in a Heat Exchange system. So even if converting one temperature to a relative type (quantity<temperature>) might be a workaround, it seems like a forced misuse to me. Eventually it turned out that I was mistaken with the formula, and subtraction was required instead, so there's no problem there. Alas, there's also a much simpler use case: What if I want to average the temperature of the last N readouts? Shouldn't boost::units support this simple operation? I have no formal physics education, but intuitively, adding two absolute temperatures doesn't seem really like a mistake to me, even if it's an odd thing to do. Will appreciate your thoughts on the matter.

3 4

Modifying all matching elements in a Boost.MultiIndex Container
by Amit Prakash Ambasta 01 Jan '16

01 Jan '16

Hi, I am trying to modify members of all elements matching value for a given index in a boost.multiindex container index.modify( index.find(value), [](T& element) { ... } ) seems to update a singular element(first match) On the other hand, std::pair<index::iterator, index::iterator> iter = index.equal_range(value); while(iter.first != iter.second) { index.modify( iter.first, [](T& element) { ... } ); iter.first++; } leads to segfaults and unexpected behavior. What would be right way to approach this?

3 4

Pointer to objects in Boost.MultiIndex
by Amit Prakash Ambasta 01 Jan '16

01 Jan '16

Consider the following code snippet: #include <iostream> #include <boost/multi_index_container.hpp> #include <boost/multi_index/ordered_index.hpp> #include <boost/multi_index/member.hpp> using namespace std; using namespace boost::multi_index; struct LinkList; struct LinkList { size_t index; LinkList* parent; LinkList(size_t index, LinkList* parent) : index(index), parent(parent) {} }; struct llindex {}; typedef ordered_unique<tag<llindex>, member<LinkList, size_t, &LinkList::index> > LinkListIndex; typedef boost::multi_index_container<LinkList, indexed_by<LinkListIndex> > IndexedLinkList; template <typename T> void show(T& iterable) { for(auto const& element: iterable) { if(element.parent != nullptr) { std::cout << "Index<" << element.index << ">: " << element.parent->index << std::endl; } else { std::cout << "Index<" << element.index << ">: " << "NULL" << std::endl; } } } int main() { IndexedLinkList ill; auto &index_ll = ill.get<0>(); ill.insert(LinkList{0, nullptr}); ill.insert(LinkList{1, (LinkList*)(&(*index_ll.find(0)))}); ill.insert(LinkList{2, (LinkList*)(&(*index_ll.find(0)))}); ill.insert(LinkList{3, (LinkList*)(&(*index_ll.find(2)))}); show(ill); return 0; } Would (LinkList*)(&(*index__ll.find(value))) be the recommended way to fetch the pointer to parent?

2 3

[BGL] Are normal and reverse undirected edges the same or different?
by Ireneusz Szcześniak 01 Jan '16

01 Jan '16

Hi, In an undirected graph, we create an undirected edge: add_edge(a, b, g); We get the reverse of that edge: edge(b, a, g); Now, are these two edges the same or different? vIf I compare them with the == operator, they are equal, but they have different source and target vertexes. Can I count on this behavior? Will it stick? I'm asking because I couldn't find it in the documentation. Please find attached my unit test. On Debian Jessie, I'm compiling it with: g++ test.cc -l boost_test_exec_monitor -l boost_unit_test_framework -o test Thanks & best, Irek

1 0