June 2005 - Boost - lists.boost.org

RE: [boost] Re: meta-double
by Martin Bonner 09 Jun '05

09 Jun '05

> Rob Stewart <stewart(a)sig.com> writes: >> AFAIK, the only thing you can say about the size of int is that >> it must handle the INT_MIN to INT_MAX range on a given platform >> and the only thing you can say about short is that it is no >> bigger than int and at least one byte. >> Have I missed something that requires both to be at least 16 >> bits? David Abrahams <dave(a)boost-consulting.com> writes: > Yes. That's a bit gnomic. What you have missed Rob is that the standard requires SHRT_MIN <= -32767 and SHRT_MAX >= 32767. That implies short must have at least 16 bits. There is a similar requirement on long that means it must be at least 32 bits. -- Martin Bonner Martin.Bonner(a)Pitechnology.com Pi Technology, Milton Hall, Ely Road, Milton, Cambridge, CB4 6WZ, ENGLAND Tel: +44 (0)1223 441434

4 3

Announcement: Library-Centric Software Design (LCSD 05)
by jarvi 09 Jun '05

09 Jun '05

The following call for papers should be of interest to many in the Boost community. For more information, see http://lcsd05.cs.tamu.edu Posting the announcement has been approved by Boost moderators. Best, Jaakko Järvi ----------------------------------------------------------------------- LIBRARY-CENTRIC SOFTWARE DESIGN - LCSD'05 Workshop, on Sunday, October 16, 2005 at the Object-Oriented Programming, Systems, Languages and Applications (OOPSLA'05) conference in San Diego, California, October 16-20, 2005 CALL FOR PAPERS Libraries are central to all major scientific, engineering, and business areas, yet the design, implementation, and use of libraries are underdeveloped arts. This workshop is one of the first steps in the process of placing all aspects of libraries on a sound technical and scientific basis through research into fundamental issues and documentation of best practices. A software library is an organized collection of code with associated tools supporting programming in general or in specific domains, usually united by a specified set of principles and conventions. Most libraries are aimed at the use by several people and in different environments. The areas of software library research include * Design and implementation of libraries * Program and system design based on libraries * Libraries supporting specific application domains, such as biology and banking * Evolution, refactoring, and maintenance of libraries * Empirical studies of library use * Performance of libraries, including benchmarking and library-based optimizations * Design of language facilities and tools in support of library definition and use * Validation, debugging, and testing of libraries * Extensibility, parameterization, and customization * Distribution of libraries * Specification of libraries and their semantics * Usability for library users and developers * Assessing quality of libraries * Documentation and teaching of libraries * Creating and supporting communities of library users * Using several libraries in combination We invite the submission of extended abstracts on software library research, including, but not limited to, the above list of topics. The extended abstracts should address issues important to libraries as a field, i.e., describe ideas or techniques that can be reused for libraries across problem domains and/or languages; they should refrain from merely describing a particular library, no matter how novel the choice of domain. As an additional criterion, the extended abstracts are reviewed against suitability for a journal publication of the corresponding full paper. For uniformity, authors should use the latest ACM SIGS conference style file (option 1) at http://www.acm.org/sigs/pubs/proceed/template.html. Submissions should be limited to 10 pages in this style. Accepted extended abstracts will be posted on the workshop's Web site prior to the workshop, and collected in a proceedings published as a Rensselaer Polytechnic Institute tech report. Authors of selected papers will be invited to submit a full paper for a special issue of a journal, to be announced later. IMPORTANT DATES Jul 31 Submission of extended abstracts Sep 9 Notification of acceptance Oct 4 Final version posted on workshop Web site Oct 16 Workshop SUBMISSION PROCEDURE For details of the electronic submission procedure, see the workshop's Web site, http://lcsd05.cs.tamu.edu. ORGANIZERS * David Musser, Rensselaer Polytechnic Institute * Andrew Lumsdaine, Indiana University * Jaakko Jarvi, Texas A&M University * Sibylle Schupp, Chalmers University of Technology * Todd Veldhuizen, Indiana University * Jeremy Siek, Rice University Primarily, the email address lcsd05(a)cs.tamu.edu should be used for questions addressed to the organizers. PROGRAM COMMITTEE Not yet finalized, but the following are confirmed: * Uwe Assmann, Technical University of Dresden * Matt Austern, Google Inc. * Herve Broennimann, Polytechnic University * Antonio Cisternino, University of Pisa * Jack Dongarra, University of Tennessee * Ulrich Eisenecker, University of Leipzig * Calvin Lin, University of Texas at Austin * Alex Stepanov, Adobe Systems Inc. * Bjarne Stroustrup, Texas A&M and AT&T Labs * Frank Tip, IBM Research In addition, the organizers will serve as program committee members. WORKSHOP GOALS AND ACTIVITIES The workshop establishes a scientific forum for presenting original research in the design, implementation, and evaluation of software libraries. Other major activities include the identification of open questions specific to library research and the discussion of a strategic plan for establishing library research as a field. The outcome of the workshop is a combination of research contributions and specific next steps for improving the infrastructure for library research. Participants are expected to read the accepted submissions beforehand. The technical presentations, although based on the accepted papers, should not provide mere summaries of the papers. Instead, authors are encouraged to use their presentation slots (20 + 10 mins) to bring up topics for discussion. The technical presentations are mixed with scientific and organizational discussions. The discussions aim at furthering the topics of the presentations, thus their agenda will be publicly discussed among the participants and then posted on the website of the workshop. All participants are expected to come prepared with their tentative answers or thoughts. The full-day workshop starts with a keynote talk for the stimulation of discussion and concludes with a plenary discussion that decides the specific next steps for improving the infrastructure for library research. FOR MORE INFORMATION AND UPDATES please visit the workshop's Web site, http://lcsd05.cs.tamu.edu. _______________________________________________

1 0

[ann]Fast_lookup - first snapshot available
by Mikhail Glushenkov 09 Jun '05

09 Jun '05

First snapshot of the to-be proposed Fast_lookup library is available for download at the vault. Direct link (watch for line breaks!): http://boost-sandbox.sourceforge.net/vault/index.php?&order= &directory=fast_lookup Sorry, no documentation as of yet. Fast_lookup provides "sorted vector"-based versions of standard associative containers, thus embracing the common practice. Highlights of this release: * map and set have been implemented * Two different storage policies - 'default' and KeepKeysSeparate, which is usually faster, but takes more memory * Out-of-the-box support for Boost.Serialization I haven't done any significant optimizations yet, but the performance tests are in, and they show that we are in pretty good shape(compared to Loki::AssocVector). Fast_lookup currently does not work on vc6 though I've made some initial stabs at this problem. Since I'm going on vacation starting from this Friday, the next snapshot will likely be posted in August. Planned features include multiset and multimap + indirect storage(some parts of pointer_containers library will be probably reused) Any suggestions, comments, feature requests or critique are welcome.

4 7

share_ptr serialization
by Robert Ramey 09 Jun '05

09 Jun '05

In the course if making a new shared_ptr seriailzation implementation, I've come upon a question. If a shared pointer has been created with a custome deleter, how is one to determine what kind of deleter is attached without opening the implementation of shared_ptr? That is, I see no way to correctly serialize/deserialize a shared_ptr with a custom deleter from the published interface of shared_ptr. Can anyone explain how to do this? Robert Ramey

3 2

[1.33.0] Timeline and remaining issues
by Douglas Gregor 09 Jun '05

09 Jun '05

I want to be rolling prerelease tarballs by next Friday, June 10th, and hope to release 1.33.0 shortly thereafter. To get there, I need your help. We've just brought the "Unresolved issues" page back online at: http://engineering.meta-comm.com/boost-regression/CVS-HEAD/developer/ issues.html This reflects all of the bugs that we need fixed or accounted for before we release Boost 1.33.0. The page itself has some flaws that we are aware of (and will work on), but please verify that your libraries don't have any entries on this page. Click on the name of the library to see the full set of results for the compilers important for this release. Focus on those compilers; ask me first before making changes to accommodate other compilers. We're...almost...there. Doug

7 11

Bug-Report.
by Juan Antonio Gálvez Gamboa 09 Jun '05

09 Jun '05

Greetings to everyone. It seems there´s a bug when using the astar_search.hpp in the dummie property map section. namespace detail { template <class VertexListGraph, class AStarHeuristic, class CostMap, class DistanceMap, class WeightMap, class IndexMap, class ColorMap, class Params> inline void astar_dispatch2 (VertexListGraph& g, typename graph_traits<VertexListGraph>::vertex_descriptor s, AStarHeuristic h, CostMap cost, DistanceMap distance, WeightMap weight, IndexMap index_map, ColorMap color, const Params& params) { dummy_property_map p_map; typedef typename property_traits<CostMap>::value_type C; astar_search (g, s, h, choose_param(get_param(params, graph_visitor), make_astar_visitor(null_visitor())), choose_param(get_param(params, vertex_predecessor), p_map), cost, distance, weight, index_map, color, choose_param(get_param(params, distance_compare_t()), std::less<C>()), choose_param(get_param(params, distance_combine_t()), closed_plus<C>()), choose_param(get_param(params, distance_inf_t()), std::numeric_limits<C>::max()), choose_param(get_param(params, distance_zero_t()), C())); } I´m using Visual C++ .NET 2003 and it seems it´s getting a confusion between: std::numeric_limits<C>::max()) and a macro called max, defined somewhere, whose body would be: #define max(((a)>(b))?(a):(b)) I got the definition of this macro pointing with the mouse cursor over the "max" word on std::numeric_limits<C>::max()) .Before trying to use the astar_search() function, in the copilements always a warning telling "not enough parameters for the macro max" has appeared (that´s logic if it´s interpreted as a macro -where are paseed the two parameters?-) but the questions is... it´s necessary to be interpreted as the "max" numeric_limit. I´m not sure if this is an atar_search bug but, in case it´s not and ,so that, I have a "max" macro defined, any suggestions where should I fin it for modifying it´s name to MAX or directly deleted from the header file?. Thanks for your time... ______________________________________________ Renovamos el Correo Yahoo! Nuevos servicios, más seguridad http://correo.yahoo.es

2 1

Re: Who's Using Boost?
by Jeffrey Williams 09 Jun '05

09 Jun '05

Hi boosters, We use boost too, here is my "report". Application: Rule in Hell Company: Megahard Software Technologies Inc. Description of Application: Massively Multiplayer Online Role Playing Game (still in beta) Boost libs used: bind function any tuples ref shared_ptr type_traits noncopyable By *FAR* the combination of bind, function,shared_ptr and ref is what we use most heavily. As time goes on we tend to replace our custom code with boost libs that perform more or less the same functionality (where it makes sense) url: http://www.ruleinhell.com

1 0

[parameter] missing docs?
by Joaquín Mª López Muñoz 09 Jun '05

09 Jun '05

Are the docs for Boost.Parameter already into the CVS? I cannot seem to find them. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo

2 1

[filesystem] error codes revisited
by Beman Dawes 09 Jun '05

09 Jun '05

Peter Dimov suggested that Boost.Filesystem's error reporting codes use the POSIX <cerrno>/<errno.h> codes as the portable way to encode errors. That made a lot of sense for POSIX systems, and since POSIX is now an ISO standard (ISO/IEC 9945:2002), other portions of Boost.Filesystem are also as of the i18n branch being formally defined by reference to the ISO POSIX standard. Checking how the various standards interrelate as far as errno.h, cerrno, and errno definitions are concerned, the C++ and POSIX standards both defer to the C standard, although POSIX does add additional codes. No problems there. As far as actual header implementations go, there was a concern that the Windows errno.h implementations didn't provide the needed definitions (since C only mandates EDOM, EILSEQ, and ERANGE). That turned out to be a non-problem. The Windows implementations only provide a subset of the POSIX macros, but with few exceptions they do provide all the macros Boost.Filesystem users will need. One exception was that Borland fails to define one of the needed macros. There were also two cases where additional non-POSIX macros were needed, but the standards do permit extensions, so again no problem. That has been worked around by providing a <boost/filesystem/cerrno.hpp> header which sucks in <cerrno> and adds any needed definitions. I had some concerns about Boost.Filesystem headers gratuitously including <cerrno> (or <boost/filesystem/cerrno.hpp>) because that could cause macro name clashes. But it turned out the Boost.Filesystem headers have no reason to include <cerrno> or <boost/filesystem/cerrno.hpp>. So no problem. The CVS filesystem i18n branch now has the POSIX aligned error mechanisms in place. Seems to work well and be a very nice improvement to the library. Thanks to Peter for the suggestion! --Beman

1 0

[boost][date_time] errors in time_facet.hpp (cvs HEAD)
by Jan Hermelink 09 Jun '05

09 Jun '05

I think there are several errors in time_facet.hpp from cvs HEAD: The lines using std::basic_string::find() evaluate the return code wrongly, e.g. line 227: if (format.find(seconds_with_fractional_seconds_format)) { should be if (format.find(seconds_with_fractional_seconds_format) != string_type::npos) { I think. In addition I think "%%" should always evaluate to "%" and leave the following char unexpanded. Current e.g. "%%s" evaluates to "%59.000000", not to "%s". This is the outcome of using boost::algorithm::replace_all(). Otherwise thank you for your great library! Jan

2 1