March 2013 - Boost-users - lists.preview.boost.org

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

[Range, Phoenix] What am I missing...
by Robert Jones 25 Apr '17

25 Apr '17

Hi Folks Can anyone explain the output of this program... #include <iostream> #include <boost/range/algorithm/copy.hpp> #include <boost/range/counting_range.hpp> #include <boost/range/adaptor/reversed.hpp> #include <boost/range/adaptor/transformed.hpp> #include <boost/phoenix/bind/bind_function.hpp> #include <boost/phoenix/core/argument.hpp> int f( int i ) { return i * 2; } int main( ) { using boost::adaptors::reversed; using boost::adaptors::transformed; using boost::counting_range; using boost::copy; using boost::phoenix::arg_names::_1; copy( counting_range( 1, 5 ) | reversed | transformed( f ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; copy( counting_range( 1, 5 ) | reversed | transformed( bind( f, _1 ) ), std::ostream_iterator<int>( std::cout, " " ) ); std::cout << std::endl; } Which is... 8 6 4 2 1768406272 1768406272 1768406272 1768406272 I'm using Gcc 4.6.2 & Boost 1.53 Thx All.

3 4

[statechart] Passing parameters from event to State Local Storage
by Christophe Bourez 16 Nov '16

16 Nov '16

I need to maintain a parameter into the state local storage. This parameter is initially contained in the event that causes the transition to the target state. I give hereafter a small illustrative example. typename sc = boost::statechart; class EvTest : public sc::event<EvTest> { public: EvTest(std::size_t val) : value(val) {} std::size_t getValue() const { return this->value; } private: std::size_t value; }; class MyStateMachine; class StSource; class StTarget; class StSource : public sc::simple_state<StSource, MyStateMachine> { public: typedef sc::custom_reaction<EvTest> reactions; sc::result react(const EvTest &event) { // How to pass event.getValue() to the target state ? transit<StTarget>(); } }; class StTarget : public sc::simple_state<StTarget, MyStateMachine> { public: StTarget(std::size_t val) : val(value) {} private: std::size_t value; }; Thanks, Christophe

5 6

Statechart serialization
by mbrodeur65 04 Mar '15

04 Mar '15

Hi, I'm looking for a solution to serialize boost::statechart objects. I'm aware that this feature is on the statechart library todo list but was wondering if there are any workaround to achieve this with the latest boost release (1.34) ? thanks for your help ! mbrodeur65 -- View this message in context: http://www.nabble.com/Statechart-serialization-tf4131326.html#a11749139 Sent from the Boost - Users mailing list archive at Nabble.com.

4 4

[Thread] Read-write locks
by lfrfly＠icqmail.com 18 Sep '14

18 Sep '14

I'm trying to create a standard read/write lock using Boost Threads, and I'm having a bit of difficulty mapping the Boost concepts onto the usual ones. A read/write lock should have several states: Locked for reading (multiple threads may lock at once), locked for writing (only one thread may lock, and no threads may be locked for reading at the same time), and unlocked. Ideally it would be nice if an RWL which is locked for reading may temporarily upgrade to locked for writing, then return to the locked for reading state. Boost supports several relevant notions of locking: shared locking, upgrade locking, and exclusive locking. This to me is a confusing distinction. In particular, a shared_mutex seems appropriate as the basis for a RWL, but is lock_upgrade() the equivalent of a write lock and lock_shared the equivalent of a read lock? This is unclear. If "upgrade locking" is not the same as "exclusive locking", then is an upgrade lock actually exclusive? Could someone please clarify this.

4 3

[Statechart] How to decide between post_event and process_event atrun time ?
by Philippe DAVID 22 Jul '14

22 Jul '14

Hi, I have a method in which I want to post/process an event. The thing is, this method can be called from outside the state machine (so I need to call process_event), or indirectly by a reaction of the state machine (in this case I must call post_event since process_event is not reentrant). I don't want to write 2 distinct methods to do this (one that calls post, and the other process), I would much rather prefer adding a 'if' in my method that tells me if I have to call process_event or post_event (if I'm being called indirectly by the state machine or not). Is there a way to do this with statechart ? regards, Philippe

3 3

[asio] resolver::cancel() problem
by Matthew Edwards 14 Mar '14

14 Mar '14

In my application (and a separate test program) it seems as though the cancel() function on the resolver does not work as intended. For async resolves, the cancel functionality should abort them immediately and pass an 'operation aborted' error code to the callback handler. In my tests, I will resolve an invalid domain (this causes the resolve to take a few seconds, to demonstrate the problem), sleep for 100ms, then call cancel on the resolver object. No cancelling actually occurs, and the callback is simply triggered after a few seconds with a "No host found" error code, not the expected operation aborted. Has anyone experienced this before, or know how I might be using the resolver incorrectly?

3 2

Server failing when BOOST_ASIO_ENABLE_HANDLER_TRACKING is active
by Gonzalo Garramuno 22 Jan '14

22 Jan '14

Trying to track down when the socket closes on my program, I turned on asio debugging. Server fails when BOOST_ASIO_ENABLE_HANDLER_TRACKING is active. Its stack trace is: g Scanning dependencies of target mrViewer [ 9%] Building CXX object mrViewer/src/CMakeFiles/mrViewer.dir/core/mrvServer.o Linking CXX executable ../../../bin/mrViewer [100%] Built target mrViewer # gga@gga-laptop1 /media/Linux/code/applications/mrViewer # mar ene 01 10:04 [8] $ mrViewer /media/Linux/movies/Tangled.mov [opengl] Using hardware shader profile: NVidia NV30 [opengl] mrViewer supports YUV images through shaders. [psql] Connected to database 'assets2d_development'. The code: boost::asio::io_service io_service; tcp::endpoint listen_endpoint(tcp::v4(), s->port); server rp(io_service, listen_endpoint, s->ui); io_service.run(); fails with: @asio|1357088683.200673|0|socket@0x7f303d8d2d00.close Got signal 11, faulty address is 0x1, from 0x4d222a [bt] Execution path: [bt] mrViewer(_ZN5boost4asio6detail15task_io_service16shutdown_serviceEv+0x3a) [0x4d222a] [bt] mrViewer(_ZN5boost4asio6detail15task_io_service16shutdown_serviceEv+0x3a) [0x4d222a] [bt] mrViewer() [0x4dd2c9] [bt] mrViewer(_ZN3mrv13server_threadEPKNS_10ServerDataE+0x408) [0x4e0e58] [bt] /usr/lib/libboost_thread.so.1.48.0(+0xdda9) [0x7f304e191da9] [bt] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a) [0x7f304f7f0e9a] [bt] /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f304da1ccbd] without the #define the code works reliably except sometimes the socket closes unexpectedly.

4 5

[boost.test] How to register custom exception for auto test?
by Jörg Becker 13 Jan '14

13 Jan '14

Hi, I'm using the test library of boost 1.49.0 for my unit tests. It works fine so fare, but if my program throws an error, I get the default error message unknown location(0): fatal error in "excption1_test": unknown type, witch hides the original error message. I tried to register an error translator, but without success. Here is what I tried (modified test/test/custom_exception_test.cpp to use auto test with global fixture): #define BOOST_TEST_MODULE "boost test custom_exception_test" #include <boost/test/unit_test.hpp> #include <boost/test/unit_test_monitor.hpp> using namespace boost::unit_test; BOOST_AUTO_TEST_SUITE( custom_exception_testsuite ) struct my_exception1 { explicit my_exception1( int res_code ) : m_res_code( res_code ) {} int m_res_code; }; void throw_my_exception1() { throw my_exception1( 12 ); } void my_exception1_translator( my_exception1 ) { BOOST_TEST_MESSAGE( "Caught my_exception1" ); } class my_config { public: my_config () { unit_test_monitor.register_exception_translator<my_exception1>( &my_exception1_translator ); } }; BOOST_GLOBAL_FIXTURE( my_config ) BOOST_AUTO_TEST_CASE( excption1_test ) { throw_my_exception1(); } BOOST_AUTO_TEST_SUITE_END() Can anybody tell me what I'm missing? Thanks, Jörg

3 5

using boost with net-snmp
by moshe levi 12 Sep '13

12 Sep '13

I wrote an example on how to integrate net-snmp with boost. please checkout http://blog-moshe.blogspot.co.il/

2 1

[BGL] Having a cost function as weight map
by Maxime van Noppen 06 Sep '13

06 Sep '13

Hi, I can't find how to do this pretty basic thing : having a function instead of a field to compute the cost of edges for various path finding algorithms. I couldn't find the answer in the documentation and Google was of no help. Did I miss something obvious ? Example : ------------------- #include <boost/graph/dijkstra_shortest_paths.hpp> #include <boost/graph/graph_traits.hpp> #include <boost/graph/adjacency_list.hpp> struct my_edge { double cost() const { return cost_ * 2; } double cost_; }; struct my_node { }; int main() { typedef boost::adjacency_list< boost::vecS, boost::vecS, boost::directedS, my_node, my_edge > graph_t; typedef boost::graph_traits<graph_t>::vertex_descriptor vertex_t; graph_t graph; vertex_t v /*= ... */; using boost::weight_map; // Works : boost::dijkstra_shortest_paths(graph, v, weight_map(boost::get(&my_edge::cost_, graph))); // Doesn't compile : //boost::dijkstra_shortest_paths(graph, v, // weight_map(boost::get(&my_edge::cost, graph))); } ------------------- Thanks ! -- Maxime

4 8

Identify cycles in a undirected graph
by NsPx 20 Aug '13

20 Aug '13

Hi all, I use undirected_dfs to detect all cycles in a undirected graph. I detect a cycle with DFSVisitor.back_edge(e,g) but how can I get the list of vertices defining this cycle ? Thanks by advance

4 4

[thread] synchronized_value: value and move semantics
by Vicente J. Botet Escriba 08 Jun '13

08 Jun '13

Hi, boost::synchronized_value (not released yet [1][2][3]) is based on [4]. See below part of this paper adapted to the Boost.Thread interface. Currently boost::synchronized_value is in addition Copyable and Swappable. I was wondering if it is worth adding value and move semantics to synchronized_value. Making it EqualityComparable, LessThanComparable and Movable if the underlying type satisfy these requirements will allow to store them on a Boost.Container/C++11 container. Do you see something completely wrong with this addition? Has some of you had a need for this? Could you share the context? Best, Vicente [1] https://svn.boost.org/svn/boost/trunk/boost/thread/synchronized_value.hpp [2] https://svn.boost.org/svn/boost/trunk/libs/thread/example/synchronized_valu… [3] https://svn.boost.org/svn/boost/trunk/libs/thread/example/synchronized_pers… [4] "Enforcing Correct Mutex Usage with Synchronized Values" by Anthony Williams http://www.drdobbs.com/cpp/enforcing-correct-mutex-usage-with-synch/2252002… ------------- [section The Problem with Mutexes] The key problem with protecting shared data with a mutex is that there is no easy way to associate the mutex with the data. It is thus relatively easy to accidentally write code that fails to lock the right mutex - or even locks the wrong mutex - and the compiler will not help you. std::mutex m1; int value1; std::mutex m2; int value2; int readValue1() { boost::lock_guard<boost::mutex> lk(m1); return value1; } int readValue2() { boost::lock_guard<boost::mutex> lk(m1); // oops: wrong mutex return value2; } Moreover, managing the mutex lock also clutters the source code, making it harder to see what is really going on. The use of synchronized_value solves both these problems - the mutex is intimately tied to the value, so you cannot access it without a lock, and yet access semantics are still straightforward. For simple accesses, synchronized_value behaves like a pointer-to-T; for example: boost::synchronized_value<std::string> value3; std::string readValue3() { return *value3; } void setValue3(std::string const& newVal) { *value3=newVal; } void appendToValue3(std::string const& extra) { value3->append(extra); } Both forms of pointer dereference return a proxy object rather than a real reference, to ensure that the lock on the mutex is held across the assignment or method call, but this is transparent to the user. [endsect] [/The Problem with Mutexes] [section Beyond Simple Accesses] The pointer-like semantics work very well for simple accesses such as assignment and calls to member functions. However, sometimes you need to perform an operation that requires multiple accesses under protection of the same lock, and that's what the synchronize() method provides. By calling synchronize() you obtain an strict_lock_ptr object that holds a lock on the mutex protecting the data, and which can be used to access the protected data. The lock is held until the strict_lock_ptr object is destroyed, so you can safely perform multi-part operations. The strict_lock_ptr object also acts as a pointer-to-T, just like synchronized_value does, but this time the lock is already held. For example, the following function adds a trailing slash to a path held in a synchronized_value. The use of the strict_lock_ptr object ensures that the string hasn't changed in between the query and the update. void addTrailingSlashIfMissing(boost::synchronized_value<std::string> & path) { boost::strict_lock_ptr<std::string> u=path.synchronize(); if(u->empty() || (*u->rbegin()!='/')) { *u+='/'; } } [endsect] [/Beyond Simple Accesses] [section Operations Across Multiple Objects] Though synchronized_value works very well for protecting a single object of type T, nothing that we've seen so far solves the problem of operations that require atomic access to multiple objects unless those objects can be combined within a single structure protected by a single mutex. One way to protect access to two synchronized_value objects is to construct a strict_lock_ptr for each object and use those to access the respective protected values; for instance: synchronized_value<std::queue<MessageType> > q1,q2; void transferMessage() { strict_lock_ptr<std::queue<MessageType> > u1 = q1.synchronize(); strict_lock_ptr<std::queue<MessageType> > u2 = q2.synchronize(); if(!u1->empty()) { u2->push_back(u1->front()); u1->pop_front(); } } This works well in some scenarios, but not all - if the same two objects are updated together in different sections of code then you need to take care to ensure that the strict_lock_ptr objects are constructed in the same sequence in all cases, otherwise you have the potential for deadlock. This is just the same as when acquiring any two mutexes. In order to be able to use the dead-lock free lock algorithms we need to use instead unique_lock_ptr, which is Lockable. synchronized_value<std::queue<MessageType> > q1,q2; void transferMessage() { unique_lock_ptr<std::queue<MessageType> > u1 = q1.unique_synchronize(boost::defer_lock); unique_lock_ptr<std::queue<MessageType> > u2 = q2.unique_synchronize(boost::defer_lock); boost::lock(u1,u2); // dead-lock free algorithm if(!u1->empty()) { u2->push_back(u1->front()); u1->pop_front(); } } [endsect] [/Operations Across Multiple Objects]

2 4

Is boost::this_thread::sleep_for interruption point?
by Serg Gulko 23 May '13

23 May '13

Hello! According to documentation(v 1.50.0) call boost::this_thread::sleep_for can be interrupted. For some reason this functionality not works for me. Here is code sample: //Simple thread function void Test::worker(int delay) { try { boost::this_thread::sleep_for(boost::chrono::milliseconds(delay)); cout << "Doing some work" << endl; } catch (boost::thread_interrupted const& e) { cout << "INTERRUPTED" << endl; } } //Far in the code boost::thread workerThread(boost::bind(&Test::worker, this, 1200)); boost::this_thread::sleep(boost::posix_time::milliseconds(30)); workerThread.interrupt(); boost::this_thread::sleep(boost::posix_time::milliseconds(1500)); I always getting 'Doing some work'... -- View this message in context: http://boost.2283326.n4.nabble.com/Is-boost-this-thread-sleep-for-interrupt… Sent from the Boost - Users mailing list archive at Nabble.com.

3 3

[FunctionTypes] Testing for a general callable type.
by Robert Jones 24 Apr '13

24 Apr '13

Hi All Is there anything in Boost to help me test for a general type being callable with a specific signature? I've found Boost.FuncionTypes, which seems to be confined to *builtin* callable types, but has made me aware that all the const/volatile/reference variations might make a general test more complicated than I first thought. Any pointers much appreciated. Thx, Rob.

6 11

Re: [Boost-users] [CMake] [boost][b2] Differenciate 32bit and 64 bit binaries when using CMake.
by Klaim - Joël Lamotte 16 Apr '13

16 Apr '13

Júlio Hoffimann said: > > I don't know if i understood correctly, but you can set the library > directory by hand, please refer to > /usr/share/cmake-<version>/Modules/FindBoost.cmake, in particular the > variable BOOST_LIBRARYDIR. On Thu, Oct 11, 2012 at 1:29 PM, Miller, Frank <FMiller(a)sjm.com> wrote: > A simple solution would be to install only the 64bit version of boost > into a new directory and change the environment variable to point there. > Then FindBoost will only be able to see the version you want. > Thanks, this will solve my immediate problem, but it don't solve it in general. (I will use it though, so thanks) I can't guarantee where the boost libraries are installed, that's why I use FindBoost. My current understanding is that boost don't have a specific default lib dir for different address models, which is the source of the problem as FindBoost script can't rely on a protocol to find these lib files. Am I correct? Joel Lamotte

3 8

[Boost.Coroutine] Problem compiling simple code with c++98 compiler
by Lukas Czaja 03 Apr '13

03 Apr '13

Hi, i was checking if my code is compatible with c++98 standard and i've encounterd compile error. With -std c++11 option everything works fine. Below i've written code causing same problem. #include <boost/coroutine/coroutine.hpp> #include <boost/coroutine/attributes.hpp> typedef boost::coroutines::coroutine<void( boost::system::error_code , std::size_t)> coro_t; struct coro_test{ coro_test() {} void coro_fun(typename coro_t::caller_type& ca)const{ boost::system::error_code ec; boost::tie(ec, boost::tuples::ignore) = ca.get(); ca(); } coro_t coro; }; int main(int argc, char *argv[]) { { boost::system::error_code ec; coro_t coro2; //default construction is ok coro_test ctest; //compile error , why ??? coro_t coro( boost::bind(&coro_test::coro_fun, &ctest, _1),coro_t::arguments( ec, 7)); coro = coro_t(boost::bind(&coro_test::coro_fun, &ctest, _1),coro_t::arguments( ec, 7)); } ... /usr/local/include/boost/type_traits/is_function.hpp:50: błąd:forming pointer to reference type 'boost::rv<boost::coroutines::coroutine<void(boost::system::error_code, long unsigned int)> >&' /usr/local/include/boost/type_traits/is_function.hpp:102: błąd:'value' is not a member of 'boost::detail::is_function_impl<boost::rv<boost::coroutines::coroutine<void(boost::system::error_code, long unsigned int)> >&>' /usr/local/include/boost/type_traits/is_convertible.hpp:354: błąd:'value' is not a member of 'boost::is_function<boost::rv<boost::coroutines::coroutine<void(boost::system::error_code, long unsigned int)> >&>' /usr/local/include/boost/utility/enable_if.hpp:59: błąd:'value' is not a member of 'boost::is_convertible<boost::coroutines::coroutine<void(boost::system::error_code, long unsigned int)>&, boost::rv<boost::coroutines::coroutine<void(boost::system::error_code, long unsigned int)> >&>' I work with Qt, g++ compiler on ubuntu 12.10 Is this library bug ?

2 3

[serialization] serializing a pointer without causing object tracking
by Stefan Strasser 02 Apr '13

02 Apr '13

Hi everyone, Hi Robert, in case you'd like to answer this one, because I have a rather specific question about your library. Thank you in advance! I'd like to serialize an object and later reconstruct it from the serialized data: void save(T const &t){ ar << t; } T* load(){ T *t=new T(); //error ar >> *t; } T might not have a default constructor. so load_construct_data should be used. apparently the way to do this is to serialize through a pointer: void save(T const *t){ ar << t; } T *load(){ T *t; ar >> t; } this works, but it causes the type T to be tracked, if its object tracking is set to track_selectively. I don't want that. but I can't set it to track_never either, because if the type is serialized at another point in the program through a pointer, the type should be tracked. is there a solution to this? is there a serialization wrapper that says "don't track this type just because of this pointer"? what comes to mind as a solution is serializing as an object, and calling load/save_construct_data manually. but then there is another problem: void save(T const &t){ save_construct_data(t,version<T>::value); ar << t; } void load(T *unconstructed_t){ load_construct_data(unconstructed_t, ??? ); ar >> *t; } if the implementation level of T is object_class_info, the object version is loaded from the preamble when the object itself is loaded. there is no in between loading the version and loading the object, it's entirely handled in the non-header part of the library. so basically I have a solution when the implementation level is object_serializable (no version info, call load_construct_data manually), and when tracking is set to track_never (serialize as a pointer). but not for the default case, object_class_info with track_selectively. am I missing something? Stefan

3 6

Newbie Interprocess message_thread user
by John Davies 01 Apr '13

01 Apr '13

I'm new to Boost and new to Linux. But old to Windows. So I'm doing some initial development in Windows XP. I have two executables made in different projects. I planned on using a message_queue to communicate between the two applications. But sending a message from one app does not make it to the other. I can add and handle messages from one thread to another within the same application. SO I know I have things partially setup correctly. But now I'm at a complete loss. Should two exe files be able to communicate through Boost message_queues? Or am I misunderstanding the whole thing?

2 2

Problems using for_each
by Michael Powell 31 Mar '13

31 Mar '13

Hello, I am struggling making for_each work right. I am using Sourcery targeting ARM. AFAIK, GCC is actually 4.7.2, and I am flagging -std=c++11. I'm not really picky how we get for_each done (or constructs like it). I'd like to avoid "macro-expansion" for obvious reasons (i.e. debug), and the always-infamous verbosity of a for loop, if possible. I've got the following: vector<rgb_type*> all; rgb_type rgb; rgb_type rgb2 = rgb.clone(); for_each(all.begin(), all.end(), cout << _1->r() << endl); With errors: _1 was not declared in this scope. (C++ Problem) That or, void rgb_printer_func(rgb_type* prgb) { cout << prgb->r() << endl; } for_each(all.begin(), all.end(), rgb_printer_func); With errors: Invalid arguments Candidates are: #1 for_each(#0, #0, #1) (Semantic Error) Thank you. Regards, Michael Powell

2 4

Building Boost 1.53
by Michael Powell 30 Mar '13

30 Mar '13

Hello, I believe we're on the home stretch building boost and getting productive with it. But I have a couple of questions. When we run ./b2 to build boost with the PREFIX option, what actually lands there? I'm thinking we just locate that in our /path/to/boost/, which ends up being ./tools/boost_1_53_0 from our project workspace perspective. But, there are other insights I don't know about I am certain. Thanks much. Regards, Michael Powell

3 5

[lockfree] Queue with shared_ptr as elements
by sguazt 30 Mar '13

30 Mar '13

Hello, Is it possible to use lockfree::queue with shared_ptr as element types? For instance, ---[code]--- #include <boost/lockfree/queue.hpp> #include <boost/smart_ptr.hpp> class foobar { }; int main() { typedef boost::shared_ptr<foobar> element_type; typedef boost::lockfree::queue<element_type> queue_type; queue_type queue; } ---[/code]--- If I compile the above code I get the following error: ---[error]--- boost_lockfree_mwmr_queue.cpp:13:13: required from here ~/projects/svn/boost-trunk/boost/lockfree/queue.hpp:81:5: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE<false>’ ~/projects/svn/boost-trunk/boost/lockfree/queue.hpp:85:5: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE<false>’ ---[/error]--- If I use "foobar" or "foobar*" as element_type, it works. I'm using - GCC 4.7.2 with the following options enabled: -Wextra -Wall -ansi -pedantic - boost SVN trunk version Thank you very much for helping. Best, -- Marco

2 1

[fusion] [mpl] binary mpl::transform on empty std::tuple
by Nathan Ridge 30 Mar '13

30 Mar '13

Hello, Fusion provides adaptation code for treating an std::tuple as a Fusion sequence, and adaptation code for treating Fusion sequences as MPL sequences, but it seems that in the case of a binary mpl::transform on an empty std::tuple, the two do not work well together. When trying to compile the following code: #include <boost/mpl/transform.hpp> #include <boost/mpl/back_inserter.hpp> #include <boost/mpl/vector.hpp> #include <boost/fusion/adapted/std_tuple.hpp> #include <boost/fusion/adapted/mpl.hpp> #include <boost/fusion/mpl.hpp> struct first { template <typename T, typename U> struct apply { typedef T type; }; }; int main() { typedef std::tuple<> fusion_sequence1_type; typedef std::tuple<> fusion_sequence2_type; typedef boost::mpl::transform<fusion_sequence1_type, fusion_sequence2_type, first, boost::mpl::back_inserter<boost::mpl::vector<>> >::type result_type; } I get the following errors: In file included from test.cpp:4: In file included from boost/fusion/adapted/std_tuple.hpp:13: In file included from boost/fusion/adapted/std_tuple/detail/begin_impl.hpp:10: boost/fusion/adapted/std_tuple/std_tuple_iterator.hpp:45:13: error: implicit instantiation of undefined template 'std::tuple_element<0, std::tuple<> >' : std::tuple_element<Iterator::index, ^ boost/fusion/iterator/value_of.hpp:34:28: note: in instantiation of template class 'boost::fusion::std_tuple_iterator<std::tuple<>, 0>::value_of<boost::fusion::std_tuple_iterator<std::tuple<>, 0> >' requested here struct apply : Iterator::template value_of<Iterator> {}; ^ boost/fusion/iterator/value_of.hpp:51:15: note: in instantiation of template class 'boost::fusion::extension::value_of_impl<boost::fusion::iterator_facade_tag>::apply<boost::fusion::std_tuple_iterator<std::tuple<>, 0> >' requested here : extension::value_of_impl<typename detail::tag_of<Iterator>::type>:: ^ boost/fusion/iterator/mpl/fusion_iterator.hpp:46:45: note: in instantiation of template class 'boost::fusion::result_of::value_of<boost::fusion::std_tuple_iterator<std::tuple<>, 0> >' requested here typedef typename fusion::result_of::value_of<Iterator>::type type; ^ boost/mpl/iterator_category.hpp:27:22: note: in instantiation of template class 'boost::mpl::fusion_iterator<boost::fusion::std_tuple_iterator<std::tuple<>, 0> >' requested here typedef typename Iterator::category type; ^ boost/mpl/pair_view.hpp:152:20: note: in instantiation of template class 'boost::mpl::iterator_category<boost::mpl::fusion_iterator<boost::fusion::std_tuple_iterator<std::tuple<>, 0> > >' requested here typename iterator_category<iter1_>::type ^ boost/mpl/aux_/has_tag.hpp:20:1: note: (skipping 5 contexts in backtrace; use -ftemplate-backtrace-limit=0 to see all) BOOST_MPL_HAS_XXX_TRAIT_NAMED_DEF(has_tag, tag, false) ^ boost/mpl/has_xxx.hpp:244:65: note: expanded from macro 'BOOST_MPL_HAS_XXX_TRAIT_NAMED_DEF' , boost::mpl::aux::type_wrapper<BOOST_MSVC_TYPENAME U::name>* = 0 \ ^ boost/mpl/transform.hpp:75:7: note: in instantiation of template class 'boost::mpl::fold<boost::mpl::pair_view<std::tuple<>, std::tuple<> >, boost::mpl::vector<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na>, boost::mpl::bind2<boost::mpl::push_back<mpl_::na, mpl_::na>, mpl_::arg<1>, boost::mpl::bind2<first, boost::mpl::bind1<boost::mpl::first<mpl_::na>, mpl_::arg<2> >, boost::mpl::bind1<boost::mpl::second<mpl_::na>, mpl_::arg<2> > > > >' requested here : fold< ^ boost/mpl/transform.hpp:114:1: note: in instantiation of template class 'boost::mpl::aux::transform2_impl<std::tuple<>, std::tuple<>, first, boost::mpl::back_inserter<boost::mpl::vector<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na> > >' requested here BOOST_MPL_AUX_INSERTER_ALGORITHM_DEF(4, transform2) ^ boost/mpl/aux_/inserter_algorithm.hpp:44:7: note: expanded from macro 'BOOST_MPL_AUX_INSERTER_ALGORITHM_DEF' : aux::name##_impl<BOOST_MPL_PP_PARAMS(arity, P)> \ ^ boost/mpl/eval_if.hpp:38:22: note: in instantiation of template class 'boost::mpl::transform2<std::tuple<>, std::tuple<>, first, boost::mpl::back_inserter<boost::mpl::vector<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na> > >' requested here typedef typename f_::type type; ^ boost/mpl/transform.hpp:138:1: note: in instantiation of template class 'boost::mpl::eval_if<boost::mpl::or_<boost::mpl::is_na<first>, boost::mpl::is_lambda_expression<std::tuple<> >, boost::mpl::not_<boost::mpl::is_sequence<std::tuple<> > >, mpl_::bool_<false>, mpl_::bool_<false> >, boost::mpl::transform1<std::tuple<>, std::tuple<>, first>, boost::mpl::transform2<std::tuple<>, std::tuple<>, first, boost::mpl::back_inserter<boost::mpl::vector<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na> > > >' requested here AUX778076_TRANSFORM_DEF(transform) ^ boost/mpl/transform.hpp:125:22: note: expanded from macro 'AUX778076_TRANSFORM_DEF' typedef typename eval_if< \ ^ test.cpp:21:25: note: in instantiation of template class 'boost::mpl::transform<std::tuple<>, std::tuple<>, first, boost::mpl::back_inserter<boost::mpl::vector<mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na, mpl_::na> > >' requested here typedef boost::mpl::transform<fusion_sequence1_type, ^ c++/4.8.0/tuple:672:12: note: template is declared here struct tuple_element; ^ 1 error generated. Seems like something is trying to call value_of on the begin iterator of the tuple, which in the case of an empty tuple is a past-the-end iterator. If I use non-empty tuples instead: typedef std::tuple<int> fusion_sequence1_type; typedef std::tuple<int> fusion_sequence2_type; It works fine. Unary mpl::transform works fine in either case. Am I doing something wrong, or is this a bug? Thanks, Nate

1 0

Elegant solution to interview question about boost::fusion::vector
by Stuart 29 Mar '13

29 Mar '13

Hello everyone, I have stumbled over m2pq36bk97.fsf(a)boostpro.com in comp.lang.c++.moderated. I had never used boost before but I always try to solve interview questions. I found a solution that works, but I have the feeling that there must be a more elegant solution. The problem that was presented in the interview was the following: typedef boost::fusion::vector<int, double, float> row; std::vector<row> M; template <typename T> typename T::value_type Accumulate (T const &t) { typedef typename T::value_type value_type; return std::accumulate (t.begin (), t.end (), value_type ()); } Provide a function fun so that Accumulate (fun<0>(M)); computes the sum of the first column of M, or more generally Accumulate (fun<x>(M)); computes the sum of the xth column of M. The solution that was provided in m2pq36bk97.fsf(a)boostpro.com did not work out of the box, but I was able to fix it into the following solution: // Functor that extracts nth element of row vector. template <unsigned N> struct tuple_at { template <class Vector> typename boost::fusion::result_of::at_c<const Vector,N>::type operator()(Vector const& t) const { return boost::fusion::at_c<N, Vector>(t); } }; template <unsigned N, class M> auto fun(M const& x) -> decltype(x | boost::adaptors::transformed(tuple_at<N>())) { return x | boost::adaptors::transformed(tuple_at<N>()); } so that int main () { M.push_back(row (1, 1.0, 2.8)); M.push_back(row (2, 0.1, 2.8)); M.push_back(row (3, 0.01, 2.8)); std::cout << Accumulate(fun<1> (M)); } prints 1.11 as expected. However, I think that I should be able to achieve the same without the template tuple_at. I tried using a lambda: template <unsigned N, class M> auto fun(M const& x) -> decltype(x | boost::adaptors::transformed( [] (typename M::value_type const& x ) { return boost::fusion::at_c<N> (x); })) { auto retval = x | boost::adaptors::transformed( [] (typename M::value_type const& x ) { return boost::fusion::at_c<N> (x); }); return retval; } Unfortunately, this does not compile ("Lambda expression in an unevaluated operand"). I'm also not sure whether boost::adaptor::transformed can work with lambdas. I also tried to generate a functor object from boost::fusion::at_c using the following code from the internet: template<typename T> std::function<T> make_function (T* t) { return { t }; } template <unsigned N, class M> auto fun (M const& x) -> decltype(make_function(&boost::fusion::at_c<N, const M>)) { auto retval = make_function(&boost::fusion::at_c<N, const M> ); return retval } but this yields an error that I can't decipher yet: at.hpp:62:15: Implicit instantiation of undefined template 'boost::fusion::extension::at_impl<boost::fusion::non_fusion_tag>::apply<const std::__1::vector<boost::fusion::vector<int, double, float, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_>, std::__1::allocator<boost::fusion::vector<int, double, float, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_, boost::fusion::void_>>>, mpl_::int_<2>>' The ideal solution would be one where I don't have to write the functor object manually. Even more elegantly, I should be able to leave out the return type and let the compiler figure it out automatically. Unfortunately, I use llvm gcc 4.2, so the automatic return type evaluation is out of reach (although boost without this feature seems to be quite cumbersome). Can anyone provide some insights? Thanks in advance, Stuart

2 2

[chrono][thread] Best way to wait?
by Klaim - Joël Lamotte 29 Mar '13

29 Mar '13

Hi, can someone clarify: 1. what is the difference between: const auto wait_time = boost::chrono::miliseconds( 8 ); boost::mutex mutex; boost::unique_lock<boost::mutex> lock( mutex ); boost::condition_variable wait_condition; wait_condition.wait_for( lock, wait_time ); and const auto wait_time = boost::chrono::miliseconds( 8 ); boost::this_thread::sleep_for( wait_time ); 2. are there other ways to wait? (I mean make the thread sleep, not looping until it's time) Joel Lamotte

2 4