- Boost - lists.boost.org

random and TR1
by Eric Niebler 24 Oct '07

24 Oct '07

I infer from the wrappers in tr1/random.hpp that Boost.Random is not TR1-compliant. What are the differences, and what is the plan for bringing Boost.Random into conformance? Also, are the wrappers in tr1/random.hpp TR1-compliant, or are there still some differences? Thanks, -- Eric Niebler Boost Consulting www.boost-consulting.com

2 1

[thread] build path names change
by Juergen Hunold 24 Oct '07

24 Oct '07

Hi Anthony ! The latest change to Boost.Thread: URL: http://svn.boost.org/trac/boost/changeset/40348 introduced "feature.feature thrd-api" as "symmetric" feature, adding "thrd-api-pthread" to the build paths on linux. I'd like to have it asymmetric, so build paths will be as short as possible. The problem with the "symmetric" property is that you can't use "feature.set-default" to change the default value so the path element will disappear. Please find "thread.diff" with propose patch attached. Also thread.txt with output without patch and thread2.txt will patched Jamfile.v2. The other thing I noticed is the usage of "os.name" to distinguish between nt/unix/cygwin. I think this should use "target-os" in order to enable cross-compilation, but I don't know how to code this. Therefore cross-post to Boost.Build list in order to get some pointer on how to change if [ os.name ] = NT to if target-os = windows or something similar. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! Ingenieurgesellschaft für * voice: ++49 511 262926 57 ! Verkehrs- und Eisenbahnwesen mbH * fax : ++49 511 262926 99 ! Lister Straße 15 * juergen.hunold(a)ivembh.de ! www.ivembh.de * * Geschäftsführer: ! Sitz des Unternehmens: Hannover * Prof. Dr.-Ing. Thomas Siefer ! Amtsgericht Hannover, HRB 56965 * PD Dr.-Ing. Alfons Radtke !

2 2

[thread] Failed assertions under Borland?
by John Maddock 24 Oct '07

24 Oct '07

I'm seeing new regex regressions caused by assertions being fired in Boost.Thread: http://tinyurl.com/2okqzn Any ideas? Thanks, John Maddock.

2 5

[1.35.0] Progress report
by Beman Dawes 24 Oct '07

24 Oct '07

Most of the bigger infrastructure issues that were getting in the way have now been solved. The tarballs are working again, the missing files in the release/branch have been found, and both trunk and release branch regression reporting is cycling smoothly. There are still some outstanding testing issues, but they are at the level of individual test platforms rather than the whole testing system. Both developers and patch submitters have been active, so it isn't like we are starting from scratch, but the emphasis for release management is shifting to focus on reducing test failures in individual libraries. Looking at the regression test results, I'd like to call attention to these failures: conversion: lexical_cast_loopback_test on many platforms graph: csr_graph_test on many platforms python: import_ on many platforms range: iterator_range and sub_range on many platforms typeof: experimental_* on many platforms These are particularly worrisome from the release management standpoint because they affect many platforms and because I'm not seeing any attempts to fix or markup by their developers. For many of the other failures that affect a lot of key platforms, the developers are actively committing fixes on a regular basis so I assume these failures will be fixed or marked up in the near future. I'll be traveling Thursday through Tuesday, and will start moving libraries to the release branch when I get back. --Beman

9 11

Boost.Test issues
by Vladimir Prus 24 Oct '07

24 Oct '07

Looking at program_options failures, it seems like two platforms are fully not working due to issues in Boost.Test. First is MIPS: http://tinyurl.com/3c8avh Second is Sun: http://tinyurl.com/2yjlpd Can those issues be fixed in near future? Thanks, Volodya

3 5

BGL: traveling sales man
by Michael Held 24 Oct '07

24 Oct '07

hi boost, is there any traveling salesman implementation in BGL available or is anything in this direction planned? I could need such an implementation and would like to volunteer to help implementing/porting such an algorithm. with the help of this community - of course ;-) thank you & cheers, michael

6 7

[fusion] Getting rid of the incomplete type error for vector
by Markus Schöpflin 23 Oct '07

23 Oct '07

Hello, a number of platforms fail when fusion vectors are used with an error message like this: cxx: Error: ../boost/fusion/sequence/conversion/detail/as_vector.hpp, line 41: incomplete type is not allowed (incompletetyp) return vector<>(); -------------------^ Removing the inclusion of boost/.../detail/as_vector.hpp in the header file boost/.../vector/vector.hpp (line 12) solves the issue for me. Could the fusion author please indicate if this is the right fix, and if yes, could this fix please be committed ASAP? TIA, Markus

5 8

boost::optional<T &>::get_ptr()
by Preston A. Elder 23 Oct '07

23 Oct '07

When was this made to NOT work? I am compiling an app against the CVS head of boost, because I want to use things like property_tree, and I don't plan on releasing my app before boost 1.35 is released anyway. But apparently, boost::optional<T&>::get_ptr() no longer works. Now instead I have to use if (myopt && &myopt.get() == &obj) instead of the terser: if (myopt.get_ptr() == &obj) I can't see anything about this in the dev list, and the docs on boost.org (which granted are for 1.34.1) still list get_ptr() as working for both optional<T> and optional<T&>. Preston

1 0

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

23 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 -

7 17

Exception late review
by Alexander Nasonov 23 Oct '07

23 Oct '07

I don't know if review manager still accepts reviews as review period is over but I'd like to share my ideas with others. I'm very interested in this library but I don't think that this version is good enough for inclusion into boost. As already pointed out by many people, library name is misleading. I'd expect from a library named Boost.exception that: - it provides functionality missing in std::exception (clone is one example), - it recommends deriving all boost exception classes from boost::exception and - wrapping standard exceptions with correspondent boost exceptions in boost::throw_exception. The library doesn't have enough features to cover problem domain or they are not well documented. Example shows how to attach additionaly information to FILE but it would be much better to demonstrate how information is added at each layer and then presented to end user. One example is RDBMS where some exception is raised at OS layer (e.g. file system full), then caught at db storage layer, rethown, then caught at higher layere up to SQL layer where it's nicely presented and send to a user. This case should cover tags associated with layers. Other important case is stacking up information as an exception is being processed. Stack trace is a good example. Also, it should be clear how library handle bad_alloc. In some situations, it's fine to rethrown bad_alloc instead of original exception but more fine tuned behavior is require in other situations. One example is stop adding info to a stack and just count all not added stack entries. Sorry for not very well detailed review and for being too late. I was hoping to find time and think thoroughly about interface but I couldn't find enough time. -- Alexander

2 3