- Boost-users - lists.boost.org

Persistent graphs with boost::graph
by Maurizio Vitale 24 Jul '13

24 Jul '13

Hello boost-users, is anybody aware of a library for building persistent graphs (graphs that allow access to a certain number of previous versions of the graph) on top of boost::graph? I don't really need access to versions after every modification, but rather I consider a new version as obtained by a set of modifications that are committed as a vlock, database style. I'm interested in large graphs, so memory sharing across versions is critical. Changes between versions are minimal (few nodes/edges in graphs with O(1M) nodes each with very few edges) Thanks, Maurizio

1 0

Can't get boost log example to link
by Jarrett Chisholm 24 Jul '13

24 Jul '13

hey all I'm having trouble getting this simple boost log example to link: #include <boost/log/trivial.hpp> int main(int, char*[]) { BOOST_LOG_TRIVIAL(trace) << " a trace message "; } I can compile it ok, but linking causes the below issues: g++ -o build/main.o -c -std=c++11 -Wall -g -O0 src/main.cpp g++ -o build/test build/main.o -lboost_log -lboost_log_setup -lboost_date_time -lboost_thread -lboost_wave -lboost_regex -lboost_program_options -lboost_system -lboost_filesystem -lpthread build/main.o: In function `main': /home/jarrett/projects/chisholmsoft/logtest/src/main.cpp:5: undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()' /home/jarrett/projects/chisholmsoft/logtest/src/main.cpp:5: undefined reference to `boost::log::v2s_mt_posix::trivial::logger::get()' build/main.o: In function `boost::log::v2s_mt_posix::record::reset()': /usr/local/include/boost/log/core/record.hpp:153: undefined reference to `boost::log::v2s_mt_posix::record_view::public_data::destroy(boost::log::v2s_mt_posix::record_view::public_data const*)' build/main.o: In function `boost::log::v2s_mt_posix::record boost::log::v2s_mt_posix::sources::basic_composite_logger<char, boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level>, boost::log::v2s_mt_posix::sources::multi_thread_model<boost::log::v2s_mt_posix::aux::light_rw_mutex>, boost::log::v2s_mt_posix::sources::features<boost::log::v2s_mt_posix::sources::severity<boost::log::v2s_mt_posix::trivial::severity_level> > >::open_record<boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> >(boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> const&)': /usr/local/include/boost/log/sources/basic_logger.hpp:457: undefined reference to `boost::log::v2s_mt_posix::core::get_logging_enabled() const' build/main.o: In function `boost::log::v2s_mt_posix::aux::record_pump<boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level> >::~record_pump()': /usr/local/include/boost/log/sources/record_ostream.hpp:278: undefined reference to `boost::log::v2s_mt_posix::aux::unhandled_exception_count()' build/main.o: In function `boost::log::v2s_mt_posix::aux::record_pump<boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level> >::record_pump(boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level>&, boost::log::v2s_mt_posix::record&)': /usr/local/include/boost/log/sources/record_ostream.hpp:259: undefined reference to `boost::log::v2s_mt_posix::aux::stream_provider<char>::allocate_compound(boost::log::v2s_mt_posix::record&)' /usr/local/include/boost/log/sources/record_ostream.hpp:259: undefined reference to `boost::log::v2s_mt_posix::aux::unhandled_exception_count()' build/main.o: In function `boost::log::v2s_mt_posix::aux::record_pump<boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level> >::auto_release::~auto_release()': /usr/local/include/boost/log/sources/record_ostream.hpp:243: undefined reference to `boost::log::v2s_mt_posix::aux::stream_provider<char>::release_compound(boost::log::v2s_mt_posix::aux::stream_provider<char>::stream_compound*)' build/main.o: In function `boost::log::v2s_mt_posix::sources::aux::severity_level<boost::log::v2s_mt_posix::trivial::severity_level>::set_value(boost::log::v2s_mt_posix::trivial::severity_level)': /usr/local/include/boost/log/sources/severity_feature.hpp:135: undefined reference to `boost::log::v2s_mt_posix::sources::aux::get_severity_level()' build/main.o: In function `boost::log::v2s_mt_posix::record boost::log::v2s_mt_posix::sources::basic_logger<char, boost::log::v2s_mt_posix::sources::severity_logger_mt<boost::log::v2s_mt_posix::trivial::severity_level>, boost::log::v2s_mt_posix::sources::multi_thread_model<boost::log::v2s_mt_posix::aux::light_rw_mutex> >::open_record_unlocked<boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> >(boost::parameter::aux::tagged_argument<boost::log::v2s_mt_posix::keywords::tag::severity, boost::log::v2s_mt_posix::trivial::severity_level const> const&)': /usr/local/include/boost/log/sources/basic_logger.hpp:260: undefined reference to `boost::log::v2s_mt_posix::core::open_record(boost::log::v2s_mt_posix::attribute_set const&)' build/main.o: In function `boost::log::v2s_mt_posix::core::push_record(boost::log::v2s_mt_posix::record&&)': /usr/local/include/boost/log/core/core.hpp:308: undefined reference to `boost::log::v2s_mt_posix::core::push_record_move(boost::log::v2s_mt_posix::record&)' collect2: error: ld returned 1 exit status I using the latest boost-trunk code from svn on Debian 7 Stable 64bit. Anyone have any ideas? Cheers Jarrett

3 3

regex icu library (thread safety)
by PingShan Li 24 Jul '13

24 Jul '13

I need to build boost regex library with ICU support. I followed instruction in: http://www.boost.org/doc/libs/1_46_1/libs/regex/doc/html/boost_regex/instal… First I downloaded ICU library and compiled it without any problem. Then I ran the following command: cd /opt/third_party_libraries/boost_1_46_1/libs/regex/build/ (Boost source code is in "/opt/third_party_libraries/boost_1_46_1") [root@pli-dc-build build]# /opt/third_party_libraries/boost_1_46_1/bjam include=/usr/local/ --toolset=gcc install Performing configuration checks - has_icu builds : yes ...patience... ... ... gcc.compile.c++ ../../../bin.v2/libs/regex/build/gcc-3.4.6/debug/usinstances.o gcc.link.dll ../../../bin.v2/libs/regex/build/gcc-3.4.6/debug/libboost_regex.so.1.46.1 common.copy /opt/third_party_libraries/boost_1_46_1/lib/libboost_regex.so.1.46.1 ln-UNIX /opt/third_party_libraries/boost_1_46_1/lib/libboost_regex.so ln-UNIX /opt/third_party_libraries/boost_1_46_1/lib/libboost_regex.so.1 ln-UNIX /opt/third_party_libraries/boost_1_46_1/lib/libboost_regex.so.1.46 ...updated 22 targets... The build process is successful and I can find the library in "/opt/third_party_libraries/boost_1_46_1/lib/libboost_regex.so.1.46.1". The question is: does this library support multiple threads? I did some research on this topic, it seems like even though the name does not contain "mt", it is actually thread safe. Or do I have to pass extra parameter to generate thread safe version? The normal boost build process generates regex library with name like: libboost_regex-gcc34-mt-1_46_1.so.1.46.1 (http://www.boost.org/doc/libs/1_46_1/more/getting_started/unix-variants.html) From the name, I know if the library supports multiple threads. My development box: uname -a Linux 2.6.18-308.1.1.el5PAE #1 SMP Wed Mar 7 04:57:46 EST 2012 i686 i686 i386 GNU/Linux gcc --version gcc (GCC) 3.4.6 20060404 (Red Hat 3.4.6-4.1) Copyright (C) 2006 Free Software Foundation, Inc. Thanks

2 1

Is MultiIndex right for me?
by Sensei 23 Jul '13

23 Jul '13

Hello everyone, I was playing with std::unordered_multimap trying to achieve the following. I need to store values in no particular order. I need to find, however, all values (let's assume they are integers) that satisfy some given criteria that is NOT the simple equality. For example, I'd like to store integers, and find all integers that are equal modulo p, for instance given two integers u, v, I may write the equality predicate as return (u % p) == (v % p). This requirement might change (at compile time, of course), for example, in another map I'd like to find all integers that have a particular bit set to 1. I tried, as I said, with std::unordered_multimap, but I was told (correctly, AFAIK) that the ISO requires that items matching values MUST match also with hash values. Of course, in my case matching integers do not possess matching hashes. I was wondering if boost might be handy here. Thanks & Cheers!

2 3

[multiprecision] Compiler Warnings
by Michael Olea 23 Jul '13

23 Jul '13

Hi. I'm getting compiler warnings for narrowing conversions when I write a cpp_int to a stream. This is with boost 1_53_0 on OS X 10.8.3 using Xcode version 4.6.2 with clang: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang --version Apple LLVM version 4.2 (clang-425.0.28) (based on LLVM 3.2svn) Target: x86_64-apple-darwin12.3.0 Thread model: posix Here's a short example causing the problem: // // main.cpp // #include <boost/multiprecision/cpp_int.hpp> #include <iostream> int main(int argc, const char * argv[]) { using namespace boost::multiprecision; cpp_int u = 1; for(unsigned i = 1; i <= 100; ++i) u *= i; std::cout << "100! using arbitrary precision cpp_int:\n"; std::cout << u << std::endl; // prints 100! return 0; } The short compiler messages: In file included from /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp:5: /usr/local/include/boost/multiprecision/cpp_int.hpp:1573:34: warning: implicit conversion loses integer precision: 'unsigned long' to 'int' [-Wshorten-64-to-32] int pos = result.size() - 1; ~~~ ~~~~~~~~~~~~~~^~~ /usr/local/include/boost/multiprecision/cpp_int.hpp:1653:14: note: in instantiation of member function 'boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >::do_get_string' requested here return do_get_string(f, trivial_tag()); ^ /usr/local/include/boost/multiprecision/number.hpp:576:24: note: in instantiation of member function 'boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >::str' requested here return m_backend.str(digits, f); ^ /usr/local/include/boost/multiprecision/number.hpp:1650:22: note: in instantiation of member function 'boost::multiprecision::number<boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >, 1>::str' requested here std::string s = r.str(d, os.flags()); ^ /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp:16:12: note: in instantiation of function template specialization 'boost::multiprecision::operator<<<boost::multiprecision::backends::cpp_int_backend<0, 0, 1, 0, std::__1::allocator<unsigned int> >, 1>' requested here std::cout << u << std::endl; // prints 100! ^ In file included from /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp:5: /usr/local/include/boost/multiprecision/cpp_int.hpp:1606:34: warning: implicit conversion loses integer precision: 'unsigned long' to 'int' [-Wshorten-64-to-32] int pos = result.size() - 1; ~~~ ~~~~~~~~~~~~~~^~~ /usr/local/include/boost/multiprecision/cpp_int.hpp:1639:23: warning: implicit conversion loses integer precision: 'size_type' (aka 'unsigned long') to 'unsigned int' [-Wshorten-64-to-32] unsigned n = result.find_first_not_of('0'); ~ ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3 warnings generated. The compile command: CompileC /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.o mp_warner/main.cpp normal x86_64 c++ com.apple.compilers.llvm.clang.1_0.compiler cd /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner setenv LANG en_US.US-ASCII /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -x c++ -arch x86_64 -fmessage-length=0 -std=gnu++11 -stdlib=libc++ -Wno-trigraphs -fpascal-strings -O0 -Wno-missing-field-initializers -Wno-missing-prototypes -Wreturn-type -Wno-non-virtual-dtor -Wno-overloaded-virtual -Wno-exit-time-destructors -Wformat -Wno-missing-braces -Wparentheses -Wswitch -Wno-unused-function -Wno-unused-label -Wno-unused-parameter -Wunused-variable -Wunused-value -Wempty-body -Wuninitialized -Wno-unknown-pragmas -Wno-shadow -Wno-four-char-constants -Wno-conversion -Wconstant-conversion -Wint-conversion -Wenum-conversion -Wshorten-64-to-32 -Wno-newline-eof -Wno-c++11-extensions -DDEBUG=1 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.8.sdk -fasm-blocks -fstrict-aliasing -Wdeprecated-declarations -Winvalid-offsetof -mmacosx-version-min=10.8 -g -fvisibility-inlines-hidden -Wno-sign-conversion -iquote /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-generated-files.hmap -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-own-target-headers.hmap -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-all-target-headers.hmap -iquote /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/mp_warner-project-headers.hmap -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Products/Debug/include -I/usr/local/include -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/DerivedSources/x86_64 -I/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/DerivedSources -F/Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Products/Debug -MMD -MT dependencies -MF /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.d --serialize-diagnostics /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.dia -c /Users/olea/code/mjaal/learn/boost/build/xcode/mp_warner/mp_warner/main.cpp -o /Users/olea/Library/Developer/Xcode/DerivedData/mp_warner-fvjhjlwtkmsewtfsdqsuzhczhlxd/Build/Intermediates/mp_warner.build/Debug/mp_warner.build/Objects-normal/x86_64/main.o

2 3

Re: [Boost-users] [graph] in-depth parsing and modifications of the graph
by Orianne Siret 23 Jul '13

23 Jul '13

Thanks a lot, it worked ! Le 12/07/2013 20:54, boost-users-request(a)lists.boost.org a écrit : > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. [msm] access to root fsm (Alexander Mingalev) > 2. Re: issues compiling Boost 1.54 thread on AIX5.2 > (Vicente J. Botet Escriba) > 3. [boost format] Not getting expected errors (Rob Conde) > 4. Re: [graph] in-depth parsing and modifications of the graph > (Jeremiah Willcock) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 12 Jul 2013 20:29:36 +0400 > From: Alexander Mingalev <infest21h(a)gmail.com> > To: boost-users(a)lists.boost.org > Subject: [Boost-users] [msm] access to root fsm > Message-ID: <51E02EF0.4010202(a)gmail.com> > Content-Type: text/plain; charset="iso-8859-1"; Format="flowed" > > I have main fsm with two sub-levels. > The problem is, the sub-fsms need data which is held in root fsm, like: > > struct SomeAction > { > template <typename EVT, typename FSM, typename > SourceState, typename TargetState> > void operator()(EVT&, FSM& fsm, SourceState&, > TargetState&) const > { > // ... > } > }; > > Instance of fsm here might be root fsm as well as sub-fsm. > I see two possible solutions: > > 1. use sm_ptr policy and store parent pointer in each sub-fsm > In this case access might look like this: > > fsm.parent_->data; (access from 1-level fsm) > fsm.parent_->parent_->data; (access from 2-level fsm) > > doesn't look so nice, besides, documentation states that using sm_ptr is > deprecated. > > 2. recursively traverse all states, detect fsm's and store root pointer > > typedef RootFSM::stt stt; > typedef boost::msm::back::generate_state_set<stt>::type all_states; > > boost::mpl::for_each<all_states, boost::msm::wrap<mpl::placeholders::_1> > > (find_sub_fsm<stt>()); > > template <typename stt> > struct find_sub_fsm > { > template <class StateType> > void operator()(boost::msm::wrap<StateType>& state) const > { > // ??? > // state.root_ = &g_root; > // do the recurs > } > }; > > How to detect that StateType is sub-fsm? > > 3. Maybe, there is a easier way to communicate between sub-fsm's? > >

1 0

Announcing boost dependency analyzer
by Jens Weller 23 Jul '13

23 Jul '13

Hello to the boost community, I'd like to announce the release of a small tool, that allows you analyze the dependencies in boost. It is based on bcp, requirement is that you have bcp build and well a version of boost to analyze installed. Simply select the boost directory (the tool also might find BOOST_ROOT) and the location of bcp, and the tool will start. This will take a little time, depending on your machine, on my multicore intel ist 90 seconds - 2 minute. The tool will store this information into a database, so that with the next start, this will be a lot shorter. The tool allows to analyze the dependcies of a single boost library, but also of all of boost. Its build with Qt for the UI and processing part, and uses boost graph for the layout. Full information + download you'll find at my blogpost: http://www.meetingcpp.com/index.php/br/items/boost-dependency-analyzer.html Current Issues: What libraries might be missing? I'm reading the libs from maintainers.txt, which isn't all the boost libs. For example, lexical_cast is missing, and function_types is twice in there. (C&P error or missing library?) So far Windows is supported, linux support planned and improving, currently ownly the (beta) binaries for linux available. kind regards, Jens Weller

1 0

[icl] joining two simple intervals
by Olaf Krzikalla 23 Jul '13

23 Jul '13

Hi, I just tried and failed to find a simple way to compute the upper and lower bounds of some interval_sets: typedef boost::icl::interval_set<int> list_type; typedef list_type::value_type interval; void add_region(interval& av, const list_type& reg) { av += reg; // didn't work if (!reg.empty()) { // didn't work either: av += tAddressInterval( reg.begin()->lower(), (--reg.end())->upper())); // this one works: av = tAddressInterval(std::min(av.lower(), reg.begin()->lower()), std::max(av.lower(), (--reg.end())->upper())); } } My workaround doesn't even respect the boundary types. I wonder if there is not a simpler way for such a fundamental tasks. Best regards Olaf

2 2

[msm] access to root fsm
by Alexander Mingalev 22 Jul '13

22 Jul '13

I have main fsm with two sub-levels. The problem is, the sub-fsms need data which is held in root fsm, like: struct SomeAction { template <typename EVT, typename FSM, typename SourceState, typename TargetState> void operator()(EVT&, FSM& fsm, SourceState&, TargetState&) const { // ... } }; Instance of fsm here might be root fsm as well as sub-fsm. I see two possible solutions: 1. use sm_ptr policy and store parent pointer in each sub-fsm In this case access might look like this: fsm.parent_->data; (access from 1-level fsm) fsm.parent_->parent_->data; (access from 2-level fsm) doesn't look so nice, besides, documentation states that using sm_ptr is deprecated. 2. recursively traverse all states, detect fsm's and store root pointer typedef RootFSM::stt stt; typedef boost::msm::back::generate_state_set<stt>::type all_states; boost::mpl::for_each<all_states, boost::msm::wrap<mpl::placeholders::_1> > (find_sub_fsm<stt>()); template <typename stt> struct find_sub_fsm { template <class StateType> void operator()(boost::msm::wrap<StateType>& state) const { // ??? // state.root_ = &g_root; // do the recurs } }; How to detect that StateType is sub-fsm? 3. Maybe, there is a easier way to communicate between sub-fsm's?

3 3

packaged_task returning boost::any with BOOST_THREAD_VERSION>=3
by Nicolas P 22 Jul '13

22 Jul '13

Hello, I'm trying to enable boost (1.54) thread version >=3 with my code and i run into a package_task compilation issue I reduced my issue to a minimal test program that compiles fine on windows 7, but fails to compile on osx and linux (compilers info bellow) with BOOST_THREAD_VERSION = 3 or 4 (fine with boost thread version 2) test succeded on - Windows 7 with Visual 2010 Express sp1 with SDK 7.1 ok test failed on - Mac os x 10.6 Xcode 4.2 : gcc 4.2.1 and clang 3.0 - Mac os x 10.7 Xcode 4.4 : gcc and clang 4.0 - Ubuntu 13.04 gcc 4.7.4 The minimal test program : #define BOOST_THREAD_PROVIDES_SIGNATURE_PACKAGED_TASK #define BOOST_THREAD_VERSION 4 #include <boost/any.hpp> #include <boost/thread.hpp> #include <boost/function.hpp> boost::any process() { return 1; } int main() { boost::function< boost::any () > f = &process ; //boost::packaged_task< boost::any () > task(&process); // Works fine boost::packaged_task< boost::any () > task(f); return 0; } // Replacing 'boost::any' with 'int' make it compile. Error log with clang on os x 10.6 : In file included from /tmp/packaged_task_test/main.cpp:5: In file included from boost/thread.hpp:24: boost/thread/future.hpp:2298:27: error: no matching member function for call to 'set_value_at_thread_exit' this->set_value_at_thread_exit(f()); ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~ boost/thread/future.hpp:2857:33: note: in instantiation of member function 'boost::detail::task_object<boost::function<boost::any ()>, boost::any ()>::do_apply' requested here task = task_ptr(new task_object_type(f)); ^ /tmp/packaged_task_test/main.cpp:17:43: note: in instantiation of function template specialization 'boost::packaged_task<boost::any ()>::packaged_task<boost::function<boost::any ()> >' requested here boost::packaged_task< boost::any () > task(f); ^ boost/thread/future.hpp:673:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'source_reference_type' (aka 'boost::any &') for 1st argument void set_value_at_thread_exit(source_reference_type result_) ^ boost/thread/future.hpp:687:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'rvalue_source_type' (aka 'rv<boost::any> &') for 1st argument void set_value_at_thread_exit(rvalue_source_type result_) ^ boost/thread/future.hpp:2329:25: error: no matching member function for call to 'mark_finished_with_result' this->mark_finished_with_result(f()); ~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~ boost/thread/future.hpp:2857:33: note: in instantiation of member function 'boost::detail::task_object<boost::function<boost::any ()>, boost::any ()>::do_run' requested here task = task_ptr(new task_object_type(f)); ^ /tmp/packaged_task_test/main.cpp:17:43: note: in instantiation of function template specialization 'boost::packaged_task<boost::any ()>::packaged_task<boost::function<boost::any ()> >' requested here boost::packaged_task< boost::any () > task(f); ^ boost/thread/future.hpp:627:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'source_reference_type' (aka 'boost::any &') for 1st argument void mark_finished_with_result(source_reference_type result_) ^ boost/thread/future.hpp:633:18: note: candidate function not viable: no known conversion from 'result_type' (aka 'boost::any') to 'rvalue_source_type' (aka 'rv<boost::any> &') for 1st argument void mark_finished_with_result(rvalue_source_type result_) ^ 2 errors generated. Am i missing something ? Regards, Nicolas

1 0