- Boost-announce - lists.boost.org

[review] Boost.Functional/Forward - result
by John Torjo 12 Dec '07

12 Dec '07

Hi all, I'm happy to announce that The Boost.Functional/Forward library has been accepted into Boost. Congrats to Tobias for a great lib! Summary: 5 reviews, all positive. Suggestions for improvement: - Automatically detect if the compiler supports variadic templates and rvalue references and use those instead. This can be a useful portability utility when such compilers become more common. - It should use compressed_pair to store the wrapped function object to take advantage of EBO. - more tweakable parameters for specific uses - like, arity 3 for function X, and arity 5 for function Y - Docs: add more material explaining the forwarding problem - Docs: should be explicitly specified that the wrapped function object must be result_of compatible - Docs: A discussion of the impact of the library on compile time (especially with high values of N) Best, John -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

1 0

[review] Review of Unordered library begins today December 7
by Ion Gaztañaga 07 Dec '07

07 Dec '07

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&filenam… 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 -

1 0

[review] Fast track formal review of Forward library begins today
by John Torjo 04 Dec '07

04 Dec '07

Hi all, The formal review of the Boost.Functional/Forward library, proposed by Tobias Schwinger, begins today : Boost.Functional/Forward provides decorator function objects to have an n-ary, generic function object accept both RValues and mutable LValues. An exponential number of overloads is needed with C98, so redundant solutions are highly undesirable. Functional/Forward is a reusable implementation asking to live in a central place in Boost. Download it from here: http://www.boost-consulting.com/vault/index.php?action=downloadfile&filenam… http://www.boost-consulting.com/vault/index.php?&direction=0&order=&directo… The documentation is included in the .zip file, in the usual place: forward/libs/functional/forward/doc/html/index.html 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. We're looking forward to your evaluation of this Boost candidate! John Torjo - Review Manager - -- http://John.Torjo.com -- C++ expert ... call me only if you want things done right

1 1

[unordered] Remainder: Unordered review will start December 7
by Ion Gaztañaga 03 Dec '07

03 Dec '07

Hi to all, We have several reviews on December and just between two fast-track reviews, Unordered library will be reviewed December 7-16. For those interested in the library: *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&filenam… The documentation is in the zip file. Regards, Ion

1 0

[boost] [review] Exception - result
by Tobias Schwinger 07 Nov '07

07 Nov '07

I'm pleased to announce that the Exception library has been accepted into boost. Thanks to all formal and informal reviewers and to Emil Dotchevski for the library! Summary of possible improvements: ================================= Design ------ Nearly all reviewers made suggestions for syntactic improvements. The "tag(value) syntax" (as suggested by John Torjo) for instance provides sufficient syntactic sugar and seems lightweight to implement. Suggested features in this area are (those are implementable on top of the current design - but will keep users from reinventing the wheel if provided by the library): - Support for grouping information, and - support for generating stack traces. I personally still have a bad feeling about 'enable_error_info' - let's just revisit and discuss it on the list before changing boost::throw_exception. The related discussions about clone/rethrow support is still ongoing. Documentation ------------- Best practices for the catch-site should be clarified in the documentation. Same goes for using the same tag multiple types with one exception object. Other comments should be addressed (I won't put much energy into summarizing documentation comments, guessing most of them might have been taken care of, already). Deployment ---------- There was a suggestion (from Pavel Vozenilek) to put #ifdef around the code of boost::exception that could be put into a separate translation unit. There should probably also be a 'build' directory and a Jamfile so there is smooth integration with the Boost build system. Of course, Jamfiles for test/examples should be added. Implementation -------------- Several reviewers noted that the library is rather allocation-heavy. It pretty much comes down to shared_ptr overuse (causing many unnecessary allocations of small objects and synchronized instructions to be executed) though not in performance critical code possibly affecting other threads and future allocations. -- Tobias Schwinger - Review Manager - _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/ listinfo.cgi/boost

1 0

[review] Exception - review period extended
by Tobias Schwinger 12 Oct '07

12 Oct '07

The review period of the proposed Exception library has been extended until October 20th. Although several people seemed interested in the submission, we only have two votes, so far. So we really need more votes. Further, I'm concerned about some potential issues, which I wouldn't want to bless into Boost without being sure there has been a thorough investigation (see below). So, I want to encourage you to evaluate the submission, in particular regarding the following questions: 1. Should the library be accepted as a Boost library? For a guideline on what to include in your evaluation see http://www.boost.org/more/formal_review_process.htm 2. Is the design of the 'enable_error_info' function (see http://www.revergestudios.com/boost-exception/boost-exception.htm#existing_… and http://www.revergestudios.com/boost-exception/boost-exception.htm#enable_er… ), using multiple inheritance, really sound? 3. Does the current implementation use appropriate data structures? We are looking forward to your reviews! Regards, Tobias Schwinger - Review Manager -

1 0

[review] Review of Exception begins today
by Tobias Schwinger 27 Sep '07

27 Sep '07

The formal review of the Exception library, proposed by Emil Dotchevski, begins today. The library provides an exception class that can transport arbitrary values, thus freeing the user from designing custom exception classes. The library can be downloaded at http://tinyurl.com/24wtwu and its documentation can be read online at http://tinyurl.com/2bkojl . 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. We're looking forward to your evaluation of this Boost candidate! Tobias Schwinger - Review Manager -

1 0

Review wizard's report for October 2007
by Ronald Garcia 14 Sep '07

14 Sep '07

============================================ Review Wizard Status Report for October 2007 ============================================ News ==== August 17, 2007 -- Time Series Accepted. Announcement: http://lists.boost.org/boost-announce/2007/08/0142.php July 24, 2007 -- Boost Version 1.34.1 Released. This is a bug fix release addressing many problems with the 1.34.0 release. Announcement: http://svn.boost.org/trac/boost/query? status=closed&milestone=Boost+1.34.1 We need experienced review managers. Please take a look at the list of libraries in need of managers and check out their descriptions. In general review managers are active boost participants or library contributors. If you can serve as review manager for any of them, email Ron Garcia or John Phillips, "garcia at cs dot indiana dot edu" and "jphillip at capital dot edu" respectively. A link to this report will be posted to www.boost.org. If you would like us to make any modifications or additions to this report before we do that, please email Ron or John. If you're library author and plan on submitting a library for review in the next 3-6 months, send Ron or John a short description of your library and we'll add it to the Libraries Under Construction below. We know that there are many libraries that are near completion, but we have hard time keeping track all of them. Please keep us informed about your progress. Review Queue ============ * Exception * Finite State Machines * Floating Point Utilities * Switch * Property Map (fast-track) * Graph (fast-track) -------------------- Exception --------- :Author: Emil Dotchevski :Review Manager: Need Volunteer :Download: http://www.revergestudios.com/boost-exception/boost-exception.zip :Description: The purpose of this library is to free designers of exception classes from having to consider what data needs to be stored in exception objects in order for the catch site to be able to make sense of what went wrong. When the exception class is used, arbitrary values can be stored in any exception. This can be done directly in the throw-expression, or at a later time as the exception object propagates up the call stack. The ability to add data to any exception object after it has been thrown is important, because often some of the information needed to handle an exception is unavailable at the time of the throw. Finite State Machines --------------------- :Author: Andrey Semashev :Review Manager: Martin Vuille :Download: `Boost Sandbox Vault <http://tinyurl.com/yjozfn>`__ :Description: The Boost.FSM library is an implementation of FSM (stands for Finite State Machine) programming concept. The main goals of the library are: * Simplicity. It should be very simple to create state machines using this library. * Performance. The state machine infrastructure should not be very time and memory-consuming in order to be applicable in more use cases. * Extensibility. A developer may want to add more states to an existing state machine. A developer should also be able to specify additional transitions and events for the machine with minimum modifications to the existing code. Floating Point Utilities ------------------------ :Author: Johan Råde :Review Manager: Need Volunteer :Download: `Boost Sandbox Vault <http://boost-consulting.com/vault/ index.php?directory=Math%20-%20Numerics>`__ :Description: The Floating Point Utilities library contains the following: * Floating point number classification functions: fpclassify, isfinite, isinf, isnan, isnormal (Follows TR1) * Sign bit functions: signbit, copysign, changesign (Follows TR1) * Facets that format and parse infinity and NaN according to the C99 standard. (These can be used for portable handling of infinity and NaN in text streams.) Switch ------ :Author: Steven Watanabe :Review Manager: Need Volunteer :Download: `Boost Sandbox Vault <http://boost-consulting.com/vault/ index.php? action=downloadfile&filename=mcs_units_v0.7.1.zip&directory=Units>`__ :Description: The built in C/C++ switch statement is very efficient. Unfortunately, unlike a chained if/else construct there is no easy way to use it when the number of cases depends on a template parameter. The Switch library addresses this issue. Property Map (fast-track) ------------------------- :Author: Andrew Sutton :Review Manager: Jeremy Siek :Download: http://svn.boost.org/svn/boost/sandbox/graph-v2 :Description: A number of additions and modifications to the Property Map Library, including: * A constant-valued property map, useful for naturally unweighted graphs. * A noop-writing property map, useful when you have to provide an argument, but just don't care about the output. * See `ChangeLog <http://svn.boost.org/trac/boost/browser/sandbox/graph- v2/libs/property_map/ChangeLog>`__ for details. Graph (fast-track) ------------------ :Author: Andrew Sutton :Review Manager: Jeremy Siek :Download: http://svn.boost.org/svn/boost/sandbox/graph-v2 :Description: A number of additions and modifications to the Graph Library, including: * Two new graph classes (undirected and directed) which are intended to make the library more approachable for new developers * A suite of graph measures including degree and closeness centrality, mean geodesic distance, eccentricity, and clustering coefficients. * An algorithm for visiting all cycles in a directed graph (Tiernan's from 1970ish). It works for undirected graphs too, but reports cycles twice (one for each direction). * An algorithm for visiting all the cliques a graph (Bron&Kerbosch). Works for both directed and undirected. * Derived graph measures radius and diameter (from eccentricity) and girth and circumference (from Tiernan), and clique number (from Bron&Kerbosch). * An exterior_property class that helps hides some of the weirdness with exterior properties. * runtime and compile-time tests for the new algorithms. * a substantial amount of documentation * Graph cores, implemented by David Gleich (@Stanford University) * Deterministic graph generators - capable of creating or inducing specific types of graphs over a vertex set (e.g., star graph, wheel graph, prism graph, etc). There are several other specific types that could be added to this, but I haven't had the time just yet. Libraries under development =========================== Please let us know of any libraries you are currently developing that you intend to submit for review.

1 0

ScopeExit Review ends tomorrow (Wednesday)
by Jody Hagins 21 Aug '07

21 Aug '07

The ScopeExit review ends on Wednesday, August 22. If you want to have input on its acceptance into Boost, please provide a review by tomorrow. BTW, we need more input ;-) Thanks! >From the original announcement... The review period for Scope Exit Time Series, submitted by Alexander Nasonov, runs from Monday, August 13 until Wednesday, August 22. >From the documentation: Nowadays, every C++ developer is familiar with RAII technique. It binds resource acquisition and release to initialization and destruction of a variable that holds the resource. But there are times when writing a special class for such variable is not worth the effort. This is when ScopeExit macro comes into play. You put resource acquisition directly in your code and next to it you write a code that releases the resource. Note that ScopeExit uses PP macros and relies on Boost.Typeof. The latest version can is here: http://boost-consulting.com/vault/index.php?action=downloadfile&filename=sc… It's available also at http://tinyurl.com/2z6qg2 Online documentation is here: http://194.6.223.221/~nasonov/scope_exit-0.04/libs/scope_exit/doc/html/inde… >From the review guidelines here: http://boost.org/more/formal_review_process.htm ... Boost mailing list members are encouraged to submit Formal Review comments: * Publicly on the mailing list. * Privately to the Review Manager. Private comments to a library submitter may be helpful to her or him, but won't help the Review Manager reach a decision, so the other forms are preferred. 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. Thanks in advance to every for your participation in this review. _______________________________________________ Boost-users mailing list Boost-users(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Looking for ScopeExit Reviews
by Jody Hagins 19 Aug '07

19 Aug '07

The review ends in three days (on Wednesday). The current collection of reviews is very small, thus I am asking for more reviews of this library. Thanks! >From the original announcement... The review period for Scope Exit Time Series, submitted by Alexander Nasonov, runs from Monday, August 13 until Wednesday, August 22. >From the documentation: Nowadays, every C++ developer is familiar with RAII technique. It binds resource acquisition and release to initialization and destruction of a variable that holds the resource. But there are times when writing a special class for such variable is not worth the effort. This is when ScopeExit macro comes into play. You put resource acquisition directly in your code and next to it you write a code that releases the resource. Note that ScopeExit uses PP macros and relies on Boost.Typeof. The latest version can is here: http://boost-consulting.com/vault/index.php?action=downloadfile&filename=sc… It's available also at http://tinyurl.com/2z6qg2 Online documentation is here: http://194.6.223.221/~nasonov/scope_exit-0.04/libs/scope_exit/doc/html/inde… >From the review guidelines here: http://boost.org/more/formal_review_process.htm ... Boost mailing list members are encouraged to submit Formal Review comments: * Publicly on the mailing list. * Privately to the Review Manager. Private comments to a library submitter may be helpful to her or him, but won't help the Review Manager reach a decision, so the other forms are preferred. 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. Thanks in advance to every for your participation in this review.

1 0