September 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.Compute]: double3 - typedef redefinition with different types
by Manfred Doudar 30 Sep '20

30 Sep '20

Hello List, [Posting over from the Slack channel which didn't get any attention]: Any Boost.Compute users here that might be able to help with the following code snippet - BOOST_COMPUTE_ADAPT_STRUCT(double3, double3, (x, y, z)) BOOST_COMPUTE_FUNCTION(bool, CompareX, (double3 a, double3 b), { return a.x < b.x; }); boost::compute::vector<double> points; ... auto it = boost::compute::min_element(points.begin(), points.end(), CompareX, queue); results in the kernel compilation failure - --- build log --- <kernel>:9:3: error: typedef redefinition with different types ('struct double3' vs 'double __attribute__((ext_vector_type(3)))') } double3; ^ cl_kernel.h:154:1: note: previous definition is here __NV_DECLARE_VECT_TYPES(double, double) ^ cl_kernel.h:114:61: note: expanded from macro '__NV_DECLARE_VECT_TYPES' typedef __attribute__(( ext_vector_type(3) )) CTYPE CLTYPE##3; \ ^ <scratch space>:53:1: note: expanded from here double3 ^ ^@ Thanks, /M

1 0

unable to update boost version
by Shiladitya Porey 24 Sep '20

24 Sep '20

Respected Sir/Madam, I am running a code where the minimum required version of the boost package is 66. But the version of boost in my laptop is 65. I tried the command > sudo apt install libboost-filesystem-dev libboost-log-dev But it failed to update. Then I tried to download the package from the website and followed the instructions to install it. But still the version is still 65. Could you kindly help me, please? Thanking you, Sincerely, Shiladitya Porey -- Shiladitya Porey Graduate student Laboratory of Cosmology and Elementary Particle Physics <http://astro.nsu.ru/> Novosibirsk State University <https://english.nsu.ru/>, Russia Office: Room no. : 434,Old Building Mobile: 8 913 462-44-32 https://sites.google.com/a/g.nsu.ru/shiladitya/home

2 2

[log]: Filter declaration in settings files, associativity and operator precedence
by Bill Somerville 18 Sep '20

18 Sep '20

Hi all, I am experimenting with using multiple channels with Boost.Log. I am using the boost::trivial severity levels, the common attributes, and logging using BOOST_LOG_SEV() using a mix of global and class specific loggers. I am also using boost::log::init_from_stream(std::istream&) to configure sinks from a settings file. I would like to be able to define a sink filter that allows increasing the logging verbosity on just one channel but I am struggling to write succinct filer expressions. E.g given three channels A, B, and C I would like to write: Filter="(%Channel% = \"B\" and %Severity% >= trace) or %Severity% >= warning" to increase the verbosity to trace only on channel B, but this doesn't work. I am finding I have to write: Filter="(%Channel% = \"B\" and %Severity% >= trace) or (%Channel% != \"B\" and %Severity% >= warning)" Is this expected behaviour? If so then declaring more complex filtering will become burdensome. Regards Bill Somerville.

1 0

[Urgent request] : Boost default_locale() is causing an application crash!
by kamallochan Jena 17 Sep '20

17 Sep '20

Hi All, Thank you for your kind support! In one of our applications, we are using Boost library and recently found an application crash because of the locale object return from below highlighted code from Boost source code (path.cpp). Boost library source code (File name: path.cpp and line No: 865) seems to return NULL locale object [image: image.png] As per call stack, Application is found to be crashed when std::use_facet() tried to Getfacet id from the passed locale object : [image: image.png] Please Note: At above line 934, path_locale() calls to the above default_locale() which return an locale object with NULL value. *Can someone please answer the below queries:* 1>> In which scenario the code at std::locale(global_loc, new windows_file_codecvt);", mentioned above will return a locale object with NULL values ?? 2>> How to enable BOOST_ASSERT_MSG, so below code will execute ?? Example: BOOST_ASSERT_MSG(&path_locale(), "boost::filesystem::path locale initialization error"); 3>> In which conditions a locale object can be null ?? Thank you in Advance!!, please let me know if any further details are required on this issue. Regards, Kamal

2 2

[multiprecision] 128 bit integer support on Windows
by Neill Clift 15 Sep '20

15 Sep '20

Hi, I managed to get boost multi-precision to work with 128 bit integers on Windows using clang. I had to change this in clang.hpp: #if defined(__SIZEOF_INT128__) && !defined(BOOST_NVCC_CXX03) && !defined(_MSC_VER) <--- remove this last thing # define BOOST_HAS_INT128 #endif Clang-cl defines _MSC_VER for compat I guess. I had to pull in the library clang_rt.builtins-x86_64.lib for two routines needed for division and remainder. For my particular application I only saw a 10% improvement in performance. I am wondering if there are other things that need to be changed to get better performance? My program deals with integers of various sizes so it might be an artifact of the sizes of integers I mostly do operations on. I was expecting a bigger return. I am seeing the most expensive routine being _udivmodti4 on profiling. Division wasn't showing up as much in the traces before I made the change. Thanks. Neill.

1 0

Can boost.asio read/write io of files asynchronously?
by lampahome 02 Sep '20

02 Sep '20

As title, I read boost.asio documents and generally said io about http/network. I don't see any info. of io of files. Does boost.asio support read/write io of files asynchronously?

1 0