From fe84503b031a67a5d88afe00a676578ace7a9608 Mon Sep 17 00:00:00 2001 From: Andreas Huber Date: Sun, 18 Jun 2006 10:31:25 +0000 Subject: [PATCH] Updated docs regarding local transitions to history. [SVN r34339] --- doc/faq.html | 6 ------ doc/future_and_history.html | 4 ++-- 2 files changed, 2 insertions(+), 8 deletions(-) diff --git a/doc/faq.html b/doc/faq.html index 5dae4e0..c0603fe 100644 --- a/doc/faq.html +++ b/doc/faq.html @@ -302,12 +302,6 @@ struct MyPump : PumpBase local transitions are supposed to work, see here for more information -
  • The origin of a transition to history must not be a direct or indirect -inner state of the state containing the history pseudo state. UML2.0 -explicitly allows this, the semantics of the library will be changed -accordingly for the 1.35 release, see -here for -more information
  • There is no direct support for the UML2.0 elements entry point and exit point. However, both can easily be simulated, the former with a typedef and the latter with a state that is a template (with the transition destination diff --git a/doc/future_and_history.html b/doc/future_and_history.html index 2d861c9..b7a55d5 100644 --- a/doc/future_and_history.html +++ b/doc/future_and_history.html @@ -45,8 +45,6 @@ review):

      -
    1. Make transitions to history UML2.0 compliant, see - here for more information
    2. Optimize state-entry and state-exit for speed and code-size
    3. Implement simple_state::triggering_event(), which @@ -165,6 +163,8 @@
    4. Declared state_base::~state_base virtual for GCC. This makes state exit slightly slower but does away with loads of "has virtual functions but non-virtual destructor" warnings
      5. +
    5. Made transitions to history UML2.0 compliant, see + here for more information

      6. 17 December, 2005