[boost] [Review] Formal review of Boost.Convert library starts Saturday

Subject: [boost] [Review] Formal review of Boost.Convert library starts Saturday
From: Edward Diener (eldiener_at_[hidden])
Date: 2011-04-21 10:24:48

This is a reminder that formal review of the Boost.Convert library by 
Vladimir Batov starts on Saturday, April 23, and is scheduled to last 
through May 2.

***************
* Its Purpose *
***************

 From the introduction:

Boost.Convert builds on the boost::lexical_cast experience and still 
offers a simple, minimal interface, familiar conversion behavior and more:

     * throwing and non-throwing behavior when conversion fails;
     * support for the default/fallback value to be returned when 
conversion fails;
     * two types of the conversion-failure check - basic/simple and 
better/safe;
     * formatting support based on the standard std::streams and 
std::stream-based manipulators (like std::hex, std::scientific, etc.);
     * support for different locales;
     * support for boost::range-compliant char and wchar_t-based string 
containers (std::string, std::wstring, char const*, wchar_t const*, char 
array[], etc.);
     * no DefaultConstructibility requirement for the Target/Destination 
type;
     * extendibility and additional room to grow.

*******************
* Where to get it *
*******************

You can find the Boost.Convert here:

http://www.boostpro.com/vault/index.php?action=downloadfile&filename=boost-string-convert.zip

     The HTML documentation is part of the distribution and can be found 
at libs/convert/index.html in the distribution above.

********************
* Writing a review *
********************

The reviews and all comments should be submitted to the developers list,
and the email should have "[convert] Review" at the beginning of the 
subject line to make sure it's not missed.

Please explicitly state in your review whether the library should be
accepted.

The general review checklist:

     - 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?

And finally, every review should answer this question:

     - Do you think the library should be accepted as a Boost library?

Be sure to say this explicitly so that your other comments don't
obscure your overall opinion.

Edward Diener,
Review Manager