blob: f39b22d98648b6c71ca26a24f2e20a35abd673cb (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
<?xml version="1.0" encoding="UTF-8"?>
<!--
Copyright 2011-2012 Jacob Beard, INFICON, and other SCION contributors
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<!--
This is a test to illustrate the event lifeline, and how multiple events are handled. The whole set of triggered events will be dequeued from the inner event queue in the next small step. This is different from scxml, where only one event will be dequeued at a time in the next small step. So, SCXML semantics would lead to f2, whereas our semantics would lead to d.
-->
<scxml
datamodel="ecmascript"
xmlns="http://www.w3.org/2005/07/scxml"
initial="a"
version="1.0">
<state id="a">
<transition target="b" event="t">
</transition>
</state>
<state id="b">
<onentry>
<raise event="s"/>
<raise event="r"/>
</onentry>
<transition target="c" event="s"/>
</state>
<state id="c">
<transition target="f2" event="r"/>
<transition target="d"/>
</state>
<state id="f1">
</state>
<state id="d">
</state>
<state id="f2">
</state>
</scxml>
|
