[Boost-announce] FW: [Review] Coroutine review starts today, September 3rd, ends September 12th

Subject: [Boost-announce] FW: [Review] Coroutine review starts today, September 3rd, ends September 12th
From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2012-09-11 10:42:49

This is just a reminder that the review of Oliver's Boost.Coroutine is
ending tomorrow (see below for the initial announcement). Please get your
reviews in as soon as possible. If you need more time, please let me know.

Regards Hartmut
---------------
http://boost-spirit.com
http://stellar.cct.lsu.edu

> -----Original Message-----
> From: Hartmut Kaiser [mailto:hartmut.kaiser_at_[hidden]]
> Sent: Monday, September 03, 2012 6:46 AM
> To: 'boost-announce_at_[hidden]'
> Subject: {Review] Coroutine reviewstarts today, September 3rd
> 
> 
> Hi all,
> 
> The review of Oliver Kowalke's Boost.Coroutine library starts today,
> September 3rd 2012, and will end on September 12th.
> I really hope to see your vote and your participation in the discussions
> on the Boost mailing lists!
> 
> -----------------------------------------------------
> 
> About the library:
> 
> Boost.Coroutine provides templates for generalized subroutines
> (coroutines) which allow multiple entry points for suspending and resuming
> execution at certain locations. It preserves local state/data and allows
> re-entering subroutines more than once (useful if state must be kept
> across function calls). Coroutines can be viewed as a language-level
> construct providing a special kind of control flow.
> 
> You can download the library and the view documentation here:
> 
> docs: http://ok73.ok.funpic.de/boost/libs/coroutine/doc/html/
> src: http://ok73.ok.funpic.de/boost.coroutine.zip
> 
> ---------------------------------------------------
> 
> Please always state in your review, whether you think the library should
> be accepted as a Boost library!
> 
> Additionally please consider giving feedback on the following general
> topics:
> 
> - 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
> problems?
> - How much effort did you put into your evaluation? A glance? A quick
> reading? In-depth study?
> - Are you knowledgeable about the problem domain?
> 
> Regards Hartmut
> Review Manager