- Boost-users - lists.boost.org

use boost preprocessor to generate T1 t1, T2 t2 ...
by weiqingh 27 Oct '12

27 Oct '12

hi there, I would like to use boost preprocessor to generate something like this: (for n from 0 to N with n = 2 in the following example) template <typename T1, typename T2> void foo(T1 t1, T2 t2) I have tried to use BOOST_PP_ENUM_PARAMS but cannot figure out how to get both T_i and t_i changed each time. is there some other macros I can use? any help is highly appreciated. Thanks, -- View this message in context: http://boost.2283326.n4.nabble.com/use-boost-preprocessor-to-generate-T1-t1… Sent from the Boost - Users mailing list archive at Nabble.com.

5 5

Re: [Boost-users] [boost] Fwd: Re: [system] symbol visibility and GCC vs. Clang
by Michel Morin 26 Oct '12

26 Oct '12

Fixed in r81068. Since dllexport/dllimport are not fully supported on clang (see http://llvm.org/bugs/show_bug.cgi?id=11170 ), I didn't add the macros (BOOST_SYMBOL_EXPORT/BOOST_SYMBOL_IMPORT) for the Windows platform. Regards, Michel

1 0

[unique_ptr] How should I assign unique_ptr returned from a factory function, possibly using boost::move, in C++03
by Adam Romanek 26 Oct '12

26 Oct '12

Hi, the question is: how should I assign boost::interprocess::unique_ptr returned from a factory function, possibly using boost::move, in C++03? Here's an example: --- #include <boost/interprocess/smart_ptr/unique_ptr.hpp> using namespace boost::interprocess; class my_class { public: my_class() {} }; struct my_class_deleter { void operator()(my_class *p) {} }; typedef unique_ptr<my_class, my_class_deleter> uptr; uptr create() { return uptr(); } int main() { uptr x; x = create(); // return 0; } --- The problem is that gcc fails to compile the above code saying: main.cpp:22: error: ambiguous overload for ‘operator=’ in ‘x = create()()’ ../../boost_latest/boost/interprocess/smart_ptr/unique_ptr.hpp:211: note: candidates are: boost::interprocess::unique_ptr<T, D>& boost::interprocess::unique_ptr<T, D>::operator=(boost::rv<boost::interprocess::unique_ptr<T, D> >&) [with T = my_class, D = my_class_deleter] ../../boost_latest/boost/interprocess/smart_ptr/unique_ptr.hpp:249: note: boost::interprocess::unique_ptr<T, D>& boost::interprocess::unique_ptr<T, D>::operator=(int boost::interprocess::unique_ptr<T, D>::nat::*) [with T = my_class, D = my_class_deleter] I use gcc v4.4.3 and Boost v1.51.0. BTW: I posted the same question on StackOverflow: http://stackoverflow.com/questions/13086428/how-should-i-assign-boostinterp…

1 0

Re: [Boost-users] boost wave memory leak
by Hartmut Kaiser 26 Oct '12

26 Oct '12

> I apologize if this is not standard procedure (not quite sure what > that is) but I was wondering if you've been able to reproduce the issue > using the information from my last email. Sorry, I have not had any time to look into this issue. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > > Rob Conde > > -----Original Message----- > From: boost-users-bounces(a)lists.boost.org > [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Hartmut Kaiser > Sent: Monday, October 22, 2012 8:00 PM > To: boost-users(a)lists.boost.org > Subject: Re: [Boost-users] boost wave memory leak > > > I'm getting a report of a memory leak when using boost wave. I see a > > similar problem at: > > > > https://svn.boost.org/trac/boost/ticket/4346 > > > > but supposedly that is fixed for a while. > > > > The call stack is: > > How did you get that call stack? What do I need to do to reproduce this > problem? > > Regards Hartmut > --------------- > http://boost-spirit.com > http://stellar.cct.lsu.edu > > > > > > MyDll.dll!operator new(unsigned int count, const std::nothrow_t & > > __formal) > > Line 18 + 0x9 bytes C++ > > > > MyDll.dll!operator new[](unsigned int count, const std::nothrow_t & x) > > Line > > 15 + 0xd bytes C++ > > > > MyDll.dll!boost::default_user_allocator_new_delete::malloc(const > unsigned > > int bytes) Line 97 + 0xe bytes C++ > > > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::mallo > > c_ne > > ed > > _resize() Line 693 + 0x9 bytes C++ > > > > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::malloc() > > Line 432 C++ > > > > MyDll.dll!boost::singleton_pool<boost::fast_pool_allocator_tag,12,boos > > t::d > > ef > > ault_user_allocator_new_delete,boost::mutex,32,0>::malloc() Line 137 > > + 0xb > > bytes C++ > > > > > MyDll.dll!boost::fast_pool_allocator<std::_List_nod<boost::wave::cpplexer: > > :l > > ex_token<boost::wave::util::file_position<boost::wave::util::flex_stri > > ng<c > > ha > > r,std::char_traits<char>,std::allocator<char>,boost::wave::util::CowSt > > ring > > <b > > oost::wave::util::AllocatorStringStorage<char,std::allocator<char> > > >,char *> > > > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >::_Node,boost::default_user_allocator_new_delete,boost::mutex,32,0>:: > > >al > > >loca > > te(const unsigned int n) Line 419 + 0xb bytes C++ > > > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util > > ::fi > > le > > > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > > al > > locator<char>,boost::wave::util::CowString<boost::wave::util::Allocato > > rStr > > in > > gStorage<char,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >>::_Buynode() > > Line 1172 + 0x7 bytes C++ > > > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util > > ::fi > > le > > > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > > al > > locator<char>,boost::wave::util::CowString<boost::wave::util::Allocato > > rStr > > in > > gStorage<char,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_posit > > >io > > >n<bo > > ost::wave::util::flex_string<char,std::char_traits<char>,std::allocato > > r<ch > > ar > > >,boost::wave::util::CowString<boost::wave::util::AllocatorStringStora > > >ge > > ><cha > > r,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> >() Line > > >436 > > + 0x68 bytes C++ > > > > MyDll.dll!`dynamic initializer for > > > 'boost::wave::util::impl::gen_unput_queue_iterator<boost::wave::cpplexer:: > > le > > x_iterator<boost::wave::cpplexer::lex_token<boost::wave::util::file_po > > siti > > on > > <boost::wave::util::flex_string<char,std::char_traits<char>,std::alloc > > ator > > <c > > har>,boost::wave::util::CowString<boost::wave::util::AllocatorStringSt > > har>or > > har>age< > > char,std::allocator<char> >,char *> > > > > > >,boost::wave::cpplexer::lex_token<boost::wave::util::file_position<bo > > >os > > >t::w > > ave::util::flex_string<char,std::char_traits<char>,std::allocator<char > > >,bo > > os > > t::wave::util::CowString<boost::wave::util::AllocatorStringStorage<cha > > r,st > > d: > > :allocator<char> >,char *> > > > > >,std::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_p > > >os > > >itio > > n<boost::wave::util::flex_string<char,std::char_traits<char>,std::allo > > cato > > r< > > char>,boost::wave::util::CowString<boost::wave::util::AllocatorStringS > > char>to > > char>rage > > <char,std::allocator<char> >,char *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::w > > >av > > >e::u > > til::file_position<boost::wave::util::flex_string<char,std::char_trait > > s<ch > > ar > > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util: > > >:A > > >lloc > > atorStringStorage<char,std::allocator<char> >,char *> > > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > > >>::last''() > > Line 155 + 0x28 bytes C++ > > > > msvcr90d.dll!__initterm() + 0x1c bytes > > > > > > _______________________________________________ > > Boost-users mailing list > > Boost-users(a)lists.boost.org > > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users > > ______________________________________________________________________ > This email has been scanned by the Symantec Email Security.cloud service. > For more information please visit http://www.symanteccloud.com > ______________________________________________________________________ > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

1 0

Re: [Boost-users] boost wave memory leak
by Hartmut Kaiser 26 Oct '12

26 Oct '12

> I'm getting a report of a memory leak when using boost wave. I see a > similar problem at: > > https://svn.boost.org/trac/boost/ticket/4346 > > but supposedly that is fixed for a while. > > The call stack is: How did you get that call stack? What do I need to do to reproduce this problem? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu > > MyDll.dll!operator new(unsigned int count, const std::nothrow_t & > __formal) > Line 18 + 0x9 bytes C++ > > MyDll.dll!operator new[](unsigned int count, const std::nothrow_t & x) > Line > 15 + 0xd bytes C++ > > MyDll.dll!boost::default_user_allocator_new_delete::malloc(const unsigned > int bytes) Line 97 + 0xe bytes C++ > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::malloc_ne > ed > _resize() Line 693 + 0x9 bytes C++ > > MyDll.dll!boost::pool<boost::default_user_allocator_new_delete>::malloc() > Line 432 C++ > > MyDll.dll!boost::singleton_pool<boost::fast_pool_allocator_tag,12,boost::d > ef > ault_user_allocator_new_delete,boost::mutex,32,0>::malloc() Line 137 + > 0xb > bytes C++ > > MyDll.dll!boost::fast_pool_allocator<std::_List_nod<boost::wave::cpplexer: > :l > ex_token<boost::wave::util::file_position<boost::wave::util::flex_string<c > ha > r,std::char_traits<char>,std::allocator<char>,boost::wave::util::CowString > <b > oost::wave::util::AllocatorStringStorage<char,std::allocator<char> >,char > *> > > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > >::_Node,boost::default_user_allocator_new_delete,boost::mutex,32,0>::al > >loca > te(const unsigned int n) Line 419 + 0xb bytes C++ > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util::fi > le > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > al > locator<char>,boost::wave::util::CowString<boost::wave::util::AllocatorStr > in > gStorage<char,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > >>::_Buynode() > Line 1172 + 0x7 bytes C++ > > MyDll.dll!std::list<boost::wave::cpplexer::lex_token<boost::wave::util::fi > le > _position<boost::wave::util::flex_string<char,std::char_traits<char>,std:: > al > locator<char>,boost::wave::util::CowString<boost::wave::util::AllocatorStr > in > gStorage<char,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > >::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_positio > >n<bo > ost::wave::util::flex_string<char,std::char_traits<char>,std::allocator<ch > ar > >,boost::wave::util::CowString<boost::wave::util::AllocatorStringStorage > ><cha > r,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> >() Line > >436 > + 0x68 bytes C++ > > MyDll.dll!`dynamic initializer for > 'boost::wave::util::impl::gen_unput_queue_iterator<boost::wave::cpplexer:: > le > x_iterator<boost::wave::cpplexer::lex_token<boost::wave::util::file_positi > on > <boost::wave::util::flex_string<char,std::char_traits<char>,std::allocator > <c > har>,boost::wave::util::CowString<boost::wave::util::AllocatorStringStor > har>age< > char,std::allocator<char> >,char *> > > > > >,boost::wave::cpplexer::lex_token<boost::wave::util::file_position<boos > >t::w > ave::util::flex_string<char,std::char_traits<char>,std::allocator<char>,bo > os > t::wave::util::CowString<boost::wave::util::AllocatorStringStorage<char,st > d: > :allocator<char> >,char *> > > > >,std::list<boost::wave::cpplexer::lex_token<boost::wave::util::file_pos > >itio > n<boost::wave::util::flex_string<char,std::char_traits<char>,std::allocato > r< > char>,boost::wave::util::CowString<boost::wave::util::AllocatorStringSto > char>rage > <char,std::allocator<char> >,char *> > > > >,boost::fast_pool_allocator<boost::wave::cpplexer::lex_token<boost::wav > >e::u > til::file_position<boost::wave::util::flex_string<char,std::char_traits<ch > ar > >,std::allocator<char>,boost::wave::util::CowString<boost::wave::util::A > >lloc > atorStringStorage<char,std::allocator<char> >,char *> > > > >,boost::default_user_allocator_new_delete,boost::mutex,32,0> > > >>::last''() > Line 155 + 0x28 bytes C++ > > msvcr90d.dll!__initterm() + 0x1c bytes > > > _______________________________________________ > Boost-users mailing list > Boost-users(a)lists.boost.org > http://lists.boost.org/mailman/listinfo.cgi/boost-users

2 2

How can I make the libboost_regex.a static library?
by Scott Johnson 26 Oct '12

26 Oct '12

Transitioning an application from CentOS 5 to CentOS 6 and I noticed that neither the boost-devel nor boost-static rpms contain the libboost_regex.a static library. The boost-static rpm has most of the static libs but not that one. The CentOS 5 boost-devel package had the static library. I know dynamic libraries are encouraged but I still need the static lib. I grabbed the boost src rpm. I guess I need to build a custom version of the static rpm, but not sure yet which Makefile or where to make a change to get the libboost_regex.a. Thanks for any help.

2 1

[units] Missing quantity operator++, operator%
by Nathan Crookston 25 Oct '12

25 Oct '12

All, I'm in the process of switching my homegrown units system over to boost units. Some operators which I'm missing are the modulus and the pre and post increment operators. Looking through the archives I note an original review[1] which mentioned the absence of those operators. One response claimed that quantity<si::length, int> t = 5. ...; t++; was nonsensical as writing 5 m + 1, and the reviewer eventually agreed, citing possible confusion if the quantity type converted the initializer. Matthias Schabel seemed to respond favorably: 'I debated this for a while - the only problem is that there will be some value types with heterogeneous operator+ / operator- for which q + 1 is not the same type as q, but I guess that it is just OK for it to just give a compile error in those cases.' And Steven Watanabe said 'Will do.' I haven't found anything regarding the modulus operator. My question is, would a patch adding those operators be accepted? Thanks, Nate [1] http://lists.boost.org/Archives/boost/2007/03/119001.php

3 4

Errors when linking a CXX executable to boost static libraries, using gcc4.7 and boost 1.51.0
by camille chambon 25 Oct '12

25 Oct '12

Hello, I'm trying to link a CXX executable to boost static libraries. My environment is: - Fedora 17 64bit - gcc 4.7 - boost 1.51.0 built with gcc 4.7 I then get the following errors : `.text._ZN5boost16exception_detail19error_info_injectorINS_16bad_lexical_castEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_16bad_lexical_castEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_16bad_lexical_castEED1Ev]' of /home/cchambon/libs/lib/libpgma.a(Timeline.cpp.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_16bad_lexical_castEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_16bad_lexical_castEED5Ev]' of /home/cchambon/libs/lib/libpgma.a(Timeline.cpp.o) `.text._ZN5boost16exception_detail19error_info_injectorINS_12bad_any_castEED2Ev' referenced in section `.text._ZN5boost16exception_detail19error_info_injectorINS_12bad_any_castEED1Ev[_ZN5boost16exception_detail19error_info_injectorINS_12bad_any_castEED1Ev]' of /home/cchambon/libs/lib/libpgma.a(DistributionFactory.cpp.o): defined in discarded section `.text._ZN5boost16exception_detail19error_info_injectorINS_12bad_any_castEED2Ev[_ZN5boost16exception_detail19error_info_injectorINS_12bad_any_castEED5Ev]' of /home/cchambon/libs/lib/libpgma.a(DistributionFactory.cpp.o) error: collect2: ld returned 1 exit status Does anyone know what these errors mean? Cheers, Camille

1 0

Re: [Boost-users] Occasional blocking with tcp::socket::receive
by Stuart Siegel 25 Oct '12

25 Oct '12

I have read the documentation :-) My understanding is that it's blocking if there's no data left to be read and you ask it to read from the socket. In my case, the server has sent the data and it's there waiting for it to read. I've confirmed this via wireshark and, as I mentioned, the plain POSIX call to read (which is also blocking by the way) works as expected. ________________________________ From: nullable.type <nullable.type(a)gmail.com> To: boostusers(a)googlegroups.com Cc: "boost-users(a)lists.boost.org" <boost-users(a)lists.boost.org>; boost-users(a)lists.boost.org; ssiegel95(a)yahoo.com Sent: Thursday, October 25, 2012 3:34 AM Subject: Re: [Boost-users] Occasional blocking with tcp::socket::receive Hi Read the documentation: http://www.boost.org/doc/libs/1_51_0/doc/html/boost_asio/reference/basic_st… A call to boost::asio::ip::tcp::socket::receive(..) IS a blocking call. If you wannt to avoid blocking, just use the async_* functions. Cheers, Simon On Friday, October 19, 2012 3:50:11 PM UTC+2, Stuart Siegel wrote: The call to receive below will occasionally hang. All interactions are synchronous and single threaded. Things work perfectly if I use the alternative <sys/socket.h> (POSIX) implementation under the #else. Since I'm pretty new to boost::asio, I must be doing something wrong but after many hours of trying different things, I'm still stuck. Any advice would be appreciated. #if 1 namespace bas = boost::asio; remaining = X //(something typically about 5000 bytes of char data) bas::streambuf b; bas::streambuf::mutable_ buffers_type bufs = b.prepare(1024); while (remaining > 0) { size_t n = sock.receive(bufs); //<-------------this blocks every so often remaining -= n; for ( bas::buffers_iterator<bas:: streambuf::mutable_buffers_ type, char> it = bas::buffers_begin(bufs); it < (bas::buffers_begin(bufs) + n); it++ ) qba.append(*it); } #else //this works perfectly in the 250000 or so test calls I've hit it with char buf[1024]; while (remaining > 0) { n = read( sock, buf, min( sizeof(buf), remaining ) ); remaining -= n; for (int i = 0 ; i < n; i++ ) qba.append(buf); } #endif >

1 0

Are shared_mutex's recursive?
by John M. Dlugosz 25 Oct '12

25 Oct '12

Clearly recursive acquiring of a shared (reading) lock is natural. But what about an exclusive lock? Can the owning thread acquire the write lock recursively, or even read locks recursively?

2 1