Re: [Boost-users] Accessing MSM attribute under specific conditions causes non-compile

This is even more clear when I note that having an entry action on both the FSM and the initial state "seems redundant." And it is, but only for the top-most level composite state. For composite state embedded in other machines, history could cause the entry action on the composite state to be called, but the not the entry action on the (normally) initial state.

I don't think it's redundant if you consider the case of orthogonal regions. In this case, you usually want an entry action called only once. In any case, I think I have to precise the doc a bit on this. Regards, Christophe