Sebastian

Hava a look at Akka. https://akka.io/

This could possibly be solved in the port with pragma GCC optimize or using intrinsics. The code could also be wrapped in a function with an attribute __attribute__((optimize("O0")))

This could possibly be solved in the port with pragma GCC optimize or using intrinsics. The code could also be wrappen in a function with an attribute __attribute__((optimize("O0")))

This could possibly be solved in the port with pragma GCC optimize or using intrinsics.

What I do is adding the me pointer when posting an event I want an answer for. This is because when I first needed this, it looked like Miro does not want us to access QF_active_. QActive *QF_active_[QF_MAX_ACTIVE + 1]; /* to be used by QF ports only */ But now, using QUTest I think it would be better using the prio, because the me-pointer parameter makes the code hard to test. Is there another way to get an AO from the prio?

What I do is adding the me pointer when posting an event I want an answer for. This is because when I first needed this, it looked like Miro does not want us to access QF_active_. QActive *QF_active_[QF_MAX_ACTIVE + 1]; /* to be used by QF ports only */ But now, using QUTest I think it would be better using the prio, but the reference makes the code hard to test. Is there another way to get an AO from the prio?

What I do is adding the me pointer when posting an event I want an answer for. This is because when I first needed this, it looked like Miro does not want us to access QF_active_ (the only way to get a reference to an AO via prio) QActive *QF_active_[QF_MAX_ACTIVE + 1]; /* to be used by QF ports only */ But now, using QUTest I think it would be better using the prio, but the reference makes the code hard to test. Is there another way to get an AO from the prio?

First of all I want to say, that I'm really happy to finally have a solid way to test QP applications, this was the last thing I was missing in this great framework. Here are my questions: when using QUTest, events posted by the unit-under-test (UUT) are not really processed by the framework, but they are just traced. This is OK when the event the UUT posts is some result of a request to the UUT. But what if the event is internal to the UUT, for example when using the reminder pattern? The only solution...