[boost] [Review] Fixed Strings library

From: Hartmut Kaiser (hartmut.kaiser_at_[hidden])
Date: 2006-01-23 19:52:12

Hi all,

this is just a reminder for all interested people to possibly submit a
review for the Fixed Strings library written by Reece Dunn.

The review is half over and the response we've got by now is far from
sufficient to allow to make a proper judgement. So please try to find some
time and write about your findings here.

Please find the original announcement below.

Regards Hartmut
Review Manager

---------------------------------

Hi all,

The review of the proposed Boost Fixed Strings library written by Reece Dunn
starts today (January 19th, 2006) and ends January 28th, 2006.

You can download the library here: http://tinyurl.com/czrh9
(http://boost-consulting.com/vault/index.php?action=downloadfile&filename=fi
xed_string.zip&directory=Strings%20-%20Text%20Processing&)

---------------------------------------------------
About the library:

The fixed_strings library is a buffer-overrun safe version of using
fixed-size character array data buffers. It provides integration with the C
API allowing strcpy, et. al. to be used safely for a fixed string and
provides a basic_string interface allowing easy migration to C++ strings. 
There is also a formatter function object allowing (w)sprintf to be used in
a single line!

Example:
   boost::fixed_string< 5 > hi;
   strcpy( hi, "Hello World" );
   hi.push_back( '!' );
   std::cout << hi << std::endl;
   std::cout << boost::formatter( "Meine %s Welt!", "kleine" ) << std::endl;

output:
   Hello
   Meine kleine Welt!

---------------------------------------------------

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?