Boost logo

Boost Announcement :

From: Martin Vuille (martin_at_[hidden])
Date: 2008-08-20 11:52:38

By request, the formal review for Andrey Semashev's Finite
State Machines (FSM) library has been extended and will run
until August 27th.

This is your last chance to submit a review and cast your
vote for or against inclusion of this library into Boost.

The documentation (overview and reference) is available online:

The current submission is available from the sandbox vault at (or
if you prefer.)


"The main goals of the library are:

* Simplicity. It should be very simple to create state machine
  using this library.
* Performance. The state machine infrastructure should not be very
  time and memory-consuming in order to be applicable in more use
* Extensibility. A developer may want to add more states to the
  existing state machine, and this addition should be relatively
  safe since it shouldn't interfere with the existing states. The
  developer should also be able to specify additional transitions
  and events for the machine with minimum modifications to the
  existing code."

"Boost.FSM vs. Boost.Statechart

There is another library in Boost that provides similar functionality:
Boost.Statechart. Although it currently covers almost all major Boost.FSM
features and provides ones that are not supported in this library,
Boost.Statechart is more targeted to creation of big and complex state
machines with possibility of distributed development. But this does not
come at no price and Statechart has little tools for compile-time
and does not provide as much run-time performance as Boost.FSM does. So
there are main guidelines for users to make a decision between Boost.FSM
and Boost.Statechart: [...]"

"The following compilers are known to have problems or most likely
will have ones:

* Microsoft Visual C++ 6.0 and 7.0. Most probably will fail to
  compile due to lack of partial template specialization support.
* Borland C++ Builder 5.5.1 (free version). Fails to compile due
  to lack of partial template specialization and in-class using
  declarations support. Some other minor problems also have been
  noticed. Newer versions of the compiler have not been tested.
* OpenWatcom 1.5. Fails to compile due to problems with Boost.MPL
  code. Newer versions of the compiler have not been tested.
* SunPro C++ Compiler 5.5 for Solaris (SPARC). Most likely will
  show problems with function overload resolution. Newer versions
  of the compiler have not been tested."

The current submission is available from the sandbox vault at (or
if you prefer.)

What to include in Review Comments

Your comments may be brief or lengthy, but basically the Review Manager
needs your evaluation of the library. If you identify problems along
the way, please note if they are minor, serious, or showstoppers.

Here are some questions you might want to answer in your review:

What is your evaluation of the design?
What is your evaluation of the implementation?
What is your evaluation of the documentation?
What is your evaluation of the potential usefulness of the library?
Did you try to use the library? With what compiler? Did you have any
How much effort did you put into your evaluation? A glance? A quick reading?
In-depth study?
Are you knowledgeable about the problem domain?

And, finally, every review should answer this question:

Do you think the library should be accepted as a Boost library? Be sure to
this explicitly so that your other comments don't obscure your overall

Thanks in advance for your participation in this review.


Boost-announce list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at