- Boost - lists.boost.org

[General] A standard idiom or technique?
by Robert Jones 24 Oct '08

24 Oct '08

A recent post in this list started me thinking... Given this code snippet, using namespace std; void f( int, int ); vector<int> v1; vector<int> v2; // populate... for ( unsigned i = 0; i <= v1.size( ); ++ i ) { f( v1[ i ], v2[ i ] ); } How would you write this as a for_each() or in some other Boosty, functional way? (The aspect I'm trying to highlight is that two iterators over different ranges must advance in step) One could imagine a tuple-based solution, in which one specifies how an operation applied to the tuple distributes to operations applied to each of the tuple's elements. Does any such thing exist in Boost? Is it ever necessary, or can the functionality be achieved by some C++/STL/Boost idiom that I've not thought of? If there is no obvious technique, is there any interest in a Boost library which address this in a generic way? Thanks. - Rob.

5 7

How to install Boost.Numeric.Bindings
by Peng Yu 24 Oct '08

24 Oct '08

Hi, I've downloaded the whole boost src. svn co https://svn.boost.org/svn/boost boost Right now, I need Boost.Numeric.Bindings which is in the sandbox. I tried bjam, but I got the following error. Can somebody let me know how to compile Boost.Numeric.Bindings? Thanks, Peng $ bjam Unable to load Boost.Build: could not find build system. --------------------------------------------------------- /home/local/eda06/yupeng/test/C++/svn/boost/sandbox/boost-build.jam attempted to load the build system by invoking 'boost-build ;' but we were unable to find "bootstrap.jam" in the specified directory or in BOOST_BUILD_PATH (searching /usr/share/boost-build). Please consult the documentation at 'http://www.boost.org'.

3 8

[Pool]: How to tag pool_allocator
by VoidEx 24 Oct '08

24 Oct '08

Hello pool_allocator based on singleton allocator, but uses it's own tag. But I want use one pool_allocator for some strings/vectors/lists and another for some other data, because I want destroy data separately. Is it possible now? Or may be I do it wrong?

2 2

[pool] Conversion to Boost.Thread for singleton_pool
by Chris Newbold 24 Oct '08

24 Oct '08

Boost.Pool contains a private mutex implementation used as the default mutex type for singleton_pool (which provides a thread-safe API). Now that Boost.Thread is well-established and in line with TR1, I'd like to jettison the private mutex implementation inside Boost.Pool and switch the default mutex type to be boost::mutex. The obvious consequence of this change is that singleton_pool becomes dependent on Boost.Thread. The dependency would exist only for singleton_pool and its clients and would not affect the other Boost.Pool interfaces. Anyone have any objections or reasons why this wouldn't be a good idea? -Chris

3 5

[Generator Iterator] [random]
by Andy Tompkins 24 Oct '08

24 Oct '08

I am trying to use boost::generator_iterator with a random number generator as follows: --- #include <boost/generator_iterator.hpp> #include <boost/random/mersenne_twister.hpp> class my_generator {...}; my_generator gen; boost::generator_iterator<my_generator> first(&gen); boost::generator_iterator<my_generator> last; boost::random::mt19937 rng; rng.seed(first, last); --- Sadly the default constructor of generator_iterator leaves m_gen uninitialized and the seed function is trying to compare first with last. I could pass gen to last, ie. boost::generator_iterator<my_generator> last(&gen), but then if ever begin has the same value as end, it will stop. The documentation for generator_iterator says that it models an input iterator, and I assume that an input iterator is ok to use with the seed function. I'm not sure what can/should be done. Thanks in advance, Andy.

2 3

[filesystem] file monitoring
by Carlos Rafael Giani 24 Oct '08

24 Oct '08

Hi, is a file monitor feature planned for boost.filesystem? I have been looking for a platform independent solution, but there is none (except in toolkits like Qt). Also, so far only inotify (a subsystem in the Linux kernel) can tell me when a file is closed after writing, which is absolutely necessary when watching a plugins/ directory, for example (you don't want to touch the plugins when they're only halfway copied). Several tools watch the plugin directory, but don't care if the plugins are being written or are fully there already. This can lead to instabilities. I think it is only logical to add this to boost.filesystem, something like set_monitor_callback(pathname, function_object); any thoughts?

10 11

[function] function.hpp lacks include guard
by Okko Willeboordse 24 Oct '08

24 Oct '08

Hello, My co-worker Bob Praster found, using PC-Lint 9.0, that function.hpp doesn't have an include guard like; #ifndef BOOST_FUNCTION_HPP #define BOOST_FUNCTION_HPP ... #endif // BOOST_FUNCTION_HPP Kind regards, Okko Willeboordse

12 17

[boost.org] people not updated?
by Thorsten Ottosen 24 Oct '08

24 Oct '08

Hi, It seems like we are missing some of our recent members. -Thorsten

4 3

[asio] HTTPS async_read() question
by Gregory Dai 24 Oct '08

24 Oct '08

I'm playing with the following SSL client example against an https site: http://www.boost.org/doc/libs/1_36_0/doc/html/boost_asio/example/ssl/client… I replaced std::cout << "Enter message: " with the part of the URL corresponding to an HTTP GET request, and changed the handle_read() to void handle_read(const boost::system::error_code& error, size_t bytes_transferred) { if (!error) { std::cout << "Reply: "; std::cout.write(reply_, bytes_transferred); std::cout << "\n"; boost::asio::async_read(socket_, boost::asio::buffer(reply_, bytes_transferred), boost::bind(&client::handle_read, this, boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred)); } else { std::cout << "Read failed: " << error << "\n"; } } so that it goes back to read more data. I'm able to get more than 20k data in response, but unable to reach the end of the data stream as the browser can. What could be a good reason for this behavior? Thanks, Greg

2 2

Re: [boost] [1.37.0][serialization] Assertion failed at libs/serialization/src/extended_type_info.cpp:92
by Hartmut Kaiser 24 Oct '08

24 Oct '08

Robert, Would it be possible to get an answer to my initial questions, please? Thanks! Regards Hartmut > Anything I can do about this? > What does this assertion mean? > > My setup: Linux 64Bit, gcc 4.2.4, serialization is used for polymorphic > objects loaded from different shared libraries, shared libraries are > loaded with dlopen(RTLD_GLOBAL|RTLD_LAZY). > > Assertion (extended_type_info.cpp:92) occurs during program termination > (after main returned), during dlclose(). > > If anything else isn't possible, would it be appropriate to change the > related code (before the release!) from: > > assert(start != end); > > // remove entry in map which corresponds to this type > do{ > if(this == *start) > x.erase(start++); > else > ++start; > }while(start != end); > > To: > > assert(start != end); > > // remove entry in map which corresponds to this type > while(start != end) { > if(this == *start) > x.erase(start++); > else > ++start; > } > > Which wouldn't remove the problem, but at least avoids hanging the > program if assertions are off... > > Regards Hartmut

3 6