April 2012 - Boost-users - lists.preview.boost.org

boost.multi_index & IPC
by 陈海峰 10 Apr '12

10 Apr '12

typedef managed_shared_memory::allocator<char>::type char_allocator; typedef basic_string<char, std::char_traits<char>, char_allocator>shm_string; struct quote { public: int market; int kind; shm_string seccode; shm_string secname; float price; float zf; quote(int market_, int kind_, const char* seccode_, const char_allocator& a, const char* secname_, const char_allocator& b, float price_, float zf_): market(market_),kind(kind_), seccode(seccode_, a), secname(secname_, b), price(price_), zf(zf_) {} }; typedef boost::multi_index::composite_key<quote, BOOST_MULTI_INDEX_MEMBER(quote, int, market), BOOST_MULTI_INDEX_MEMBER(quote, shm_string, seccode) >comp_key_search; typedef boost::multi_index::composite_key_compare< std::greater<int>, std::greater<shm_string> >comp_key_compare_search; typedef boost::multi_index::composite_key<quote, BOOST_MULTI_INDEX_MEMBER(quote, float, price), BOOST_MULTI_INDEX_MEMBER(quote, int, market), BOOST_MULTI_INDEX_MEMBER(quote, shm_string, seccode) >comp_key_sortbyprice; typedef boost::multi_index::composite_key_compare< std::greater<float>, std::greater<int>, std::greater<shm_string> >comp_key_compare_sortbyprice; typedef boost::multi_index::multi_index_container< quote, boost::multi_index::indexed_by< boost::multi_index::ordered_non_unique<comp_key_search, comp_key_compare_search>, boost::multi_index::ordered_non_unique<comp_key_sortbyprice, comp_key_compare_sortbyprice> >, managed_shared_memory::allocator<quote>::type >quote_mic; int main() { /* struct shm_remove { shm_remove() { shared_memory_object::remove("MySharedMemory"); } ~shm_remove(){ shared_memory_object::remove("MySharedMemory"); } } remover; */ managed_shared_memory segment(open_only,"MySharedMemory"); quote_mic *quotes = segment.find_or_construct<quote_mic> ("My MultiIndex Container") //Container's name in shared memory ( quote_mic::ctor_args_list(), //, segment.get_allocator<quote>()); //Ctor parameters quote_mic::allocator_type(segment.get_segment_manager())); quote_mic::nth_index<0>::type& idx_search = quotes->get<0>(); quote_mic::nth_index<1>::type& idx_sortbyprice = quotes->get<1>(); int count = 0; char_allocator ca1(segment.get_allocator<char>()); // 查询股票实时行情 shm_string seccode("600000", ca1); count = idx_search.count(boost::tuples::make_tuple(1, seccode)); quote_mic::nth_index<0>::type::iterator it = idx_search.find(boost::tuples::make_tuple(1, seccode)); for (int i=0; i<count; i++) { std::cout << it->seccode << std::endl; it++; } std::vector<quote> result; BOOST_FOREACH(const quote& q, idx_sortbyprice) { int kind = q.kind; if (kind == 1 || kind == 11) { // std::cout << "市场" << q.market << ",类别" << q.kind << ", " << q.secname << ",最新价" << q.price << std::endl; result.push_back(q); this statement will compile error, why? how to write? } else { // std::cout << "过滤：市场" << q.market << ",类别" << q.kind << ", " << q.secname << ",最新价" << q.price << std::endl; } } return 0; }

3 3

boost serialization skip a node
by ujoimro 10 Apr '12

10 Apr '12

Hello, I am working on a config file format, which is a collection of several xml "config file" classes. I would like to save them in a single file like this: oarchive << NVP(filters); oarchive << NVP(processor); oarchive << NVP(segmentation); However, it does make sense te use the "processor" class without the filters or the segmentation. Is there a simple way to skip some nodes in Boost.Serialization.XML? Or to refer to nodes by their name? iarchive >> NVP(processor); Thank You for Your help, LM

1 0

Including Boost 1.48.0 "qi.hpp" header file
by devika R S 10 Apr '12

10 Apr '12

Hi All, This post is regarding the issue we saw on IBM compiler using BOOST 1.48 version. Here is the sample code where we are trying to just include the header file "boost/spirit/include/qi.hpp>". *********************************Example Code************************************* #include <iostream> #include <boost/spirit/include/qi.hpp> main() { using namespace std; std::cout<<"test"<<"\n"; } *********************************END************************************************** When we compile this code on IBM with the compiler* : IBM XL C/C++ for AIX, V11.1 (5724-X13) Version: 11.01.0000.0000 *we end up with below error: xlC -I /usr/include/boost/1_48_0 -o dump test_prog.cpp - *xlC: 1501-230 (S) Internal compiler error; please contact your Service Representative. For more information visit:* - *http://www.ibm.com/support/docview.wss?uid=swg21110810* But this code works absolutely fine on g++ Linux. Looks like the inclusion of this header file on IBM platform is causing the issue. Is this is a known bug ?Is any patch available ? Thanks, Abc

2 1

problems with Boost.Thread on VS10
by John M. Dlugosz 10 Apr '12

10 Apr '12

I'm trying to use a packaged_task, and get an error on creation. template<typename R,typename F> struct task_object: task_base<R> { F f; task_object(F const& f_): // << refers to look here f(f_) {} #ifndef BOOST_NO_RVALUE_REFERENCES task_object(F&& f_): // <<<< Error here f(f_) {} E:\boost_1_49\boost/thread/future.hpp(1251): error C2535: 'boost::detail::task_object<R,F>::task_object(F)' : member function already defined or declared with [ R=size_t, F=std::tr1::_Bind<size_t,size_t,std::tr1::_Bind1<std::tr1::_Callable_fun<size_t (__cdecl *const )(std::string &),false>,const char *>> & ] E:\boost_1_49\boost/thread/future.hpp(1247) : see declaration of 'boost::detail::task_object<R,F>::task_object' with [ R=size_t, F=std::tr1::_Bind<size_t,size_t,std::tr1::_Bind1<std::tr1::_Callable_fun<size_t (__cdecl *const )(std::string &),false>,const char *>> & ] So I'm thinking that VS10 (Microsoft Visual Studio 2010) has problems overloading the constructor with (T const&) and (T&&) ? But shouldn't someone have noticed that long ago? Any ideas here? Thanks, —John

4 16

[Boost.Thread] unique_future without && ?
by John M. Dlugosz 09 Apr '12

09 Apr '12

My code needs to be compatible with a platform that doesn't have rvalue references available, for the time being. I've avoided explicit uses of move and made my && arguments fall back to const&. But I'm not sure about returning a unique_future. I see that unique_future<T> has a special move-the-guts type, with an implicit conversion operator and a constructor. But do I need to do anything special to declare a function returning one, and likewise the return statement itself? The code in packaged_task ( unique_future<R> packaged_task<R>::get_future() ) is not conditionally compiled based on BOOST_NO_RVALUE_REFERENCES, so I'm supposing that it just works by itself. Is that correct? But maybe it only works by itself in some cases? In that code, the return statement names a constructor directly. return unique_future<R>(task); In my code, I'm returning a unique_future that I already made somewhere else (actually, the result of another function call) so it would be wanting to call the copy constructor, I would think. So if I write unique_future<int> foo(); unique_future<int> bar() { return foo(); } what _should_ happen is that the existing value uses a user-defined conversion to construct the "copy", right? So I should expect this to work correctly if the thing I'm returning is already exactly the right type, as well as when naming the constructor directly. —John

3 8

split_iterator not working with a reference to const std::string
by asif saeed 09 Apr '12

09 Apr '12

Hi, Here is my code: struct CharIterator { CharIterator( const std::string &s, char_t const *delimiters) : s_(s), begin_(boost::algorithm::split_iterator<std::string::iterator>(s, boost::token_finder(boost::is_any_of(delimiters), boost::token_compress_off))), end_(boost::algorithm::split_iterator<std::string::iterator>()), i_(begin_) { } const std::string s_&; boost::algorithm::split_iterator<std::string::iterator> begin_, end_, i_; }; The compile gives me an error on parameter 1 of the above constructor. It compiles fine if I change "const std::string &s" to "std::string s" - that is, pass by value. I just want to store a reference to a string. Could you help me on this? Best regards, Asif

2 1

Clang "blocks" and function<>
by John M. Dlugosz 08 Apr '12

08 Apr '12

I wonder if there is anything already in Boost's implementation of the function template (that is exposed as std::tr1::function if you use Boost.TR1) that allows Clang's lambda-like "blocks" to be assigned to a function? Or, has anyone already fiddled with that and willing to share? —John reference: http://clang.llvm.org/docs/BlockLanguageSpec.txt

1 0

C++ Now! Early Bird Registration Ending Soon
by Jon Kalb 08 Apr '12

08 Apr '12

The fifteenth of this month is the end of Early Bird registration. Register by the end of next week to reserve your place and save on registration. Featuring 3 keynote speakers headlining 3 tracks of 50+ session brought to by 35+ presenters, this year¹s conference is our largest and most ambitious. What isn¹t bigger is the registration fee. If you beat the April 15th deadline you can enjoy the conference offering the most complete C++11 tutorial coverage of the year and save money too. See you in Aspen! Registration: http://cppnow.eventbrite.com/?ref=ecount Jon

1 0

mpl documentation question
by Robert Ramey 07 Apr '12

07 Apr '12

Documentation for mpl::less<T> has the following section: Expression semantics For any Integral Constants c1 and c2: typedef less<c1,c2>::type r; Return type:Integral Constant. Semantics:Equivalent to typedef bool_< (c1::value < c2::value) > r; typedef less<c1,c2> r; // a Return type:Integral Constant. Semantics:Equivalent to struct r : less<c1,c2>::type {}; //b if //a is used then the following yields bool_<true> is_same< less<c1, c2>, r> if // b is used then the following yields bool_<false> is_same< less<c1, c2>, r> So in what sense are //a and // b equivalent? Robert Ramey

3 6

Is boost::asio::io_service thread safety?
by 文凯 07 Apr '12

07 Apr '12

My code like this: #include <iostream> #include <map> #include <boost/asio.hpp> #include <boost/bind.hpp> #include <boost/thread.hpp> #include <boost/date_time/posix_time/posix_time.hpp> namespace ba = boost::asio; namespace bp = boost::posix_time; typedef std::map<int, ba::deadline_timer*> timer_map; timer_map g_timers; boost::mutex g_timers_lock; ba::io_service g_ios; void on_timer(int id) { { boost::mutex::scoped_lock lock(g_timers_lock); timer_map::iterator it = g_timers.find(id); assert(it != g_timers.end()); g_timers.erase(id); } // std::cout << "delete timer " << id << std::endl; } int main(void) { boost::thread trd(boost::bind(&ba::io_service::run, &g_ios)); trd.detach(); int count = 0; for (;;) { for (int i = 0; i < 100; i++) { ba::deadline_timer* pt = new ba::deadline_timer(g_ios, bp::seconds(1)); pt->async_wait(boost::bind(&on_timer, count)); boost::mutex::scoped_lock lock(g_timers_lock); g_timers.insert(std::make_pair(count++, pt)); } usleep(20000); } return 0; } ================================== I know, I should lock the g_timers, but should I lock the g_ios? I mean these lines: ba::deadline_timer* pt = new ba::deadline_timer(g_ios, bp::seconds(1)); pt->async_wait(boost::bind(&on_timer, count)); Are thread safety? It reference the g_ios, and will it call g_ios.add_job(this_timer) ..etc.. ? -- Cheers & KaiWen

2 1