On Fri, Mar 4, 2011 at 3:39 PM, Ronald Garcia
Review Wizard Status Report for March 2011 ============================================== ... Review Schedule ===============
* Fiber (M) * Context
``(M)`` marks libraries that need review managers.
--------------------
Fiber ----- :Author: Oliver Kowalke
:Review Manager: Needed
:Download: `Boost Vault < http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost.fiber-0.3.7.zip&directory=Concurrent%20Programming& ;>`__
:Description: C++ Library for launching fibers (micro-threads) and synchronizing data between the fibers.
Link should apparently be: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost.fiber-0.9.2.zip&directory=Concurrent%20Programming& The stated link is broken in a couple ways. Context
------- :Author: Oliver Kowalke :Review Manager: Vicente Botet
:Download: `Boost Vault < http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost.context-0.1.0.zip&directory=Concurrent%20Programming& ;>`__
Similarly, this should apparently be: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost.context-0.6.7.zip&directory=Concurrent%20Programming&
:Description: Context provides the ability to switch between different user-level context and is intended to be the basis for a higher abstraction like coroutine and fiber.
A user-level context represents the current execution state, including all registers and CPU flags, the instruction pointer, the stack pointer. boost::context encapsulates such a user-level context and is able to store/restore its associated user-level context. This allows multiple execution paths running on a single thread using a sort of cooperative scheduling (in contrast a thread is preemptively scheduled) - the running boost::context decides explicitly when its yields to allow another boost::context to run (user-level context switching). A context can only run on a single thread at any point in time but may be migrated between thread.