* What is your evaluation of the design?
7 out of 10.
* What is your evaluation of the implementation?
8 out of 10.
* What is your evaluation of the documentation?
8 out of 10.
* What is your evaluation of the potential usefulness of the library?
10 out of 10.
* Did you try to use the library? With what compiler?
mingw, cygwin,  gcc, msvc visual studio 2005, and no.
* How much effort did you put into your evaluation?
A quick reading.
* Are you knowledgeable about the problem domain?
Hmm not really.

And finally, every review should answer this question:

* Do you think the library should be accepted as a Boost library?
I do not think it should be accepted, and my only small gripe with it its how the library is organize. Most boost library have "boost" as the top folder for organization of jam file and jam.v2...., when I used unordered library, unordered seems to be like the top folder structure...thats my only gripe. Its small but it destroys the uniformity of boost library".
Clearer words.. when you unzip boost library. boost is top level structure.
When you unzip unordered library, it is unordered --> boost --> unordered....
On Dec 7, 2007 2:05 AM, Ion Gaztaņaga <igaztanaga@gmail.com> wrote:
Hi all,

The formal review of the Unordered library, proposed by Daniel James,
begins today :

*Description*:

An implementation of the unordered containers specified in TR1, with
most of the changes from the recent draft standards.

*Author*:

Daniel James

*Download*:

http://www.boost-consulting.com/vault/index.php?action=downloadfile&filename=unordered.zip&directory=Containers

The documentation is in the zip file.  I've put documentation online here:

http://igaztanaga.drivehq.com/unordered

http://tinyurl.com/yw8wjp


What to include in Review Comments
==================================

Your comments may be brief or lengthy, but basically the Review Manager
needs your evaluation of the library. If you identify problems along
the way, please note if they are minor, serious, or showstoppers.

Here are some questions you might want to answer in your review:

* 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.

Unordered containers are likely to become one of the most used Boost
libraries so I encourage you to review the library in order to see if
Unordered fulfills all your expectations.

Ion Gaztaņaga
- Review Manager -
_______________________________________________
Boost-users mailing list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users