Roadmap of boost::fsm
What is the state of boost::fsm? Are there plans to move it in to Boost from the sandbox? I have noticed that the problem with atomic_count_gcc has now been fixed on HEAD so that is not a limiting factor anymore.
It has to undergo a review to be accepted in to boost first. AFAIK, this is scheduled for later this year, so I doubt we'll see fsm in 1.32, possibly 1.33 depending on the review schedule and its beeing accepted. Cheers Russell Schalk_Cronje@McAfee.com wrote:
What is the state of boost::fsm? Are there plans to move it in to Boost from the sandbox? I have noticed that the problem with atomic_count_gcc has now been fixed on HEAD so that is not a limiting factor anymore.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
What is the state of boost::fsm? Are there plans to move it in to Boost from
<Schalk_Cronje <at> McAfee.com> writes: the sandbox? I'm currently busy implementing the additional features that were requested in the last discussion (exit() and BOOST_FSM_RELAX_TRANSITION_CONTEXT). After that I'll concentrate on implementing regression tests. Progress is quite slow at the moment as I'm swamped with other stuff but I think I'll have everything ready when the formal review comes (late October or mid November). If the library is accepted and no major rewrites are requested it should be available in the next official boost release after review... Regards, Andreas
participants (3)
-
Andreas Huber -
Russell Hind -
Schalk_Cronje＠McAfee.com