Closed rherrmannr closed 4 years ago
Using [true]at transitions without always/else leads to compile errors in C, as the sequencer does not do any optimizations. Using always [true] resolves the problem, as the sequencer recognizes an AlwaysEvent and evaluates the guard expression.
[true]
always [true]
AlwaysEvent
AlwaysTrue.zip
Same problem for C++ and Java:
void AlwaysTrue::effect_alwaysTrue__choice_0_tr1() { (); }
private void effect_alwaysTrue_A_tr1() { exitSequence_alwaysTrue_A(); (); }
We need to discuss if we want to do the same optimizations as we do with always [true] or if we extend the validator.
Might be also related to #3134
Using
[true]
at transitions without always/else leads to compile errors in C, as the sequencer does not do any optimizations. Usingalways [true]
resolves the problem, as the sequencer recognizes anAlwaysEvent
and evaluates the guard expression.AlwaysTrue.zip
Same problem for C++ and Java: