T'is possible that the state objects should be singletons, since they can be shared amongst all objects using the same set of states. The current state is that to which the object points.. On 12/18/06, Andrey Semashev <andysem@mail.ru> wrote:
Hello Alexander,
Monday, December 18, 2006, 12:02:53 AM, you wrote:
Pavel Vozenilek wrote:
The Statechart library is named as is not to give impression that this is the only possible FSM implementation in Boost.
-------------
An interesting idea had bubbled up during the review - a FSM that could be "hidden" within a class and would simplify internals of the class.
Something like that was described on: http://www.codeproject.com/cpp/statebased.asp but this implementation is IMHO too complicated for the end user.
Also, you can take a look at http://www.rsdn.ru/File/21403/Overloads.pdf
Thanks for the article. It dropped me a thought of a way of improving my automatic transitions support in runtime.
Although, I still don't catch the point of creating/destroying state objects during transitions. This can even be inconvenient if a state is intended to be visited more than once.
-- Best regards, Andrey mailto:andysem@mail.ru
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost