Refactoring and W3C tests

- Moved core of interpreter to support various versions
- Added experimental setConfiguration()
- There can be more than one initial state

1 files changed, 36 insertions, 0 deletions

diff --git a/test/samples/w3c/txml/test409.txml b/test/samples/w3c/txml/test409.txml
new file mode 100644
index 0000000..abc92ee
--- /dev/null
+++ b/test/samples/w3c/txml/test409.txml
@@ -0,0 +1,36 @@
+<?xml version="1.0"?>
+<!-- we test that states are removed from the active states list as they are exited.  When s01's onexit handler
+fires, s011 should not be on the active state list, so in(S011) should be false, and event1 should not
+be raised.  Therefore the timeout should fire to indicate success   -->
+
+
+<scxml initial="s0" version="1.0" conf:datamodel=""  xmlns="http://www.w3.org/2005/07/scxml" xmlns:conf="http://www.w3.org/2005/scxml-conformance">
+
+     
+<state id="s0" initial="s01">
+  <onentry>
+    <send event="timeout" delay="1s"/>
+    </onentry>
+  
+  <transition event="timeout" conf:targetpass=""/> 
+  <transition event="event1" conf:targetfail=""/>
+  
+  <state id="s01" initial="s011">
+    <onexit>
+     <if conf:inState="s011">
+       <raise event="event1"/>
+       </if>
+       </onexit>
+       
+    <state id="s011">
+      <transition target="s02"/>
+      </state>
+  </state> <!-- end s01 -->
+
+<state id="s02"/>
+
+</state> <!-- end s0 -->
+ 
+<conf:pass/>
+<conf:fail/>
+</scxml>
\ No newline at end of file