Riom

The `unexpected_event` is explained in the [tutorial](https://boost-ext.github.io/sml/tutorial.html). It seems to contradict your statement above. I have not seen the `event`. Is this mentioned anywhere? I think this definitely should be...

Oh no! ;) My understanding is the following: - The docs say `unexpected_event` catches all not handled events. - You on the other hand say `unexpected_event` catches all not handled...

@erikzenker An uncaught event isn't necessarily a usage error. I often have events triggered from external sources that might be too late and therefore will, intentionally, no longer be caught....

I see - thanks for the explanation. Though I'm not convinced this is the best possible behaviour. Also I wonder what defines an `unexpected_event` in the context of a composite...

I always use `sm.process_event(start {}); // working`. You create an instance of the event and pass it on to the state machine. To me this seems like the most natural...

What's the point of an internal transition with no action?

Not sure exactly what your question is. Do you want to build an event queue that then is processed by a dedicated thread? You need to use type erasure of...

@drorspei Thanks for your workaround. The first version appears to work fine, but the second one for some reason always returns false... I'm also not quire following the magic here:...

Explicit entry is not supported by SML. Therefore I would say this is not a non-issue and can be closed.

Is it? I can't find it in the presentation you linked.