- Boost-users - lists.boost.org

Example program that fails to compile (boost::bind and boost::function called for collection)
by Archie14 28 Jan '09

28 Jan '09

Below is a a test program with the purpose of calling member function for each element of the collection. Argument of this member function is a boost::function. I put compilation error after the source code. Any help will be greatly appreciated. #include <boost/bind.hpp> #include <boost/function.hpp> #include <boost/ptr_container/ptr_vector.hpp> typedef boost::function<void (int, int, const char*) > delegate; class A : public boost::noncopyable { public: commandhandler(delegate& f) {} }; template <typename C> class Acoll { typedef boost::ptr_vector<C> ptr_container; ptr_container m_data; public: typedef C CLIENT; ptr_container& operator() (){return m_data;} }; template <typename CLIENTS> class Test { CLIENTS& m_clients; public: delegate dosomething; Test(CLIENTS& val) : m_clients(val) {} void run() { std::for_each(m_clients().begin(), m_clients().end(), boost::bind(&CLIENTS::CLIENT::commandhandler, boost::ref(dosomething), _1 )); } }; int _tmain(int argc, _TCHAR* argv[]) { Acoll<A> coll; Test<Acoll<A> > test(coll); test.run(); return 0; } Error: 1>e:\libraries\boost\boost_1_37_0\boost\bind.hpp(292) : error C2664: 'R boost::_mfi::mf1<R,T,A1>::operator ()<boost::function<Signature>>(const U &,A1) const' : cannot convert parameter 2 from 'A' to 'boost::function<Signature> ' 1> with 1> [ 1> R=void, 1> T=A, 1> A1=delegate &, 1> Signature=void (int,int,const char *), 1> U=delegate 1> ] 1> and 1> [ 1> Signature=void (int,int,const char *) 1> ] 1> e:\libraries\boost\boost_1_37_0\boost\bind\bind_template.hpp(32) : see reference to function template instantiation 'void boost::_bi::list2<A1,A2>::operator ()<F,boost::_bi::list1<A &>>(boost::_bi::type<T>,F &,A &,int)' being compiled 1> with 1> [ 1> A1=boost::reference_wrapper<delegate>, 1> A2=boost::arg<1>, 1> F=boost::_mfi::mf1<void,A,delegate &>, 1> T=void, 1> A=boost::_bi::list1<A &> 1> ] 1> e:\program files\microsoft visual studio 9.0\vc\include\algorithm(29) : see reference to function template instantiation 'void boost::_bi::bind_t<R,F,L>::operator ()<T>(A1 &)' being compiled 1> with 1> [ 1> R=void, 1> F=boost::_mfi::mf1<void,A,delegate &>, 1> L=boost::_bi::list2<boost::reference_wrapper<delegate>,boost::arg<1>>, 1> T=A, 1> A1=A 1> ] 1> c:\test\t458\t458\t458.cpp(39) : see reference to function template instantiation '_Fn1 std::for_each<boost::void_ptr_iterator<VoidIter,T>,boost::_bi::bind_t<R,F,L>>(_ InIt,_InIt,_Fn1)' being compiled 1> with 1> [ 1> _Fn1=boost::_bi::bind_t<void,boost::_mfi::mf1<void,A,delegate &>,boost::_bi::list2<boost::reference_wrapper<delegate>,boost::arg<1>>>, 1> VoidIter=std::_Vector_iterator<void *,std::allocator<void *>>, 1> T=A, 1> R=void, 1> F=boost::_mfi::mf1<void,A,delegate &>, 1> L=boost::_bi::list2<boost::reference_wrapper<delegate>,boost::arg<1>>, 1> _InIt=boost::void_ptr_iterator<std::_Vector_iterator<void *,std::allocator<void *>>,A> 1> ] 1> c:\test\t458\t458\t458.cpp(37) : while compiling class template member function 'void Test<CLIENTS>::run(void)' 1> with 1> [ 1> CLIENTS=Acoll<A> 1> ] 1> c:\test\t458\t458\t458.cpp(47) : see reference to class template instantiation 'Test<CLIENTS>' being compiled 1> with 1> [ 1> CLIENTS=Acoll<A> 1> ]

2 3

Boost MPI and threads
by Clément Rezvoy 28 Jan '09

28 Jan '09

Hi all, I have a question regarding boost MPI and thread support. boost::mpi::environment uses MPI::Init to initialize MPI. I would like to be able to assess the supported thread level using MPI::Init_thread. Is it possible to first initialize MPI via MPI::Init_thread and then create a boost::mpi::environment ? the documentation reads: If the MPI environment has not already been initialized, initializes MPI with a call to MPI_Init does that also work if the initialisation is not carried out via boost::mpi::environment? Assuming the underlying MPI implementation supports it, is it safe to mix boost threads with boost MPI, at least at a FUNNELED level, carrying out all the MPI communications in the main thread? thanks for your help, Clément Rezvoy.

2 1

Build Boost 1.37 under Solaris 10 - what is the best way
by Georg Sauthoff 27 Jan '09

27 Jan '09

Hi, I built boost under Solaris with the Sun C++ compiler 12. To summarize the experience: informations are very much scattered around in the boost documentation/web pages and you have to learn bjam Finally I did it like this: $ ./configure --prefix=/my/prefix \ --with-libraries=test,program_options --with-toolset=sun $ cat > user-config.jam using sun : 5.9 : CC : <cxxflags>"-library=stlport4 -features=tmplife -features=tmplrefstatic -O" <linkflags>-library=stlport4 ; ^D $ ./tools/jam/src/bin.solaris/bjam -sICU_PATH=/usr \ --user-config=user-config.jam --with-test --with-program_options \ address-model=64 -d3 $ ./tools/jam/src/bin.solaris/bjam -sICU_PATH=/usr \ --user-config=user-config.jam --with-test --with-program_options \ address-model=64 \ -d3 --prefix=/my/prefix install My software works so far with this compiled version of boost under Solaris 10. Well, is this the right/best/official/boost/bjam-way to build boost on Solaris 10? The default sun toolset-settings does not seem to include even '-library=stlport4' option, although the Sun CC is infamous for its nonconforming STL implementation which is selected by default. Is it possible to improve the sun bjam toolset in such a way, that it selects -features=tmplife by default, if it detects that CC is of version 5.9? And is it possible to select the addresss-model=64 property via the ./configure command line? Is there is a './configure --help' aequivalent for bjam to display the options of the current toolset without reading the bjam toolset source? Best regards Georg Sauthoff

1 0

boost::signals - can't generate assignment op.
by Noah Roberts 27 Jan '09

27 Jan '09

I know that signals can't be assigned or copied, and as far as I can tell I have made sure that never happens. However, I'm still getting the warning. We have no warning policy here. Code followed by compiler output, what do I need to do?: ------------------------------------------- #include <boost/signal.hpp> #include <boost/function.hpp> struct rect {}; struct document { document() : changed_sig() {} virtual rect extents() const = 0; virtual ~document() {} boost::signals::connection attach(boost::function<void (document&)> const& slot) { return changed_sig.connect(slot); } private: boost::signal<void (document&)> changed_sig; document(document const&) {} document& operator=(document const&) { return *this;} protected: void changed(document & d) { changed_sig(d); } }; int main() { } ------------------------------------------------ 1>e:\boostvs2\include\boost\signals\trackable.hpp(163) : warning C4512: 'boost::signals::detail::bound_objects_visitor' : assignment operator could not be generated 1> e:\boostvs2\include\boost\signals\trackable.hpp(66) : see declaration of 'boost::signals::detail::bound_objects_visitor' 1>e:\boostvs2\include\boost\signals\signal_template.hpp(71) : warning C4512: 'boost::signals::detail::args1<T1>' : assignment operator could not be generated 1> with 1> [ 1> T1=document & 1> ] 1> e:\boostvs2\include\boost\signals\signal_template.hpp(344) : see reference to class template instantiation 'boost::signals::detail::args1<T1>' being compiled 1> with 1> [ 1> T1=document & 1> ] 1> e:\boostvs2\include\boost\signals\signal_template.hpp(335) : while compiling class template member function 'void boost::signal1<R,T1,Combiner,Group,GroupCompare,SlotFunction>::operator ()(T1)' 1> with 1> [ 1> R=void, 1> T1=document &, 1> Combiner=boost::last_value<void>, 1> Group=int, 1> GroupCompare=std::less<int>, 1> SlotFunction=boost::function<void (document &)> 1> ] 1> e:\boostvs2\include\boost\signal.hpp(335) : see reference to class template instantiation 'boost::signal1<R,T1,Combiner,Group,GroupCompare,SlotFunction>' being compiled 1> with 1> [ 1> R=void, 1> T1=document &, 1> Combiner=boost::last_value<void>, 1> Group=int, 1> GroupCompare=std::less<int>, 1> SlotFunction=boost::function<void (document &)> 1> ] 1> e:\dev_workspace\experimental\scratch\scratch\main.cpp(19) : see reference to class template instantiation 'boost::signal<Signature>' being compiled 1> with 1> [ 1> Signature=void (document &) 1> ] 1>Linking...

2 2

Boost.MPL: Is it possible to apply a variable substitution without evaluating the lambda-expression?
by Luke Simon 27 Jan '09

27 Jan '09

I am using BOOST_MPL_ASSERT to assert a lambda-expression applied to a sequence of types by folding the lambda-expression onto a sequence of types (see code and continue discussion below). template<class predicate, class argument> struct mpl_assert { typedef typename apply<predicate, argument>::type type; BOOST_MPL_ASSERT((type)); }; template<class pred, class xs> struct assert_for_all : foldr< mpl_assert<typename lambda<pred>::type, _>, true_, xs > {}; The foldr metafunction is a strict version of Haskell's foldr, i.e., MPL's reverse_fold with parameters passed in the order that Haskell's foldr passes parameters. The distinction isn't important for this discussion, so don't dwell on that detail. My intent is that if the lambda-expression is false for one of the types in the sequence, then the lambda-expression applied to the "bad" argument is printed in a compile-time error. However, what gets printed is the result of the lambda-expression applied to the bad argument: integral_constant<bool, false>, which is very uninformative. If the definition of mpl_assert is changed to the following: template<class predicate, class argument> struct mpl_assert { typedef typename apply<predicate, argument>::type type; BOOST_MPL_ASSERT((apply<predicate, argument>)); }; ...then what gets printed is the unevaluated application of a lambda-expression to the bad argument. While this is more informative, it is still too messy because the type is a lambda-expression containing placeholders. The most desirable type to have printed would be the lambda-expression after placeholder substitution, but before further evaluation. For example, imagine: typedef assert_for_all<is_same<foo, _>, boost::mpl::vector<foo, bar> >::type type; ...the first definition of mpl_assert prints the following uninformative type in the displayed error: boost::integral_constant<bool, false> ...the second definition of mpl_assert prints the more descriptive but overly messy type: boost::mpl::apply<boost::mpl::protect<boost::mpl::bind2<boost::mpl::quote2<boost::is_same, mpl_::void_>, foo, mpl_::arg<-0x000000001> >, 0>, bar, mpl_::na, mpl_::na, mpl_::na, mpl_::na> ...but what I want to have printed is the type: boost::is_same<foo, bar> Boost.MPL is already calculating such a type, because apply<is_same<foo, _>, bar> returns is_same<foo, bar>::type, so the needed type is there... but does Boost.MPL provide a means of accessing it as opposed to accessing its ::type field?

2 1

[boost.bind] How to retrieve the function type of a boost::bind result
by Olaf Krzikalla 27 Jan '09

27 Jan '09

Hi, The following snippet won't compile since the compiler can't deduce the template argument: template<typename T> void foo(boost::function<T> func) { /*...*/ } void bar() {} void baz() { foo(boost::bind(&bar)); // error foo<void()>(boost::bind(&bar)); // OK foo(boost::function<void()>(boost::bind(&bar))); // OK } So how do I get the first line of baz to work? That is, is there a generic way to compute the boost::function type from the bind result? Background code follows here: template<typename T> T getArg(int i) { /*...*/ } template<typename T> struct arity_dispatch; template<> struct arity_dispatch< boost::function<void()> > { static void call(const boost::function<void()>& f) { f(); } }; template<class T> struct arity_dispatch< boost::function<void(T)> > { static void call(const boost::function<void(T)>& f) { f(getArg<T>(0)); } }; template<class T, class U> struct arity_dispatch< boost::function<void(T, U)> > { static void call(const boost::function<void(T, U)>& f) { f(getArg<T>(0), getArg<T>(1)); } }; //aso. template<typename T> void generic_call(boost::function<T> func) { arity_dispatch< boost::function<T> >::call(func); } Neither is it possible for me to call "generic_call" with a boost::bind result nor is it possible to (partial) specialize for the _bi::_bind_t types as these types are internal ones. Also it seems that I can't even statically compute the arity of a boost::bind result (which would indeed help a lot). Any suggestions? If not I propose the introduction of a type function_type in the return type of a bind expression (I already needed it once before). Thanks in advance Olaf Krzikalla

3 5

Maximum Size of Matrix in Boost
by Gundala Viswanath 27 Jan '09

27 Jan '09

Hi, I have a matrix withn 10^7 * 10^7 rows, each with double value like 0.333. All this printed in text file. I want to slurp all of them in Boost Matrix, with 6GB RAM, can it handle such matrix? - Gundala Viswanath Jakarta - Indonesia

5 5

[boost.build] no best alternative error
by Sandeep Gupta 27 Jan '09

27 Jan '09

Hi, I am missing something obvious but i am at lost extending bjam. I want to chain two rules Rule 1 : generate t.gp --> x.mp Rule 2 : x.mp --> x.mps My original attempts failed (discussed here http://tinyurl.com/dg7hle)*. * I would greatly appreciate any suggestions. thanks sandeep

1 0

Re: [Boost-users] Looking for a book on graph algorithms
by Roger House 27 Jan '09

27 Jan '09

Thanks to everyone who replied to my request for pointers to books, etc., on graph algorithms. I now have several books on order. Roger House

3 2

Using Boost.Test on 64-bit OSX
by Michael Dickey 27 Jan '09

27 Jan '09

I can't seem to get Boost's unit test framework to work on OS X Leopard (10.5) when using "-arch x86_64" for 64-bit builds (note: the programs I build using boost seem to work fine, but the unit tests blow up). I have Xcode 3.1.2 installed, and the results are the same if I'm using gcc 4.0 or 4.2. I used the 32_64.diff patch from trac to make 4-way Universal boost libraries (https://svn.boost.org/trac/boost/ticket/1679 ). Any ideas would be greatly appreciated =) Thanks, -Mike Without "-arch x86_64" (defaults to 32-bit intel): Mikes-Mac-Pro:~ mdickey$ g++ -DBOOST_TEST_DYN_LINK -I/usr/local/ include/boost-1_37 -L/usr/local/lib -lboost_unit_Test_framework-xgcc42- mt -o test test.cpp Mikes-Mac-Pro:~ mdickey$ ./test Running 5 test cases... *** No errors detected With "-arch x86_64": Mikes-Mac-Pro:~ mdickey$ g++ -arch x86_64 -DBOOST_TEST_DYN_LINK -I/usr/ local/include/boost-1_37 -L/usr/local/lib -lboost_unit_Test_framework- xgcc42-mt -o test test.cpp Mikes-Mac-Pro:~ mdickey$ ./test --log_level=all Running 5 test cases... Entering test suite "simple-unit-test" Entering test suite "SimpleTests_S" Entering test case "test1" Test case test1 doesn't include any assertions Leaving test case "test1"; testing time: 22mks Entering test case "test2" Test case test2 doesn't include any assertions Leaving test case "test2"; testing time: 15mks Entering test case "test3" Test case test3 doesn't include any assertions Leaving test case "test3"; testing time: 16mks Entering test case "test4" Test case test4 doesn't include any assertions Leaving test case "test4"; testing time: 15mks Entering test case "test5" Test case test5 doesn't include any assertions Leaving test case "test5"; testing time: 14mks Leaving test suite "SimpleTests_S" Leaving test suite "simple-unit-test" *** No errors detected test(93789) malloc: *** error for object 0x30001001004d0: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug test(93789) malloc: *** error for object 0x30001001005d0: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug test(93789) malloc: *** error for object 0x30001001006c0: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug test(93789) malloc: *** error for object 0x30001001007c0: Non-aligned pointer being freed (2) *** set a breakpoint in malloc_error_break to debug gdb backtrace to malloc_error_break (note above that it's happening after completion of all tests): #0 0x00007fff810a9a11 in malloc_error_break () #1 0x00007fff810a4a90 in szone_error () #2 0x00000001000156ec in ~framework_impl [inlined] () at impl/ framework.ipp:133 #3 0x00000001000156ec in __tcf_1 () at impl/framework.ipp:222 #4 0x00007fff8100131c in __cxa_finalize () #5 0x00007fff81001232 in exit () #6 0x0000000100001057 in start () Confirm test program is a 64-bit executable: Mikes-Mac-Pro:~ mdickey$ file test test: Mach-O 64-bit executable x86_64 Dynamic linkage of test program: Mikes-Mac-Pro:~ mdickey$ otool -L test test: libboost_unit_test_framework-xgcc42-mt-1_37.dylib (compatibility version 0.0.0, current version 0.0.0) /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 7.4.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.3) Confirm Universal/FAT build of Boost libraries: Mikes-Mac-Pro:~ mdickey$ file /usr/local/lib/ libboost_unit_test_framework-xgcc42-mt.dylib /usr/local/lib/libboost_unit_test_framework-xgcc42-mt.dylib: Mach-O universal binary with 4 architectures /usr/local/lib/libboost_unit_test_framework-xgcc42-mt.dylib (for architecture i386): Mach-O dynamically linked shared library i386 /usr/local/lib/libboost_unit_test_framework-xgcc42-mt.dylib (for architecture ppc7400): Mach-O dynamically linked shared library ppc /usr/local/lib/libboost_unit_test_framework-xgcc42-mt.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64 /usr/local/lib/libboost_unit_test_framework-xgcc42-mt.dylib (for architecture ppc64): Mach-O 64-bit dynamically linked shared library ppc64 Source code for test.cpp (note that if I have just one or two test cases it doesn't crash.. having several IS significant): #define BOOST_TEST_MODULE simple-unit-test #include <boost/test/unit_test.hpp> class SimpleFixture { public: SimpleFixture() {} virtual ~SimpleFixture() {} }; BOOST_FIXTURE_TEST_SUITE(SimpleTests_S, SimpleFixture) BOOST_AUTO_TEST_CASE(test1) {} BOOST_AUTO_TEST_CASE(test2) {} BOOST_AUTO_TEST_CASE(test3) {} BOOST_AUTO_TEST_CASE(test4) {} BOOST_AUTO_TEST_CASE(test5) {} BOOST_AUTO_TEST_SUITE_END()

2 1