Just a friendly reminder that the ongoing Boost.Local review is officially set to end tomorrow (Saturday), Nov 19, 2011.
Please let me know if you plan on reviewing the library but need more time, possibly into early next week, and I'll either formally extend the review period (subject to the Review Wizards' approval) or simply informally allow late submissions.
Copied below is the original review announcement:
----------------
Hi all,
It is time!
The review of Lorenzo Caminiti's
proposed Boost.Local library begins tomorrow, ***November 10, 2011***,
and ends on ***November 19, 2011***.
Boost.Local implements local
functions, local blocks, and local exits for the C++ programming
language. It allows one to define a function at any declarative scope,
including function scope; bind variables from the enclosing scope; and
pass this function to templated STL-style algorithms.
Please see the Introduction of the documentation for a longer but still brief overview.
--------
The code and documentation are available from the Boost sandbox (https://svn.boost.org/svn/boost/sandbox/):
https://svn.boost.org/svn/boost/sandbox/local/ [everything]
https://svn.boost.org/svn/boost/sandbox/local/boost/ [code]
https://svn.boost.org/svn/boost/sandbox/local/libs/local/doc/html/index.html [documentation]
--------
Please state clearly whether you think this library should be accepted as a Boost library.
Other questions you may want to consider:
- 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?
Please also consider the following issues and proposals specific to
Boost.Local. Your opinion is welcome on any or all of these.
-
Boost.Local's local exits provide the same functionality (and then some)
as Boost.ScopeExit. Does this duplication of functionality need to be
dealt with, and if so, how?
- Lorenzo is proposing to add boost::local::function::