We need review manager volunteers for most of the libraries
in the review queue. If your interested, let us know by
replying to this thread. Preferably, you would have a
background in the problem domain, a regular contributer to the
boost mailing list, but no association with the
library. Some of the libraries have been waiting
patiently for a volunteer for some time now.
The review schedule is available here:
http://www.boost.org/more/formal_review_schedule.html .
You can read the "review manager"
requirements at the following link:
http://www.boost.org/more/formal_review_process.htm
Most of the libraries are located at the Boost Sandbox Vault,
located here:
http://boost-consulting.com/vault/
Maintainers of the Review Queue:
Ronald Garcia (garcia (at) cs.indiana.edu )
Tom Brinkman (reportbase (at) gmail.com)
If there is any errors or ommisions in this report,
please send them to Ron or Tom.
Here is a summary of the libraries that are in the queue.
-------------------------------------
Library: Exception
Author: Emil Dotchevski
Location: http://www.revergestudios.com/boost-exception/boost-exception.zip
Review Manager: Needed
Date: Needed
Summary:
The purpose of Boost Exception is to free designers of
exception classes from having to consider what data needs to
be stored in exception objects in order for the catch site to
be able to make sense of what went wrong. When Boost Exception
is used, arbitrary values can be stored in any exception. This can be
done directly in the throw-expression, or at a later time as the
exception object propagates up the call stack. The ability to add
data to any exception object after it has been thrown is important,
because often some of the information needed to handle an
exception is unavailable at the time of the throw.
-----------------------------------------
Library: Scope Exit
Author: Alexander Nasonov
Location: Boost Sandbox Vault
Review Manager: Needed
Date: Needed
Summary:
The scope-exit-arg-pp-seq is Boot.Preprocessor sequence
of identifiers that can be used inside scope-exit-body.
The direct-declarator is declarator-id followed by optional
argument of type boost::scope_exit_group (inside brackets or
after the equal sign). This construct executes scope-exit-body
at the close of the current scope.
-----------------------------------------
Library: Finite State Machines
Author: Andrey Semashev
Location: Boost Sandbox Vault
Review Manager: Martin Vuille
Date: Needed
Summary:
The Boost.FSM library is an implementation of FSM
(stands for Finite State Machine) programming concept.
There are many cases when a developer would like to distinguish the
behavior of a given object depending on some conditions or its
internal state. For example, when making software to control
an underground charging tourniquiet a programmer would like to
separate states in which the tourniquiet may persist: an idle state,
when the device awaits for another passenger that would like to
pass; a processing state, when the passenger have come
and put his ticket into the device; and the passing state,
when the tourniquiet lets the passenger pass through. In
fact, each state describes different reaction of the machine
at the same events (a passenger may only pass after paying
for ticket). Obviously, the tourniquiet have to be able to
change its internal state in order to function properly,
this is called state switching or transitions between
states (or just transitions for short).
-----------------------------------
Library: Floating Point Utilities
Author: Johan Råde
Location: Boost Sandbox Vault
http://boost-consulting.com/vault/index.php?directory=Math%20-%20Numerics
Review Manager: Needed
Date: Needed
Summary:
Proposed Additions to the Boost Math Library