August 2009 - Boost - lists.preview.boost.org

Request for feedback - Map providing insertion order preserving iteration
by Gautam Sewani 24 Aug '09

24 Aug '09

Hi, We wanted to add a map to Boost C++ libraries which would allow iteration in the order in which elements were inserted, and would also provide logarithmic time retrieval. A simple design for this would be to have a balanced binary tree along with an auxiliary linked list of pointers to the keys in the tree. We would be grateful if you could provide feedback on the utility and design. Regards Gautam Sewani Satyam Shekhar

2 1

[signals2] How to build docs?
by John Maddock 24 Aug '09

24 Aug '09

I'm looking into building PDF versions of the docs for 1.40 and I'm having trouble building the signals2 docs. For example if I cd into libs/signals2/doc and build from there, then the XML code snippets aren't found. Likewise if I build as a dependency from doc/pdf. Any ideas? Thanks, John.

3 7

Re: [boost] [C++-sig] [Boost.Python] Request to merge some patches from trunk into 1.40 branch (was: Re: PySide has been released)
by Stefan Seefeld 24 Aug '09

24 Aug '09

Anderson, let me forward that mail to the main boost list, and ping Beman (release manager) and David (boost.python maintainer). Beman, David, if it's not too late, I may help merge trunk to the release branch. Let me know... Stefan On 08/21/2009 08:08 AM, Anderson Lizardo wrote: > I think it was not clear in the announcement, but PySide uses Boost.Python. > > And for it to work properly, we need a few patches that are already in > Boost SVN trunk, but in none of the release branches. > > Therefore, is it possible to get these patches merged into the 1.40 > release branch before the final release? That would make life a lot > easier for other distros to try PySide without requiring to apply > patches separately. > > The relevant commits are listed in http://www.pyside.org/downloads/, they are: > > Add generic call operator support. > https://svn.boost.org/trac/boost/changeset/47846 > Support C++ enums which have the same value. > https://svn.boost.org/trac/boost/changeset/53660 > Fix unsigned integer converters. > https://svn.boost.org/trac/boost/changeset/54919 > Fix unsigned integer converters (update). > https://svn.boost.org/trac/boost/changeset/54923 > > IMHO these patches fix important bugs in Boost.Python, and the first > two were in trunk even before the 1.39 release, but were never > merged... > > Thanks in advance, > -- ...ich hab' noch einen Koffer in Berlin...

3 2

[Boost.Python] Request to merge some commits from trunk into 1.40 branch
by Anderson Lizardo 24 Aug '09

24 Aug '09

[I accidentally sent this e-mail to the C++-sig mailing list, please don't consider it a cross-post] As announced on the C++-sig mailing list, PySide was released: www.pyside.org. I think it was not clear in the announcement, but PySide uses Boost.Python. And for it to work properly, we need a few patches that are already in Boost SVN trunk, but in none of the release branches. Therefore, is it possible to get these patches merged into the 1.40 release branch before the final release? That would make life a lot easier for other distros to try PySide without requiring to apply patches separately. The relevant commits are listed in http://www.pyside.org/downloads/, they are: Add generic call operator support: https://svn.boost.org/trac/boost/changeset/47846 Support C++ enums which have the same value: https://svn.boost.org/trac/boost/changeset/53660 Fix unsigned integer converters: https://svn.boost.org/trac/boost/changeset/54919 Fix unsigned integer converters (update): https://svn.boost.org/trac/boost/changeset/54923 I think these patches fix important bugs in Boost.Python, and the first two were in trunk even before the 1.39 release, but were never merged... Thanks in advance, -- Anderson Lizardo OpenBossa Labs - INdT Manaus - Brazil

2 1

[persistence] interface overview
by Stefan Strasser 24 Aug '09

24 Aug '09

A while ago, I proposed a persistence library and there was some interest. Since then, the prototype has evolved into a feature-complete, reasonably optimized, implementation. Here's a quick recap of what the library is supposed to do: --------- int main(){ ... shared_ptr<A> shared(new A); db_ptr<A> db(new A); ... } // "shared" is destroyed, "db" is saved to disk to ensure data consistency, there are transactions introduced: transaction tx; //change_objects tx.commit(); if change_objects throws an exception, causing tx to be destroyed without commit() being called, all changes are undone. --------- there is no complete documentation yet, but I've written an overview of the library interface, which can be found here: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=overvi… I'd appreciate your comments. please note the "open issues" section.

4 5

[unordered] allocators and EBO
by Thorsten Ottosen 24 Aug '09

24 Aug '09

Hi James, (Sorry I called you Jeremy in the other post). When the allocator is empty, you should avoid storing them as members in different internal structures, and make the allcator a base class of some of these structures. Thanks -Thorsten

2 2

[mpl] patch for non-typeof map::insert
by Steven Watanabe 24 Aug '09

24 Aug '09

AMDG mpl::map insert can fail after an erase, because it uses size instead of order to determine the next order. The patch https://svn.boost.org/trac/boost/attachment/ticket/2042/insert_impl.hpp.pat… fixes this. Okay to commit? In Christ, Steven Watanabe

3 3

bjam - help please
by Edward Grace 23 Aug '09

23 Aug '09

Since I'm trying to Boostify (is that a legitimate word now? - heck you can verb anything these days) my code, I decided to try bjam: Gulp, having been weaned on automake and fiends [sic] it looks like it should be easy enough, but I've fallen at the first hurdle: In Jamroot: using gcc : 4.4 : g++-4 ; exe example_basic : example_basic.cpp : <include>. ; The <include>. line, as I understand it will mean the #include <blah> that I use will pick up stuff in the same directory as the source file (this seems ok). My problem is the link stage, $ bjam example_basic ...found 53 targets... ...updating 1 target... gcc.link bin/gcc-4.4/debug/example_basic /usr/bin/ld: unknown flag: --start-group collect2: ld returned 1 exit status "g++-4" -o "bin/gcc-4.4/debug/example_basic" -Wl,--start- group "bin/gcc-4.4/debug/example_basic.o" -Wl,-Bstatic -Wl,- Bdynamic -Wl,--end-group -g ...failed gcc.link bin/gcc-4.4/debug/example_basic... I've no idea where all this --start-group stuff comes from -- never seen it before. Any ideas? -ed ------------------------------------------------ "No more boom and bust." -- Dr. J. G. Brown, 1997

2 6

regex/ICU fix
by Vladimir Prus 23 Aug '09

23 Aug '09

As reported previously, --build-type=complete does not work if ICU is also configured. The below patch makes build process suppress building static Boost.Regex in this case. The wording is as follows: ghost@wind:~/Work/Boost/boost-svn$ bjam link=static runtime-link=static --with-regex .... warning: when using ICU, Boost.Regex must be a dynamic library warning: forcing link=shared runtime-link=shared for Boost.Regex Note: Building Boost.Regex with Unicode/ICU support enabled Using ICU in /usr/include Note that the warning is printed before the message that we're using ICU, which is ugly, but what I have is a minimal change. I'll tweak those configuration messages for 1.41. Comments? Ok for release branch? - Volodya

3 13

[1.40] PDB fix merge
by Vladimir Prus 23 Aug '09

23 Aug '09

Steven Watanabe has recently reported that a bug in Boost.Build caused boost libraries to be rebuilt when bjam is invoked again after a successful build. This affects msvc. I've just now reproduced and fixed this on trunk: https://svn.boost.org/trac/boost/changeset/55717 Since this fairly annoying behaviour, I would like to merge it to release branch. OK? I'd expect at least on trunk msvc tester to cycle shortly, so I should be able to merge tomorrow morning. Thanks, Volodya

3 3