Dear list,

while writing a state machine, I added an explicit_entry to my machine. My problem now is, if I want to write different function for different event types for the entry action like this: template < class FSM> void on_entry(event2 const& ev,FSM&fsm ){ … } not all events were catched by it. After some compiling and generating an example, I know when the problem occurs. I am not sure if this is a bug or a feature ☺.

It's a bug ;-)

The event for the explicit entry is wrapped with a direct_entry_event. If the transition is from outside the statemachine this is quite ok (I got the original event, not the direct_entry_event), but if transition is inside the machine, the direct_entry_event is not removed and I got this to my on_entry.

The example and the console output from the listing below show this effect. Is this a compiler problem or a problem/bug/feature coming from the msm?

I am using a gcc 4.3.4 and boost 1.46.1 (trunk also shows this)

Kind regards, Sven Steckmann

I fixed this in the trunk (rev. 71879). Please let me know if you have any problem with the fix. Thanks, Christophe