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, 31 insertions, 0 deletions

diff --git a/test/samples/w3c/txml/test178.txml b/test/samples/w3c/txml/test178.txml
new file mode 100644
index 0000000..de7a334
--- /dev/null
+++ b/test/samples/w3c/txml/test178.txml
@@ -0,0 +1,31 @@
+<?xml version="1.0"?>
+<!-- we test that multiple key/value pairs are included, even when the keys are the same.
+This is a manual test.  The tester must look at the log output and verify that both
+keys are there.  (This test uses the SCXML Event I/O processor, which is the only
+one that all platforms must support.  It does not specify the message format, so 
+we cannot test _event.raw directly.  Therefore we print it out for visual 
+inspection.) -->
+
+
+<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">
+  <onentry>
+   <send  event="event1">
+    <param conf:name="1" conf:expr="2"/>
+    <param conf:name="1" conf:expr="3"/>
+    </send>
+     </onentry>
+
+  <transition event="event1" target="final">
+   <log label="_event " conf:eventRaw=""/>
+   </transition>
+  <transition event="*" conf:targetfail=""/>
+ 
+ </state>
+
+
+<final id="final"/>
+<conf:fail/>
+
+</scxml>
\ No newline at end of file