definition

 template <class Source,class Event,class Target,class
                                    Action,class Guard> Row {
}

tags

row_type_tag is defined differently for every specialization:

methods

Like any other front-end, Row implements the two necessary static functions for action and guard call. Each function receives as parameter the (deepest-level) state machine processsing the event, the event itself, the source and target states and all the states contained in a state machine.

definition

 template <class Event,class Action,class Guard>
                                    Internal {
}

tags

row_type_tag is defined differently for every specialization:

methods

Like any other front-end, Internal implements the two necessary static functions for action and guard call. Each function receives as parameter the (deepest-level) state machine processsing the event, the event itself, the source and target states and all the states contained in a state machine.

definition

 template <class Sequence> ActionSequence_ {
}

methods

This helper functor is made for use in a transition table and in a state behavior and therefore implements an operator() with 3 and with 4 arguments:

definition

 Defer {
}

methods

This helper functor is made for use in a transition table and therefore implements an operator() with 4 arguments:

definition

This is an internal transition with an action called during the transition.

 template< class Event, class CalledForAction, void
                                    (CalledForAction::*action)(Event const&)>
                                    a_internal {
}

template parameters

definition

 template< class Event, class CalledForGuard, bool
                                    (CalledForGuard::*guard)(Event const&)>
                                    g_internal {
}

template parameters

definition

 template< class Event, class CalledForAction, void
                                    (CalledForAction::*action)(Event const&), class
                                    CalledForGuard, bool (CalledForGuard::*guard)(Event const&)>
                                    internal {
}

template parameters

definition

 template< class Event > _internal {
}

template parameters

definition

 template< class Source, class Event, class Target >
                                    _row2 {
}

template parameters

definition

 template< class Source, class Event, class Target,
                                 {
}

 class CalledForAction, void
                                    (CalledForAction::*action)(Event const&) > _row2 {
}

template parameters

definition

 template< class Source, class Event, class Target,
                                 {
}

 class CalledForGuard, bool (CalledForGuard::*guard)(Event
                                    const&) > _row2 {
}

template parameters

definition

 template< class Source, class Event, class Target,
                                 {
}

 class CalledForAction, void
                                    (CalledForAction::*action)(Event const&),  {
}

 class CalledForGuard, bool (CalledForGuard::*guard)(Event
                                    const&) > _row2 {
}

template parameters

definition

 template< class Source, class Event,  {
}

 class CalledForAction, void
                                    (CalledForAction::*action)(Event const&) > _row2 {
}

template parameters

definition

 template< class Source, class Event,  {
}

 class CalledForGuard, bool (CalledForGuard::*guard)(Event
                                    const&) > _row2 {
}

template parameters

definition

 template< class Source, class Event,  {
}

 class CalledForAction, void
                                    (CalledForAction::*action)(Event const&),  {
}

 class CalledForGuard, bool (CalledForGuard::*guard)(Event
                                    const&) > _row2 {
}

template parameters

typedefs

row methods

Like any other front-end, the following transition row types implements the two necessary static functions for action and guard call. Each function receives as parameter the (deepest-level) state machine processsing the event, the event itself, the source and target states and all the states contained in a state machine (ignored).

a_row

This is a transition with action and without guard.

template< class Source, class Event, class Target, void (Derived::*action)(Event const&) > a_row

g_row

This is a transition with guard and without action.

template< class Source, class Event, class Target, bool (Derived::*guard)(Event const&) > g_row

row

This is a transition with guard and action.

template< class Source, class Event, class Target, void (Derived::*action)(Event const&), bool (Derived::*guard)(Event const&) > row

_row

This is a transition without action or guard. The state machine only changes active state.

template< class Source, class Event, class Target > _row

a_irow

This is an internal transition for use inside a transition table, with action and without guard.

template< class Source, class Event, void (Derived::*action)(Event const&) > a_irow

g_irow

This is an internal transition for use inside a transition table, with guard and without action.

template< class Source, class Event, bool (Derived::*guard)(Event const&) > g_irow

irow

This is an internal transition for use inside a transition table, with guard and action.

template< class Source, class Event, void (Derived::*action)(Event const&), bool (Derived::*guard)(Event const&) > irow

_irow

This is an internal transition without action or guard. As it does nothing, it means "ignore event".

template< class Source, class Event > _irow

methods

state_machine_def provides a default implementation in case of an event which cannot be processed by a state machine (no transition found). The implementation is using a BOOST_ASSERT so that the error will only be noticed in debug mode. Overwrite this method in your implementation to change the behavior.

state_machine_def provides a default implementation in case an exception is thrown by a state (entry/exit) or transition (action/guard) behavior. The implementation is using a BOOST_ASSERT so that the error will only be noticed in debug mode. Overwrite this method in your implementation to change the behavior. This method will be called only if exception handling is not deactivated (default) by defining has_no_message_queue.

no_sm_ptr

deprecated: default policy for states. It means that states do not need to save a pointer to their containing state machine.

sm_ptr

deprecated: state policy. It means that states need to save a pointer to their containing state machine. When seeing this flag, the back-end will call set_sm_ptr(fsm*) and give itself as argument.

state

Basic type for simple states. Inherit from this type to define a simple state. The first argument is needed if you want your state (and all others used in a concrete state machine) to inherit a basic type for logging or providing a common behavior.

 template<class Base = default_base_state,class
                                    SMPtrPolicy = no_sm_ptr> state {
}

terminate_state

Basic type for terminate states. Inherit from this type to define a terminate state. The first argument is needed if you want your state (and all others used in a concrete state machine) to inherit a basic type for logging or providing a common behavior.

 template<class Base = default_base_state,class
                                    SMPtrPolicy = no_sm_ptr> terminate_state {
}

interrupt_state

Basic type for interrupt states. Interrupt states prevent any further event handling until EndInterruptEvent is sent. Inherit from this type to define a terminate state. The first argument is the name of the event ending the interrupt. The second argument is needed if you want your state (and all others used in a concrete state machine) to inherit a basic type for logging or providing a common behavior.

 template<class EndInterruptEvent,class Base =
                                    default_base_state, {
}

 class SMPtrPolicy = no_sm_ptr>
                                    interrupt_state {
}

explicit_entry

Inherit from this type in addition to the desired state type to enable this state for direct entering. The template parameter gives the region id of the state (regions are numbered in the order of the initial_state typedef).

 template <int ZoneIndex=-1> explicit_entry {
}

entry_pseudo_state

Basic type for entry pseudo states. Entry pseudo states are an predefined entry into a submachine and connect two transitions. The first argument is the id of the region entered by this state (regions are numbered in the order of the initial_state typedef). The second argument is needed if you want your state (and all others used in a concrete state machine) to inherit a basic type for logging or providing a common behavior.

 template<int RegionIndex=-1,class Base =
                                    default_base_state, {
}

 class SMPtrPolicy = no_sm_ptr>
                                    entry_pseudo_state {
}

exit_pseudo_state

Basic type for exit pseudo states. Exit pseudo states are an predefined exit from a submachine and connect two transitions. The first argument is the name of the event which will be "thrown" out of the exit point. This event does not need to be the same as the one sent by the inner region but must be convertible from it. The second argument is needed if you want your state (and all others used in a concrete state machine) to inherit a basic type for logging or providing a common behavior.

 template<class Event,class Base =
                                    default_base_state, {
}

 class SMPtrPolicy = no_sm_ptr>
                                    exit_pseudo_state {
}

build_stt

The function build_stt evaluates the grammar-conform expression as parameter. It returns a transition table, which is a mpl::vector of transitions (rows) or, if the expression is ill-formed (does not match the grammar), the type invalid_type, which will lead to a compile-time static assertion when this transition table is passed to a state machine.

build_internal_stt

The function build_internal_stt evaluates the grammar-conform expression as parameter. It returns a transition table, which is a mpl::vector of transitions (rows) or, if the expression is ill-formed (does not match the grammar), the type invalid_type, which will lead to a compile-time static assertion when this transition table is passed to a state machine.

transition table

The transition table accepts the following grammar:

Stt := Row | (Stt ',' Stt)
Row := (Target '==' (SourcePlusEvent)) /* first syntax*/
       | ( (SourcePlusEvent) '==' Target ) /* second syntax*/
       | (SourcePlusEvent) /* internal transitions */
SourcePlusEvent := (BuildSource '+' BuildEvent)/* standard transition*/ 
                   | (BuildSource) /* anonymous transition */
BuildSource := state_tag | (state_tag '/' Action) | (state_tag '[' Guard ']') 
            | (state_tag '[' Guard ']' '/' Action)
BuildEvent := event_tag | (event_tag '/' Action) | (event_tag '[' Guard ']') 
            | (event_tag '[' Guard ']' '/' Action)

The grammars Action and Guard are defined in state_grammar.hpp and guard_grammar.hpp respectively. state_tag and event_tag are inherited from euml_state (or other state variants) and euml_event respectively. For example, following declarations are possible:

target == source + event [guard] / action,
source + event [guard] / action == target,
source + event [guard] / (action1,action2) == target,
target == source + event [guard] / (action1,action2),
target == source + event,
source + event == target,
target == source + event [guard],
source + event [guard] == target,
target == source + event / action,
source + event /action == target,
source / action == target, /*anonymous transition*/
target == source / action, /*anonymous transition*/
source + event /action, /* internal transition*/

internal transition table

The internal transition table accepts the following grammar:

IStt := BuildEvent | (IStt ',' IStt)

BuildEvent being defined for both internal and standard transition tables.

build_sm

This function has several overloads. The return type is not relevant to you as only decltype (return type) is what one needs.

Defines a state machine without entry or exit:

Defines a state machine with entry behavior:

Defines a state machine with entry and exit behaviors:

Defines a state machine with entry, exit behaviors and attributes:

Defines a state machine with entry, exit behaviors, attributes and configuration (deferred events, flags):

Defines a state machine with entry, exit behaviors, attributes, configuration (deferred events, flags) and a base state:

Notice that this function requires the extra parameter class StateNameTag to disambiguate state machines having the same parameters but still being different.

build_state

This function has several overloads. The return type is not relevant to you as only decltype (return type) is what one needs.

Defines a simple state without entry or exit:

Defines a simple state with entry behavior:

Defines a simple state with entry and exit behaviors:

Defines a simple state with entry, exit behaviors and attributes:

Defines a simple state with entry, exit behaviors, attributes and configuration (deferred events, flags):

Defines a simple state with entry, exit behaviors, attributes, configuration (deferred events, flags) and a base state:

Notice that this function requires the extra parameter class StateNameTag to disambiguate states having the same parameters but still being different.

build_terminate_state

This function has the same overloads as build_state.

build_interrupt_state

This function has several overloads. The return type is not relevant to you as only decltype (return type) is what one needs.

Defines an interrupt state without entry or exit:

Defines an interrupt state with entry behavior:

Defines an interrupt state with entry and exit behaviors:

Defines an interrupt state with entry, exit behaviors and attributes:

Defines an interrupt state with entry, exit behaviors, attributes and configuration (deferred events, flags):

Defines an interrupt state with entry, exit behaviors, attributes, configuration (deferred events, flags) and a base state:

Notice that this function requires the extra parameter class StateNameTag to disambiguate states having the same parameters but still being different.

build_entry_state

This function has several overloads. The return type is not relevant to you as only decltype (return type) is what one needs.

Defines an entry pseudo state without entry or exit:

Defines an entry pseudo state with entry behavior:

Defines an entry pseudo state with entry and exit behaviors:

Defines an entry pseudo state with entry, exit behaviors and attributes:

Defines an entry pseudo state with entry, exit behaviors, attributes and configuration (deferred events, flags):

Defines an entry pseudo state with entry, exit behaviors, attributes, configuration (deferred events, flags) and a base state:

Notice that this function requires the extra parameter class StateNameTag to disambiguate states having the same parameters but still being different.

build_exit_state

This function has several overloads. The return type is not relevant to you as only decltype (return type) is what one needs.

Defines an exit pseudo state without entry or exit:

Defines an exit pseudo state with entry behavior:

Defines an exit pseudo state with entry and exit behaviors:

Defines an exit pseudo state with entry, exit behaviors and attributes:

Defines an exit pseudo state with entry, exit behaviors, attributes and configuration (deferred events, flags):

Defines an exit pseudo state with entry, exit behaviors, attributes, configuration (deferred events, flags) and a base state:

Notice that this function requires the extra parameter class StateNameTag to disambiguate states having the same parameters but still being different.

build_explicit_entry_state

This function has the same overloads as build_entry_state and explicit_entry_func_state as return type.

euml_event

The basic type for events with eUML.

 template <class EventName> euml_event; {
}

struct play : euml_event<play>{};

euml_state

The basic type for states with eUML. You will usually not use this type directly as it is easier to use BOOST_MSM_EUML_STATE, BOOST_MSM_EUML_INTERRUPT_STATE, BOOST_MSM_EUML_TERMINATE_STATE, BOOST_MSM_EUML_EXPLICIT_ENTRY_STATE, BOOST_MSM_EUML_ENTRY_STATE or BOOST_MSM_EUML_EXIT_STATE.

 template <class StateName> euml_state; {
}

You can however use this type directly if you want to provide your state with extra functions or provide entry or exit behaviors without functors, for example:

struct Empty : public msm::front::state<> , public euml_state<Empty> 
{
    void foo() {...}
    template <class Event,class Fsm>
    void on_entry(Event const& evt,Fsm& fsm){...}
};

euml_flag

The basic type for flags with eUML.

 template <class FlagName> euml_flag; {
}

struct PlayingPaused: euml_flag<PlayingPaused>{};

euml_action

The basic type for state or transition behaviors and guards with eUML.

 template <class AcionName> euml_action; {
}

struct close_drawer : euml_action<close_drawer>
{
    template <class Fsm,class Evt,class SourceState,class TargetState>
    void operator()(Evt const& , Fsm&, SourceState& ,TargetState& ) {...}
};

Or, as state entry or exit behavior:

struct Playing_Entry : euml_action<Playing_Entry>
{
    template <class Event,class Fsm,class State>
    void operator()(Event const&,Fsm& fsm,State& ){...}
};

euml_config

The basic type for configuration possibilities with eUML.

 template <class ConfigName> euml_config; {
}

You normally do not use this type directly but instead the instances of predefined configuration:

invalid_type

Type returned by grammar parsers if the grammar is invalid. Seeing this type will result in a static assertion.

no_action

Placeholder type for use in entry/exit or transition behaviors, which does absolutely nothing.

source_

Generic object or function for the source state of a given transition:

target_

Generic object or function for the target state of a given transition:

state_

Generic object or function for the state of a given entry / exit behavior. state_ means source_ while in the context of an exit behavior and target_ in the context of an entry behavior:

event_

Generic object or function for the event triggering a given transition (valid in a transition behavior, as well as in state entry/exit behaviors):

fsm_

Generic object or function for the state machine containing a given transition:

substate_

Generic object or function returning a state of a given state machine:

attribute_

Generic object or function returning the attribute passed (by name) as second parameter of the thing passed as first (a state, event or state machine). Example:

attribute_(substate_(my_state),cd_name_attribute)++

True_

Functor returning true for transition or state behaviors. Like all constants, only the functor form exists, so parenthesis are necessary. Example:

if_then_(True_(),/* some action always called*/)

False_

Functor returning false for transition or state behaviors. Like all constants, only the functor form exists, so parenthesis are necessary. Example:

if_then_(False_(),/* some action never called */)

Int_<int value>

Functor returning an integer value for transition or state behaviors. Like all constants, only the functor form exists, so parenthesis are necessary. Example:

target_(m_ringing_cpt) = Int_<RINGING_TIME>() // RINGING_TIME is a constant

Char_<char value>

Functor returning a char value for transition or state behaviors. Like all constants, only the functor form exists, so parenthesis are necessary. Example:

// look for 'S' in event.m_song
[string_find_(event_(m_song),Char_<'S'>(),Size_t_<0>()) != Npos_<string>()]

Size_t_<size_t value>

Functor returning a size_t value for transition or state behaviors. Like all constants, only the functor form exists, so parenthesis are necessary. Example:

substr_(event_(m_song),Size_t_<1>()) // returns a substring of event.m_song

String_ < mpl::string >

Functor returning a string for transition or state behaviors. Like all constants, only the functor form exists, so parenthesis are necessary. Requires boost >= 1.40 for mpl::string.

Example:

// adds "Let it be" to fsm.m_src_container
push_back_(fsm_(m_src_container), String_<mpl::string<'Let','it ','be'> >())

Predicate_ < some_stl_compatible_functor >

This functor eUML-enables a STL functor (for use in an algorithm). This is necessary because all what is in the transition table must be a eUML terminal.

Example:

//equivalent to: 
//std::accumulate(fsm.m_vec.begin(),fsm.m_vec.end(),1,std::plus<int>())== 1
accumulate_(begin_(fsm_(m_vec)),end_(fsm_(m_vec)),Int_<1>(),
            Predicate_<std::plus<int> >()) == Int_<1>())

process_

This function sends an event to up to 4 state machines by calling process_event on them:

process2_

This function sends an event to up to 3 state machines by calling process_event on them and copy-constructing the event from the data passed as second parameter:

Example:

// processes NotFound on current state machine, 
// copy-constructed with event.m_song
process2_(NotFound,event_(m_song))

With the following definitions:

BOOST_MSM_EUML_DECLARE_ATTRIBUTE(std::string,m_song)//declaration of m_song
NotFound (const string& data) // copy-constructor of NotFound

is_flag_

This function tells if a flag is active by calling is_flag_active on the current state machine or one passed as parameter:

defer_

This object defers the current event by calling defer_event on the current state machine. Example:

Empty() + play() / defer_

explicit_(submachine-name,state-name)

Used as transition's target, causes an explicit entry into the given state from the given submachine. Several explicit_ as targets, separated by commas, means a fork. The state must have been declared as such using BOOST_MSM_EUML_EXPLICIT_ENTRY_STATE.

entry_pt_(submachine-name,state-name)

Used as transition's target from a containing state machine, causes submachine-name to be entered using the given entry pseudo-state. This state must have been declared as pseudo entry using BOOST_MSM_EUML_ENTRY_STATE.

exit_pt_(submachine-name,state-name)

Used as transition's source from a containing state machine, causes submachine-name to be left using the given exit pseudo-state. This state must have been declared as pseudo exit using BOOST_MSM_EUML_EXIT_STATE.

MSM_EUML_FUNCTION

This macro creates a eUML function and a functor for use with the functor front-end, based on a free function:

Note that the function itself can take up to 5 arguments.

Example:

MSM_EUML_FUNCTION(BinarySearch_,std::binary_search,binary_search_,bool,bool)

Can be used like:

binary_search_(begin_(fsm_(m_var)),end_(fsm_(m_var)),Int_<9>())

MSM_EUML_METHOD

This macro creates a eUML function and a functor for use with the functor front-end, based on a method:

Note that the method itself can take up to 4 arguments (5 like for a free function - 1 for the object on which the method is called).

Example:

struct Empty : public msm::front::state<> , public euml_state<Empty> 
{
     void activate_empty() {std::cout << "switching to Empty " << std::endl;}
... 
};
MSM_EUML_METHOD(ActivateEmpty_,activate_empty,activate_empty_,void,void)

Can be used like:

Empty == Open + open_close / (close_drawer , activate_empty_(target_))

BOOST_MSM_EUML_ACTION(action-instance-name)

This macro declares a behavior type and a const instance for use in state or transition behaviors. The action implementation itself follows the macro declaration, for example:

BOOST_MSM_EUML_ACTION(good_disk_format)
{
     template <class Fsm,class Evt,class SourceState,class TargetState>
     void/bool operator()(Evt const& evt,Fsm&,SourceState& ,TargetState& ){...}
};

BOOST_MSM_EUML_FLAG(flag-instance-name)

This macro declares a flag type and a const instance for use in behaviors.

BOOST_MSM_EUML_FLAG_NAME(flag-instance-name)

This macro returns the name of the flag type generated by BOOST_MSM_EUML_FLAG. You need this where the type is required (usually with the back-end method is_flag_active). For example:

fsm.is_flag_active<BOOST_MSM_EUML_FLAG_NAME(CDLoaded)>()

BOOST_MSM_EUML_DECLARE_ATTRIBUTE(event-type,event-name)

This macro declares an attribute called event-name of type event-type. This attribute can then be made part of an attribute list using BOOST_MSM_EUML_ATTRIBUTES.

BOOST_MSM_EUML_ATTRIBUTES(attributes-expression,attributes-name)

This macro declares an attribute list called attributes-name based on the expression as first argument. These attributes can then be made part of an event using BOOST_MSM_EUML_EVENT_WITH_ATTRIBUTES, of a state as 3rd parameter of BOOST_MSM_EUML_STATE or of a state machine as 5th parameter of BOOST_MSM_EUML_DECLARE_STATE_MACHINE.

Attributes are added using left-shift, for example:

// m_song is of type std::string
BOOST_MSM_EUML_DECLARE_ATTRIBUTE(std::string,m_song)
// contains one attribute, m_song
BOOST_MSM_EUML_ATTRIBUTES((attributes_ << m_song ), FoundDef)

BOOST_MSM_EUML_EVENT(event-instance name)

This macro defines an event type (event-instance-name_helper) and declares a const instance of this event type called event-instance-name for use in a transition table or state behaviors.

BOOST_MSM_EUML_EVENT_WITH_ATTRIBUTES(event-instance-name,attributes)

This macro defines an event type (event-instance-name_helper) and declares a const instance of this event type called event-instance-name for use in a transition table or state behaviors. The event will have as attributes the ones passed by the second argument:

BOOST_MSM_EUML_EVENT_WITH_ATTRIBUTES(Found,FoundDef)

The created event instance supports operator()(attributes) so that

my_back_end.process_event(Found(some_string))

is possible.

BOOST_MSM_EUML_EVENT_NAME(event-instance-name)

This macro returns the name of the event type generated by BOOST_MSM_EUML_EVENT or BOOST_MSM_EUML_EVENT_WITH_ATTRIBUTES. You need this where the type is required (usually inside a back-end definition). For example:

typedef msm::back::state_machine<Playing_,
msm::back::ShallowHistory<mpl::vector<BOOST_MSM_EUML_EVENT_NAME(end_pause)
> > > Playing_type;

BOOST_MSM_EUML_STATE(build-expression,state-instance-name)

This macro defines a state type (state-instance-name_helper) and declares a const instance of this state type called state-instance-name for use in a transition table or state behaviors.

There are several possibilitites for the expression syntax:

BOOST_MSM_EUML_INTERRUPT_STATE(build-expression,state-instance-name)

This macro defines an interrupt state type (state-instance-name_helper) and declares a const instance of this state type called state-instance-name for use in a transition table or state behaviors.

There are several possibilitites for the expression syntax. In all of them, the first argument is the name of the event (generated by one of the previous macros) ending the interrupt:

BOOST_MSM_EUML_TERMINATE_STATE(build-expression,state-instance-name)

This macro defines a terminate pseudo-state type (state-instance-name_helper) and declares a const instance of this state type called state-instance-name for use in a transition table or state behaviors.

There are several possibilitites for the expression syntax:

BOOST_MSM_EUML_EXIT_STATE(build-expression,state-instance-name)

This macro defines an exit pseudo-state type (state-instance-name_helper) and declares a const instance of this state type called state-instance-name for use in a transition table or state behaviors.

There are several possibilitites for the expression syntax:

Note that the forwarded_event must be constructible from the event sent by the submachine containing the exit point.

BOOST_MSM_EUML_ENTRY_STATE(int region-index,build-expression,state-instance-name)

This macro defines an entry pseudo-state type (state-instance-name_helper) and declares a const instance of this state type called state-instance-name for use in a transition table or state behaviors.

There are several possibilitites for the expression syntax:

BOOST_MSM_EUML_EXPLICIT_ENTRY_STATE(int region-index,build-expression,state-instance-name)

This macro defines a submachine's substate type (state-instance-name_helper), which can be explicitly entered and also declares a const instance of this state type called state-instance-name for use in a transition table or state behaviors.

There are several possibilitites for the expression syntax:

BOOST_MSM_EUML_STATE_NAME(state-instance-name)

This macro returns the name of the state type generated by BOOST_MSM_EUML_STATE or other state macros. You need this where the type is required (usually using a backend function). For example:

fsm.get_state<BOOST_MSM_EUML_STATE_NAME(StringFind)&>().some_state_function();

BOOST_MSM_EUML_DECLARE_STATE(build-expression,state-instance-name)

Like BOOST_MSM_EUML_STATE but does not provide an instance, simply a type declaration.

BOOST_MSM_EUML_DECLARE_INTERRUPT_STATE(build-expression,state-instance-name)

Like BOOST_MSM_EUML_INTERRUPT_STATE but does not provide an instance, simply a type declaration.

BOOST_MSM_EUML_DECLARE_TERMINATE_STATE(build-expression,state-instance-name)

Like BOOST_MSM_EUML_TERMINATE_STATE but does not provide an instance, simply a type declaration.

BOOST_MSM_EUML_DECLARE_EXIT_STATE(build-expression,state-instance-name)

Like BOOST_MSM_EUML_EXIT_STATE but does not provide an instance, simply a type declaration.

BOOST_MSM_EUML_DECLARE_ENTRY_STATE(int region-index,build-expression,state-instance-name)

Like BOOST_MSM_EUML_ENTRY_STATE but does not provide an instance, simply a type declaration.

BOOST_MSM_EUML_DECLARE_EXPLICIT_ENTRY_STATE(int region-index,build-expression,state-instance-name)

Like BOOST_MSM_EUML_EXPLICIT_ENTRY_STATE but does not provide an instance, simply a type declaration.

BOOST_MSM_EUML_TRANSITION_TABLE(expression, table-instance-name)

This macro declares a transition table type and also declares a const instance of the table which can then be used in a state machine declaration (see BOOST_MSM_EUML_DECLARE_STATE_MACHINE).The expression must follow the transition table grammar.

BOOST_MSM_EUML_DECLARE_TRANSITION_TABLE(iexpression,table-instance-name)

Like BOOST_MSM_EUML_TRANSITION_TABLE but does not provide an instance, simply a type declaration.

BOOST_MSM_EUML_INTERNAL_TRANSITION_TABLE(expression, table-instance-name)

This macro declares a transition table type and also declares a const instance of the table.The expression must follow the transition table grammar. For the moment, this macro is not used.

BOOST_MSM_EUML_DECLARE_INTERNAL_TRANSITION_TABLE(iexpression,table-instance-name)

Like BOOST_MSM_EUML_TRANSITION_TABLE but does not provide an instance, simply a type declaration. This is currently the only way to declare an internal transition table with eUML. For example:

BOOST_MSM_EUML_DECLARE_STATE((Open_Entry,Open_Exit),Open_def)
struct Open_impl : public Open_def
{
    BOOST_MSM_EUML_DECLARE_INTERNAL_TRANSITION_TABLE((
          open_close [internal_guard1] / internal_action1 ,
          open_close [internal_guard2] / internal_action2
    ))
};