- Boost - lists.boost.org

[1.39.0] New libraries?
by Beman Dawes 11 Mar '09

11 Mar '09

Are there any new libraries that will be ready to go into the 1.39.0 release? Thanks, --Beman

3 8

[Review] RangeEx review extended to the 10th of March
by Thorsten Ottosen 11 Mar '09

11 Mar '09

Dear Developers and Users, The review period is extended one week. If you find this library interesting, please submit a review. The discussion so far may be found here: http://archives.free.net.ph/message/20090220.122836.73bdbd04.en.html Below you will find a description of the library and information on how to write a review. best regards Thorsten, review manager What is it? +++++++++++ The library provide two very useful extensions to the range library 1. Range-based algorithms. E.g. boost::sort( rng ); which is a convenient wrapper of instead of std::sort( boost::begin(rng), boost::end(rng) ); But the new interface also allows for more expressive code because (on the fly) composition of algorithms suddenly is possible. 2. Range adaptors. E.g. std::vector<int> vec = ...; boost::copy( vec | boost::adaptors::reversed, std::ostream_iterator<int>( std::cout ) ); where the expression "vec | boost::adaptors::reversed" wraps the iterators of the range on the left in reverse iterators. The library provides a wide range (no pun intended) of Range adaptors, and they are a powerful way to create ranges on the fly and pass them to algorithms. Getting the library +++++++++++++++++++ The library may be downloaded from http://www.cs.aau.dk/~nesotto/boost/range_ex.zip or from the Boost vault under "Algorithms". The docs may be browsed online here http://www.cs.aau.dk/~nesotto/boost/libs/range/ Please note that the documentation is integrated with the current Range ilbrary. Therefore the relevant sections for the review is http://www.cs.aau.dk/~nesotto/boost/libs/range/doc/adaptors.html and http://www.cs.aau.dk/~nesotto/boost/libs/range/doc/algorithms.html The code may be browsed here: http://www.cs.aau.dk/~nesotto/boost/boost/range/ Notice the library is header only (exception: the adaptor tokenized() depends on Boost.Regex). Writing a review ++++++++++++++++ If you feel this is an interesting library, then please submit your review to the developer list (preferably), or to the review manager. 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. Special considerations ++++++++++++++++++++++ Various RangeEx like libraries have been implemented in the past. You might want to compare with those libraries when you form your oppinion: 1. John Torjo's range lib http://rangelib.synesis.com.au/libs/boost-rangelib-20040913.zip http://torjo.com/rangelib/index.html 2. Adobe's ASL libraries include range-based algorithms: http://stlab.adobe.com/group__algorithm.html I'm looking forward to your review. best regards Thorsten, Review Manager

2 1

RangeEx review
by Mathias Gaunard 10 Mar '09

10 Mar '09

Here is a quick review of RangeEx. > - Do you think the library should be accepted as a Boost library? Yes, assuming issues raised in the recent discussions are addressed, and that people agree on the naming. > - What is your evaluation of the design? It is nice and pretty. Here are a few comments: - I am unsure about the syntax of the unified return type system. It's very practical, however, but not so pretty. - Fusion of the function syntax and pipe syntax for adaptors would be useful, so that both range | transformed(f) and transformed(range, f) may be written. - Relying on standard algorithms means that the functors have to provide a result_type. I would like the functors to be automatically wrapped so that boost::result_of can be used instead. I don't know if Boost.Iterator needs it too. - In the sandbox version, find(range) used to call range.find() if range had a find member (the has_find meta-function had a poor implementation, but that could have been solved). I don't know why this feature was removed, but I personally liked that better. - I would like to library to also provide lazy range generators, potentially defining an infinite range recursively. - Adaptors for type filtering within heterogeneous sequences (sequences of "potentially smart" pointers, sequences of variants, sequences of any...) would also be a plus. It's basically a filter+transform at the same time. I found such an adaptor primitive very practical when dealing with trees, for example. > - What is your evaluation of the implementation? It seems good. It's mostly just forwarding things to standard algorithms or Boost.Iterator for adaptors, nothing much to say. > - What is your evaluation of the documentation? Simple, but doesn't necessarily need to be more complicated. > - What is your evaluation of the potential usefulness of the library? Huge. I deal with sequences (or ranges) of objects everyday, and being able to express operations directly on them would make my code simpler and clearer. > - Did you try to use the library? With what compiler? Did you have any problems? I used an old version from the sandbox, with a few custom modifications, less than a year ago to code some experimental proof-of-concept C++ wrapper over a hierarchical thread scheduler written in C (a component which mapped trees of tasks to trees of processors) so as to see how it could make the code more high-level. This was done with GCC 4.2. I didn't have problems except making it work with a lambda DSEL (I actually cheated and used typeof for return type deduction everywhere at the time). > - How much effort did you put into your evaluation? A glance? A quick - reading? In-depth study? I only quickly read the documentation and gave a glance at the version under review; but I did study the sandbox version more in-depth. > - Are you knowledgeable about the problem domain? I know about ranges, iterators, functional programming, and lazy sequences fairly well.

2 1

Help needed with some Math lib failures
by John Maddock 10 Mar '09

10 Mar '09

Folks, There are a few failures from Boost.Math (for example http://tinyurl.com/clvlq3) which I'm unable to reproduce locally - it seems only certain (possibly AMD x86-64 machines running Linux or *BSD) exhibit the problem. I can provide a test case to help with debugging what's going on, but I need to find someone who can reproduce the issue first. So... if you think you can help, then cd into libs/math/test and do a: bjam gcc test_hypergeometric_dist0 test_hypergeometric_dist1 test_hypergeometric_dist2 test_hypergeometric_dist3 test_hypergeometric_dist4 test_hypergeometric_dist5 and if one or more fail then let me know the failure message and I'll put together a test case. Many thanks in advance! John.

2 2

Request for interest in the new Synchro library
by vicente.botet 10 Mar '09

10 Mar '09

Hi, I would like to know if the Boost community is interested in the Synchro library. Of course there is a lot of work to do, but I think that there is enough material to start a discussion on the approach. I'd appreciate it if people could take a look, test it on their compiler and give me some feedback. The library is available at Boost Sandbox: https://svn.boost.org/svn/boost/sandbox/synchro and Boost Vault: http://www.boostpro.com/vault/index.php?action=downloadfile&filename=synchr… that iIncludes every thing on the Sandbox + Html documentation Some examples use Boost.Interthreads also (available on the vault and the sandbox). This library is a compilation of what I have found in the literature not yet present in Boost. My main concern has been to boostify all these ideas in a coherent way. Next follows an overview of the library features: Boost.Synchro provides: * A uniform usage of Boost.Thread and Boost.Interprocess synchronization mechanisms based on lockables(mutexes) concepts and locker(guards) concepts. o lockables traits and lock generators, o lock adapters of the Boost.Thread and Boost.Interprocess lockable models, o locker adapters of the Boost.Thread and Boost.Interprocess lockers models, o complete them with the corresponding models for single-threaded programs: null_mutex and null_condition classes, o locking families, o semaphore, o condition_lockable lock which put together a lock and its associated conditions. * A coherent exception based timed lock approach, * A rich palette of lockers as o strict_locker, nested_strict_locker, o condition_locker, o reverse_locker, nested_reverse_locker, o locking_ptr, on_dereference_locking_ptr, o externally_locked, * A polymorphic lockable hierarchy. * High-level abstractions for handling more complicated synchronization problems, including o monitor for guaranteeing exclusive access to an object, and o a so-called rendezvous mechanism for handling direct communication between objects concurrent_components via ports using an accept-synchronize protocol based on the design of the concurrency library in the Beta language. On going work * array_locker and tuple_locker locker containers. * A complement to the already present in Boost.Thread lock, try_lock free functions: o lock_until, lock_for, try_lock_until, try_lock_for Best regrads, Vicente Juan Botet Escribá

3 12

[random] Speed up binomial and poisson distributions
by Stephan 10 Mar '09

10 Mar '09

Hi, I was wondering why the binomial distribution still isn't optimized for speed. If I look into the GSL as a comparison, they use much smarter and faster algorithms. As is, the bosst::random distributions are not usable for computational purposes to me, which is a pity since I very much like the approach using variate_generators and stuff... I would be happy to contribute some faster code, but I don't know how exactly I should proceed for that... should I contact the maintainer directly? Stephan

5 7

[threadpool] version 22 with default pool
by k-oli＠gmx.de 09 Mar '09

09 Mar '09

I've uploaded a new version of boost-threadpool. changes: * free-function get_default_pool() returning reference to static pool< unbounded_channel< fifo > > * task has new function result() returning the internal shared_future * future-like functions removed from task * boost-threadpool not a header-only library Oliver

5 26

[Asio] Starting/stopping chat_server externally
by Tres Spicher 09 Mar '09

09 Mar '09

Hi all, I am hoping someone who is an expert on Boost.Asio can help me by analyzing my modifications to the chat_server example. I have adjusted the example to closely resemble an application I am developing that uses the example as its inspiration. Important differences between my version and the official version include: 1) chat_room supports clearing the set of participants, and the destructor for participants closes the corresponding socket 2) chat_server supports a start and a stop operation from another thread 3) The io_service is managed by the chat_server object instead of the main function I would like to know if my usage is correct, particularly for the start/stop operations. I would like the stop operation to put the chat_server into the same state it was in on construction, so that the start operation semantics are identical whether the chat_server is newly constructed or has already been stopped. I am concerned about memory leaks or uncaught exceptions, and anything else that a seasoned user of the library would notice that I may have missed. The code can be found here: http://pastie.org/412088 Thanks in advance! Tres -- Tres Spicher Boulder Labs tres(a)boulderlabs.com

1 0

Re: [boost] [Python] GSoC and Python 3.0 Support
by OvermindDL1 09 Mar '09

09 Mar '09

> I'm a student who has finished SWIG's Python 3.0 support in GSoC 2008. > If Boost will participate in this year's Summer of Code, I'd like to > contribute my knowledge of Python 3 migration to Boost.Python, by > implement Python 3.0 support for it. Finally the users of Boost.Python > would get 3.0 support smoothly. Is that worth for a GSoC project? Any > interesting? I would be very pleased if you did this. I had done some minor edits myself, but have no chance for a good half year at least until I could dedicate some time to it, and if you did it then you would both get paid and save me a lot of time. Do note, adding Py3k support also involves changing the python version testing in the build scripts, I already have that part done if I can find it somewhere...

1 0

Can i do serialization on "wchar_t *"
by Selvaraj Kannan 09 Mar '09

09 Mar '09

Hi, I am getting the following error, while compile. I am using Boost 1.32 Version on Mac OS 10.5. --------- > g++ -I/usr/local/include/boost-1_32/ -L/usr/local/lib/ -lboost_wserialization Test.cpp /usr/local/include/boost-1_32/boost/serialization/access.hpp:106: error: request for member 'serialize' in 't', which is of non-class type 'wchar_t' /usr/local/include/boost-1_32/boost/serialization/access.hpp: In static member function 'static void boost::serialization::access::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::binary_wiarchive, T = wchar_t]': /usr/local/include/boost-1_32/boost/serialization/serialization.hpp:78: instantiated from 'void boost::serialization::serialize(Archive&, T&, unsigned int) [with Archive = boost::archive::binary_wiarchive, T = wchar_t]' /usr/local/include/boost-1_32/boost/serialization/serialization.hpp:121: instantiated from 'void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::binary_wiarchive, T = wchar_t]' /usr/local/include/boost-1_32/boost/archive/detail/iserializer.hpp:155: instantiated from 'void boost::archive::detail::iserializer<Archive, T>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const [with Archive = boost::archive::binary_wiarchive, T = wchar_t]' Test.cpp:27: instantiated from here /usr/local/include/boost-1_32/boost/serialization/access.hpp:106: error: request for member 'serialize' in 't', which is of non-class type 'wchar_t' -------- Can someone help me solving this issue. regards S.Kannan

2 1