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

building on OS X with custom gcc version
by Damien Hocking 12 Jul '18

12 Jul '18

All, I’m trying to get 1.65.1 compiled on OSX 10.13.5. I have gcc 8.1 installed and I’ve added it to user-config.jam in the home directory. When I run "bootstrap.sh —with-toolset=gcc" it uses the Darwin gcc toolset, if I try —with-toolset=gcc-8.1 I get an unknown toolset error. If I use the Darwin-based gcc version of b2 and try and build with gcc 8.1 I get this series of errors: error: No best alternative for libs/context/build/asm_sources. and also linker errors from an unknown option -h on ld. I’m assuming this is because b2 built with Darwin gcc doesn’t have the right options for gcc 8. Is there a way to force b2 to be built based on gcc 8 so it gets the assembly and linker options right? Damien

4 9

[release] Boost 1.68.0 Beta 1
by Marshall Clow 10 Jul '18

10 Jul '18

Boost release 1.67.0 beta 1 is now available at: https://dl.bintray.com/boostorg/beta/1.68.0.beta1/source/ The files are identical to the RC2 that was posted on Friday. The SHA256 checksums are as follows: 961d2bdc74c1499c931b32098842abba8883b1a89ef5c8f8f0ab0aff771a3ce5 boost_1_68_0_b1_rc2.7z 0364846258648e39908ca7cebfc2d2216eef6980c32aaf8276d2cfe73ef012e3 boost_1_68_0_b1_rc2.tar.bz2 d99105685a68907a76b0479ecde77915423246236ef0db9cb846c5bfc09b41f3 boost_1_68_0_b1_rc2.tar.gz 6158e0e961bfb0d8adeb2ea70337b08504668258025f0a873fb21eee3436d22e boost_1_68_0_b1_rc2.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_68_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

Boost::MSM do_actions while in state
by IgnacioVizzo 10 Jul '18

10 Jul '18

Is there any way to do this? Using boost::msm? I know for fact that you can implement transition actions using the library, I've searched a lot around the internet and I didn't find my answer. So basically let's say I want to do this: <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_1.png> boost_msm_1.png <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_1.png> diagram1.cpp <http://boost.2283326.n4.nabble.com/file/t371323/diagram1.cpp> #include <boost/msm/back/state_machine.hpp> #include <boost/msm/front/euml/euml.hpp> #include <iostream> using namespace boost::msm::front::euml; namespace msm = boost::msm; namespace fsm { BOOST_MSM_EUML_EVENT(trigger); BOOST_MSM_EUML_ACTION(transition_action) { template <class FSM, class EVT, class SourceState, class TargetState> void operator()(EVT const &, FSM &fsm, SourceState &, TargetState &) { std::cout << "-v- transition_action -v-" << std::endl; return; } }; BOOST_MSM_EUML_ACTION(guard) { template <class FSM,class EVT,class SourceState,class TargetState> bool operator()(EVT const& evt,FSM&,SourceState& ,TargetState&) { std::cout << "[guard]" << std::endl; return true; } }; BOOST_MSM_EUML_ACTION(entry_action) { template <class Event, class FSM, class STATE> void operator()(Event const &, FSM &, STATE &) { std::cout << "==>entry_action" << std::endl; return; } }; BOOST_MSM_EUML_ACTION(exit_action) { template <class Event, class FSM, class STATE> void operator()(Event const &, FSM &, STATE &) { std::cout << "<==exit_action" << std::endl; return; } }; BOOST_MSM_EUML_STATE((entry_action,exit_action), State1); // BOOST_MSM_EUML_STATE((entry_action,exit_action), State2); // define the transition table BOOST_MSM_EUML_TRANSITION_TABLE(( State1 == State1 + trigger[guard] / transition_action // State1 == State2 + trigger[guard] / transition_action ), transition_table) // BOOST_MSM_EUML_DECLARE_STATE_MACHINE((transition_table, State1), fsm) // create a state machine "on the fly" BOOST_MSM_EUML_DECLARE_STATE_MACHINE((transition_table, init_ << State1, no_action, no_action, attributes_ << no_attributes_, configure_ << no_configure_, no_action ), my_fsm) typedef msm::back::state_machine<my_fsm> fsm_t; } //namespace fsm int main(int argc, char const *argv[]) { fsm::fsm_t example_fsm; example_fsm.start(); example_fsm.process_event(fsm::trigger); example_fsm.process_event(fsm::trigger); return 0; } // OUTPUT // ==>entry_action // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action But I want the machine to DO an action ONCE the Entry_action has completed and BEFORE the states exits. This is sort of a token or mark, like it's used in petri nets and GRAFCETS, basically. I want to add this boost_msm_2.png <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_2.png> <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_2.png> And the output for should be something like / OUTPUT // ==>entry_action // -DO ACTION- // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action // -DO ACTION- // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action Thanks! -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

2 1

[python][container] map_indexing_suite for flat_map
by MM 09 Jul '18

09 Jul '18

Hello, I've tried to adapt using myfm = boost::container::flat_map<const T*, V>; with boost::python::map_indexing_suite class_< myfm, myfm* >("myfm") .def( map_indexing_suite<myfm>{} ) ; I get a compile errors: /usr/include/boost/python/detail/invoke.hpp:75:14: error: no match for call > to ‘(const > boost::python::detail::specify_a_return_value_policy_to_wrap_functions_returning<const > T*>) (const T*)’ > ... > Caller = boost::python::detail::caller<const T* (*)(std::pair<const T*, > V>&), default_call_policies ...> I would suspect that there is some function that returns the key_type of the flat_map and takes a single argument of the value_type, but I can't find any. If there's one, I would need pick a return value policy for it. MM

1 0

Boost.Beast includes CRLF in HTTP fields
by David Demelier 08 Jul '18

08 Jul '18

Hello, It looks like HTTP response headers are saved with trailing CRLF in the message upon receiption after (async_)read. Since it usually does not add additional valuable information, would it be possible to remove them in next version of Boost.Beast? It will be more convenient as you don't need to trim them when you want to capture the field value. Regards, -- David

4 11

[release] Boost 1.68.0 Beta 1 Release Candidate 1
by Marshall Clow 07 Jul '18

07 Jul '18

The release candidates for the first 1.68.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.68.0.beta.1.rc1/source/> The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ] The SHA256 checksums are as follows: 4b39978aa227f56cc00715d48032e18f4bb259de756637a653b5acead4417e0b boost_1_68_0_b1_rc1.7z 39f6fdc16fc62041ca1401c5e8d1cd0220de24fd5d909eca3f0bf1049d1fd6f9 boost_1_68_0_b1_rc1.tar.bz2 9714d11a205e6f3a1cf1ed17b0caad8a64bc4a5459dfc6e1629e14e5e4b44dc7 boost_1_68_0_b1_rc1.tar.gz fe35f20eb5c2ebf5d4e4f15d0416e484058a732ca1a1e59b831b79d4d7702bdd boost_1_68_0_b1_rc1.zip 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. -- The Boost Release Managers

6 16

[release] Boost 1.68.0 Beta 1 Release Candidate 2
by Marshall Clow 07 Jul '18

07 Jul '18

The release candidates for the second 1.68.0 beta release are now available at: <https://dl.bintray.com/boostorg/beta/1.68.0.beta1.rc2/source/> The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ] == Changes since RC1: * version.hpp now has the correct version number in it. * Boost.Wave now builds on FreeBSD * Boost.ProgramOptions should now pass tests on msvc-10.0. The SHA256 checksums are as follows: 961d2bdc74c1499c931b32098842abba8883b1a89ef5c8f8f0ab0aff771a3ce5 boost_1_68_0_b1_rc2.7z 0364846258648e39908ca7cebfc2d2216eef6980c32aaf8276d2cfe73ef012e3 boost_1_68_0_b1_rc2.tar.bz2 d99105685a68907a76b0479ecde77915423246236ef0db9cb846c5bfc09b41f3 boost_1_68_0_b1_rc2.tar.gz 6158e0e961bfb0d8adeb2ea70337b08504668258025f0a873fb21eee3436d22e boost_1_68_0_b1_rc2.zip 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. -- The Boost Release Managers

1 3

Re: [Boost-users] [boost] [release] 1.68.0 closed for Beta
by Marshall Clow 06 Jul '18

06 Jul '18

On Thu, Jul 5, 2018 at 1:52 PM, Edward Diener via Boost < boost(a)lists.boost.org> wrote: > On 7/5/2018 10:32 AM, Marshall Clow via Boost wrote: > >> The master branch is now closed for all changes except by permission >> for the Beta release. >> >> Also, remember to add your libraries' changes to the release notes at: >> >> < >> https://github.com/boostorg/website/blob/master/feed/history >> /boost_1_68_0.qbk >> >>> >>> >> Thanks, >> >> -- The Boost Release Team >> > > I would like to merge iostream's 'develop' changes to 'master'. The > changes have been heavily tested and there has been a request for at least > one of the changes to make it into the upcoming Boost release. > > Edward -- What are the changes, and how important is it that they appear in the Beta release? There will be time to merge post-beta before the final 1.68.0 release. -- Marshall

1 0

[release] 1.68.0 closed for Beta
by Marshall Clow 05 Jul '18

05 Jul '18

The master branch is now closed for all changes except by permission for the Beta release. Also, remember to add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_68_0.q… > Thanks, -- The Boost Release Team

1 0