September 2006 - Boost-announce - lists.stage.boost.cppalliance.org

BoostCon 2007 Call for Proposals
by Beman Dawes 30 Sep '06

30 Sep '06

The first annual Boost conference will take place in Aspen, Colorado, May 14-18, 2007. BoostCon 2007 is looking for session presenters. We invite you to propose a session. For details on how to become a presenter, see www.boost.org/more/BoostCon07_session_call.html This inaugural Boost conference promises to be the main face-to-face venue for all things Boost, from using libraries to writing them, from evangelizing Boost to deployment within your organization, from infrastructure and process to vision and mission, and from TR1 to TR2. Given the range and interests of the participants, the event is going to be intense and in-depth. For more information about the conference, see www.boost.org/more/BoostCon07.html --The Organizing Committee David Abrahams Beman Dawes Jeff Garland Joel de Guzman Kevlin Henney Howard Hinnant Scott Meyers Eric Niebler Sean Parent Rene Rivera Jeremy Siek Matthias Troyer

1 0

Boost.MPI accepted
by Jeremy Siek 21 Sep '06

21 Sep '06

It is my pleasure to announce that Boost.MPI has been accepted as a Boost library. Congratulations to Doug Gregor and Matthias Troyer on their excellent contribution to Boost! One particularly nice aspect of Boost.MPI is the way it leverages the Boost serialization library. So also thanks to the author of that library, Robert Ramey. Yeah generic programming and code reuse! I would also like to thank all of the people that took some time to review Boost.MPI and participate in the review discussion: Dean Michael Berris, Robert Ramey, David Abrahams, Geoffrey Irving, John Fletcher, John Phillips, and Noel Belcourt. During the review, several suggestions for improvement were made, which I recommend that the authors take action on as they prepare Boost.MPI to be included in Boost. 1. Named parameters in the interface 2. Revise introduction to focus more on describing what Boost.MPI is, and move info about how Boost.MPI is implemented to a later section. 3. Document the performance characteristics of functions, e.g., Create_vector. 4. A copy-edit pass over the docs to catch typos, etc. 5. Hooks for dispatching between the underlying MPI implementation vs. a Boost.MPI provided impl. Cheers, Jeremy __________________________________ Jeremy Siek <siek(a)cs.colorado.edu> http://www.cs.colorado.edu/~siek/ Visiting Assistant Professor Department of Computer Science University of Colorado at Boulder

1 0

Fwd: [boost] [Review][MPI] Boost.MPI review begins
by Ronald Garcia 07 Sep '06

07 Sep '06

Begin forwarded message: > From: Jeremy Graham Siek <jsiek(a)osl.iu.edu> > Date: September 6, 2006 3:16:06 PM EDT > To: Boost mailing list <boost(a)lists.boost.org>, Boost Announce > <boost-announce(a)lists.boost.org> > Subject: [boost] [Review][MPI] Boost.MPI review begins > Reply-To: boost(a)lists.boost.org > > Hi All, > > The view of the Boost.MPI (for Message Passing Interface) begins > today, Sept. 6 and continues through Sept. 15. > > Description: > > The Message Passing Interface (MPI) is a standard interface for > message > passing in high-performance parallel applications. It defines a > library > interface, available from C, Fortran, and C++, for which there are > many > MPI implementations. Although there exist C++ bindings for MPI, they > offer little functionality over the C bindings. The Boost.MPI library > provides an alternative C++ interface to MPI that better supports > modern C++ development styles, including complete support for user- > defined > data types and C++ Standard Library types, arbitrary function objects > for > colective algorithms, and the use of modern C++ library techniques to > maintain maximal efficiency. As an example, one can concatenate the > std::strings stored on each processor with a single reduce call and > the function object std::plus<std::string>. However, if the call to > reduce is merely computing the sum of integers, the implementation > transforms into the appropriate call to MPI_Reduce. For more > information > about the design of Boost.MPI, see our design philosophy. > > The review tarball is here: > > http://www.generic-programming.org/~dgregor/boost.mpi/boost- > mpi-20060906.tgz > > Online documentation is available here: > > http://www.generic-programming.org/~dgregor/boost.mpi/libs/ > parallel/doc/html/ > > PDF documentation is available here: > > http://www.generic-programming.org/~dgregor/boost.mpi/mpi.pdf > > > Review questions > ================ > > Please always explicitly state in your review, whether you think the > library should be accepted into Boost. > > You might want to comment on the following questions: > > - 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? > > Cheers, > Jeremy > > __________________________________ > Jeremy Siek <siek(a)cs.colorado.edu> > Visiting Assistant Professor > Department of Computer Science > University of Colorado at Boulder > > > > > _______________________________________________ > Unsubscribe & other changes: http://lists.boost.org/mailman/ > listinfo.cgi/boost

1 0