July 2020 - Boost-users - lists.stage.boost.cppalliance.org

Clarification on statechart post_event vs process_event within react()
by John McCabe 10 Jan '22

10 Jan '22

Hi, Apologies if this has already been answered/clarified, but my search of the internet to try to get a definitive answer, at least one I recognised as being definitive, was unsuccessful. Below I have posted some source code, based on the stopwatch example from the tutorial, but using an 'external' object to delegate the actual handling of event stuff to and using the state, rather than simple_state base class, and some other tweaks. This is a cut down version of something that someone I work with has devised, but I just wanted to get a clear answer on whether process_event() should be getting called in cases like this. I think it probably should not since, in the code below, you change state (with a state object's destructor being executed) whilst you're executing that state's react(EvStartStop) function. If someone can confirm this is the correct interpretation that would be very much appreciated. Any questions, feel free to ask (BTW - I'm compiling for C++17) John PS - In case it's of any use, the output from running this code is: ------ Entered Active Entered Stopped Stopped - payload2 m_charValue: a Exited ~Stopped <<<--- This is the bit I don't like the look of because... Entered Running Active - payload2 m_charValue: a <<<--- ... this happens from the forward_event() call payload1 value1: 20 payload1 value2: 200.2 Exited ~Running Entered Stopped Exiting Program Exited ~Stopped Exited ~Active ------ If I swap the //*** comments to the doProcess() lines instead of doPost(), the output seems more sensible ------ Entered Active Entered Stopped Stopped - payload2 m_charValue: a Exited ~Stopped Entered Running Active - payload2 m_charValue: a payload1 value1: 20 payload1 value2: 200.2 Exited ~Running Entered Stopped Exiting Program Exited ~Stopped Exited ~Active ------ ========== code =========== #include <boost/statechart/event.hpp> #include <boost/statechart/state_machine.hpp> #include <boost/statechart/state.hpp> #include <boost/statechart/transition.hpp> #include <boost/statechart/custom_reaction.hpp> #include <boost/mpl/list.hpp> #include <iostream> #include <string> namespace sc = boost::statechart; namespace mpl = boost::mpl; // Forward declare a handler 'class' that's going to have activity delegated to it struct Handler; // Normal example start/stop and reset events struct EvStartStop : sc::event<EvStartStop> {}; struct EvReset : sc::event<EvReset> {}; // A couple of events that carry data with them struct EvPayload1 : sc::event<EvPayload1> { EvPayload1(int value1, double value2) : m_value1 { value1 }, m_value2 { value2 } {}; int m_value1 { 0 }; double m_value2 { 0.0 }; }; struct EvPayload2 : sc::event<EvPayload2> { EvPayload2(const char& charValue) : m_charValue { charValue } {}; char m_charValue { false }; }; // Back to the example bits struct Active; struct StopWatch : sc::state_machine<StopWatch, Active> { typedef sc::transition<EvReset, Active> reactions; // The extra 'handler' stuff void setHandler(Handler* handler) { m_handler = handler; }; Handler* getHandler() const { return m_handler; }; Handler* m_handler { nullptr }; // Used to make post_event() accessible from an external class...seems unpleasant, but... using sc::state_machine<StopWatch, Active>::post_event; }; // The implementation of the Handler class; created with a reference to a StopWatch object struct Handler { Handler(StopWatch& stopWatch) : m_stopWatch { stopWatch } {}; void doPost() { m_stopWatch.post_event(EvStartStop()); } void doProcess() { m_stopWatch.process_event(EvStartStop()); } StopWatch& m_stopWatch; }; struct Stopped; struct Active : sc::state<Active, StopWatch, Stopped> { Active(my_context ctx) : my_base { ctx } { std::cout << "Entered Active" << std::endl; }; ~Active() { std::cout << "Exited ~Active" << std::endl; }; typedef mpl::list<sc::custom_reaction<EvPayload1>, sc::custom_reaction<EvPayload2>, sc::transition<EvReset, Active>> reactions; sc::result react(const EvPayload1& payload1) { std::cout << "payload1 Event NOT HANDLED" << std::endl; return discard_event(); } sc::result react(const EvPayload2& payload2) { std::cout << "Active - payload2 m_charValue: " << payload2.m_charValue << std::endl; return discard_event(); } }; struct Running : sc::state<Running, Active> { Running(my_context ctx) : my_base { ctx } { std::cout << "Entered Running" << std::endl; }; ~Running() { std::cout << "Exited ~Running" << std::endl; }; typedef mpl::list<sc::custom_reaction<EvPayload1>, sc::transition<EvStartStop, Stopped>> reactions; sc::result react(const EvPayload1& payload1) { std::cout << "payload1 value1: " << payload1.m_value1 << std::endl; std::cout << "payload1 value2: " << payload1.m_value2 << std::endl; //***context<StopWatch>().getHandler()->doPost(); context<StopWatch>().getHandler()->doProcess(); return discard_event(); } }; struct Stopped : sc::state<Stopped, Active> { Stopped(my_context ctx) : my_base { ctx } { std::cout << "Entered Stopped" << std::endl; }; ~Stopped() { std::cout << "Exited ~Stopped" << std::endl; }; typedef mpl::list<sc::custom_reaction<EvPayload2>, sc::transition<EvStartStop, Running>> reactions; sc::result react(const EvPayload2& payload2) { std::cout << "Stopped - payload2 m_charValue: " << payload2.m_charValue << std::endl; //***context<StopWatch>().getHandler()->doPost(); context<StopWatch>().getHandler()->doProcess(); return forward_event(); } }; int main() { StopWatch myWatch; Handler myHandler(myWatch); myWatch.setHandler(&myHandler); myWatch.initiate(); myWatch.process_event(EvPayload2 { 'a' }); myWatch.process_event(EvPayload1 { 20, 200.2 }); std::cout << "Exiting Program" << std::endl; return 0; }

1 0

Boost.Numeric.Interval: Please specify rounding control mechanism
by Bastien Commelongue 01 Dec '20

01 Dec '20

Hello, I am building an app for IOS (ARM) and I had this issue while compiling: *Boost.Numeric.Interval: Please specify rounding control mechanism.* C99 version should be used in this case but __USE_ISOC99 is not defined. Modifying the condition with this code (using __cplusplus) fixed the issue: *boost/numeric/interval/hw_rounding.hpp(36)* *#if defined(BOOST_NUMERIC_INTERVAL_NO_HARDWARE) && (defined(__USE_ISOC99) || defined(__MSL__) || (defined __cplusplus && __cplusplus >= 201103L))# include <boost/numeric/interval/detail/c99_rounding_control.hpp>#endif* Let me know if I missed something or if you plan to integrate this modification in a next version. Cheers, Bastien Commelongue

2 1

Boost-1.71.0 upgrade issue
by Tej Kumar 28 Jul '20

28 Jul '20

Hi Team, Hope you guys are doing well. I am trying to upgrade Boost to 1.71.0 version. My code is compiling and building successfully but during test run i see below error. Error seems to be related with boost chrono, even though i have included boost_chrono lib in my makefile. *undefined symbol: _ZN5boost6chrono12steady_clock3nowEv* It will be a great help if you guys can suggest something here. Thanks & Regards, Tej

3 4

[Graph] Unable to get the edge_color in depth_first_search
by Ashish Kumar 27 Jul '20

27 Jul '20

Hello, First of all, I am new to Boost Graph Library. So, there might be a simpler or easier fix to the problem I am facing. I am trying to get the edge color after executing the boost::depth_first_search algorithm on the graph. For that, I created an edge color map and passed it to the function. Also, to log the colors of the edges, I made a visitor class, passed the color of the edge to it, and printed it to the standard output stream, for the tree_edge, back_edge, etc. But, for every edge, the value of color comes out to be 0. So, I am not able to get the color of every edge. A small snippet of how I am calling the depth_first_search function: depth_first_search(graph, visitor(dfs_visitor(root, visited_order, colors, graph)) .edge_color_map(&colors) .root_vertex(root)); The complete code along with the visitor class can be found here: https://gist.github.com/krashish8/5f8d8e613e189857bd2b0fd46dd02b29 Please suggest any possible solution to this problem. Thank you, Ashish Kumar.

1 0

[boost] Clang on Windows - No Autolink?
by Klaim - Joël Lamotte 27 Jul '20

27 Jul '20

Hi, am I correct that autolinking is not supported by Boost when using Clang on Windows? To be clear, I'm talking about both clang++ and clang-cl drivers. The behavior I observe suggests that I am correct but looking at the autolink.hpp header I didn't understand how it decides if it should work or not. A. Joël Lamotte

1 0

Two Graphs Common Spanning Trees Issue [GSoC]
by Prakash Tiwari 24 Jul '20

24 Jul '20

Hello, Community Members and developers, I'm student of Google Summer Of Code and contributing to the pgRouting <https://github.com/pgRouting/pgrouting/>[1]. I need to use boost algorithm boost::two_graphs_common_spanning_trees. I have gone through the documentation and try to use it (with help of example.cpp) But I found that this algorithm is not returning the expected results. I have mentioned the example that I have used and explained the expected and given results <https://github.com/prakashupes/ProposalCodes/issues/1>.[2] So, please try to figure out that is it a bug implemented algorithm or It might be possible that I'm using the algorithm in the wrong way. Thanks Prakash Tiwari [1].https://github.com/pgRouting/pgrouting/ [2]. https://github.com/prakashupes/ProposalCodes/issues/1

2 1

jpeg resize - file size increases
by Lloyd 24 Jul '20

24 Jul '20

Hi, We tried boost gil resize example to experiment with scaling down a jpeg image file. For some images, this causes the size of the file to increase. We are using bilinear_sampler algorithm. Our aim to reduce the input image size so as to save storage/network bandwidth. Quality can be compromised to a certain extent. Which algorithm/method should we use? The code fragment is given below:- boost::gil::rgb8_image_t img; boost::gil::read_and_convert_image(InStream, img, T()); float width = (float)(img.width() * Ratio) / 100; float height = (float)(img.height() * Ratio) / 100; boost::gil::rgb8_image_t resizedImg(width, height); boost::gil::resize_view(const_view(img), view(resizedImg), boost::gil::bilinear_sampler()); boost::gil::write_view(OutStream, boost::gil::const_view(resizedImg), T()); Thanks, Lloyd

2 2

bjam resources
by Antonis Polykratis 18 Jul '20

18 Jul '20

Hello, are there any bjam tutorials documentation about how I could create a project using bjam? Thanks

2 1

Boost ABI/Linkage of clang vs g++
by DV Henkel-Wallace 17 Jul '20

17 Jul '20

boost-users(a)lists.boost.org We build with clang++-10 w/libc++.a and g++-10 w/libstdc++.a, so build a copy of boost in each configuration as well. This works great on the Mac development machines but the clang case doesn't generate the correct linkage on the Linux deployment machines. The correct clang linkage is std::__1::basic_string... but boost builds with std::__cxx11::basic_string Here's the linkage of libc++: $ objdump -T /usr/lib/llvm-10/lib/libc++.so.1|c++filt|grep ::basic_string|head -1 0000000000057450 g DF .text 0000000000000048 Base std::__1::locale::locale(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) Notice: std::__1::basic_string< ... When compiling my own code with clang++-10 the correct symbol is generated: $ nm options.cc.o |c++filt |fgrep __ |fgrep ::set_option_name |head -1 0000000000000000 W fmt::v6::basic_format_context<std::__1::back_insert_iterator<fmt::v6::internal::buffer<char> >, char>::iterator... Notice std::__1:: ... However the boost object have the wrong symbol name: $ nm 3P/llvm/lib/libboost_program_options.a |c++filt |fgrep __ |fgrep ::basic_string |head -1 0000000000000000 W boost::program_options::unknown_option::unknown_option(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) Notice std::__cxx11::basic_string< ... I'm compiling boost this way: export CC=clang CXX="clang++ -stdlib=libc++" CXXSTD=c++20 ; ./b2 stdlib=libc++ toolset=clang boost.locale.icu=off boost.locale.std=off --with-atomic --with-chrono --with-date_time --with-headers --with-locale --with-log --with-program_options --with-random --with-regex --with-system --with-thread threading=multi -sNO_COMPRESSION=1 link=static install It's 1.73.0

1 0

[release] Boost 1.74.0 beta 1 released
by Marshall Clow 16 Jul '20

16 Jul '20

Boost release 1.74.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.74.0.beta.1/source/> The SHA256 checksums are as follows: 577a6b575ff2c227e14cce1b929c73d969475e58f3d2ab2901ad234f773bbd12 boost_1_74_0_b1.7z ba09c72dc848e7c0904922967014d853897b5a634926c910cc3b1fd627c31605 boost_1_74_0_b1.tar.bz2 2ccdc39efa076822cf1b359f9449f9d07707f3e27a18b393297b25885a9ff45b boost_1_74_0_b1.tar.gz c267c450166e040a374eaddab5e583cef09f6c3fe96a4db826172d0315c38dd5 boost_1_74_0_b1.zip For details of what's in the release, see < https://www.boost.org/users/history/version_1_74_0.html>. Please download the beta, give it a try, and report any problems you encounter. Issues that were found during the beta release process and will be fixed for the final 1.74.0 release: * The Boost.STLInterfaces documentation was left out of the beta. * Some of the Boost.Geometry documentation files have very long names; this could cause problems on platforms (like Windows) with shorter limits on path lengths. * There is a compile error in Boost.ASIO when compiling with 32-bit MSVC-14.2 with BOOST_BEAST_NO_TS_EXECUTORS. Thanks, -- The Boost Release Team

4 9