The following specification works in OSATE 2.7.0 and earlier, but causes a syntax error in OSATE 2.7.1. The specific error is on the behavior specification's in modes clause: "Couldn't resolve reference to mode 'normal'." But when autocomplete is activated inside the parentheses of the in modes clause, both the component's modes show up in the list.
thread group threadB
features
output: out event data port message_pm;
modes
normal: initial mode;
fast: mode;
end threadB;
thread group implementation threadB.impl
annex behavior_specification {**
states
s0: initial state;
s1: final state;
transitions
s0 -[ ]-> s1 {output:=1};
**} in modes (normal);
The following specification works in OSATE 2.7.0 and earlier, but causes a syntax error in OSATE 2.7.1. The specific error is on the behavior specification's
in modesclause: "Couldn't resolve reference to mode 'normal'." But when autocomplete is activated inside the parentheses of thein modesclause, both the component's modes show up in the list.