SinelaboreRT Header Logo

SinelaboreRT

As simple as possible, but not any simpler!

User Tools

Site Tools


wiki:news:27okt2012

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
wiki:news:27okt2012 [2012/11/19 22:12] – [New beta version supporting regions] pmuellerwiki:news:27okt2012 [2013/08/12 15:11] – [How regions are implemented] pmueller
Line 48: Line 48:
   * For each region an own function is generated. Its name is automatically derived from the region name.   * For each region an own function is generated. Its name is automatically derived from the region name.
   * If a state contains several regions they are called one after the other (in alphabetical order). If the event sent to the state machine was processed in one of the regions no further event handling happens. Otherwise the event is processed in the parent state. This is similar to the event handling of normal hierarchical state machines.   * If a state contains several regions they are called one after the other (in alphabetical order). If the event sent to the state machine was processed in one of the regions no further event handling happens. Otherwise the event is processed in the parent state. This is similar to the event handling of normal hierarchical state machines.
-  * To maintain consistency during execution of machine code a copy of the instance data is created at the beginning of the state machine code. All tests are performed on the original instance data. All changes are done on the copy. This ensures that all regions "see" the same situation when running. At the end of the machine code the modified instance data is copied back to the original data. FIXME Note: this is not yet available in the C++ backend.+  * To maintain consistency during execution of machine code a copy of the instance data is created at the beginning of the state machine code. All tests are performed on the original instance data. All changes are done on the copy. This ensures that all regions "see" the same situation when running. At the end of the machine code the modified instance data is copied back to the original data.  <del>Note: this is not yet available in the C++ backend.</del>
  
  
wiki/news/27okt2012.txt · Last modified: 2022/08/17 19:47 by pmueller

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki