July 2012 - Boost-users - lists.boost.org

[1.50.0][scope exit] dead link documentation
by Akira Takahashi 05 Jul '12

05 Jul '12

Hi, I found dead link documentation in follow page's "Tutorial" link. http://www.boost.org/doc/libs/1_50_0/libs/scope_exit/doc/html/index.html "404 Not Found File "/home/grafik/www.boost.org/archives/live/boost_1_50_0/libs/scope_exit/doc/html/scope_exit/Tutorial.html" not found. Unable to find file." Correct page is "tutorial.html". Please fix link. Thanks, Akira >>======================== Akira Takahashi mailto:faithandbrave@gmail.com site : https://sites.google.com/site/faithandbrave/about/en

2 2

[boost.python] exec_file crashes when using python 3.2
by yjaeger＠free.fr 04 Jul '12

04 Jul '12

Hi, I'm very new to boost, and I first want to thank you all for the hard and impressive work that has been done. I'm currently trying to use Boost.python and I'm facing an annoying issue. The following source code compiles fine (with msvc10 and mingw gcc 4.7): #include <boost/python.hpp> #include <iostream> using namespace boost::python; void greet() { // Retrieve the main module. object main = import("__main__"); // Retrieve the main module's namespace object global(main.attr("__dict__")); // Define greet function in Python. object result = exec("def greet():\n" " return 'Hello from Python!' \n", global, global); // Create a reference to it. object greet = global["greet"]; // Call it. std::string message = extract<std::string>(greet()); std::cout << message << std::endl; } void greet_file() { // Retrieve the main module. object main = import("__main__"); // Retrieve the main module's namespace object global(main.attr("__dict__")); // Define greet function in Python. object result = exec_file("hello.py", global, global); // Create a reference to it. object greet = global["greet"]; // Call it. std::string message = extract<std::string>(greet()); std::cout << message << std::endl; } void main(int argc, char** argv) { Py_Initialize(); greet(); greet_file(); } It even runs perfectly well when I'm using boost.python linked against python 2.7.3 library. I have following output: Hello from Python! Hello from Python! The issue appears when I link boost.python against python 3.2 (tried with 3.2.2 and 3.2.3) the first 'Hello from Python!' shows up, but then it crashes and all I can see is a windows message box saying 'prog.exe has stopped working'. It's not that I absolutely want to use python 3, but as I'm working on a new project, I'm concerned with durability, so I would prefer 3.2. Any idea would be welcome. Thanks for reading. Yannick.

1 0

[bgl] depth_first_search does not compile. color_map howto?
by Joachim Faulhaber 04 Jul '12

04 Jul '12

Hi, When using visitors with the depth_first_search algorithm I can successfully compile and run this code: //========================================================= template<class Graph> class Visitor: public default_dfs_visitor { public: typedef typename graph_traits<Graph>::vertex_descriptor Vertex; void discover_vertex(Vertex v, const Graph& g)const {cout << v << " "; return;} }; void GLV_visit() { typedef adjacency_list<listS, vecS, directedS> GraphLV; GraphLV g; add_edge(0, 1, g); add_edge(0, 2, g); add_edge(1, 2, g); add_edge(1, 3, g); Visitor<GraphLV> vis; boost::depth_first_search(g, visitor(vis)); cout << endl; } BOOST_AUTO_TEST_CASE(graph_test) { GLV_visit(); } //========================================================= With a slightly different graph (listS instead of vecS for vertices) the same call of depth_first_search fails to compile with msvc-10. //========================================================= struct Int{ Int(): _value(0){} Int(int val): _value(val){} int _value; }; void GLL_visit() { typedef adjacency_list<listS, listS, directedS, Int> GraphLL; typedef graph_traits<GraphLL>::vertex_descriptor VertexLL; GraphLL g; Int val(42); VertexLL v0 = boost::add_vertex(g); VertexLL v1 = boost::add_vertex(g); g[v0] = Int(0); g[v1] = Int(1); add_edge(v0, v1, g); Visitor<GraphLL> vis; boost::depth_first_search(g, visitor(vis)); //compile errors } //========================================================= >From the tiny error message of 108 long verbose lines of internal graph template instantiations (see attachment) it seems that the compiler is unable to create a default color_map (but I might be wrong with this interpretation of the template jungle). 1. Do I need to provide a color_map parameter here? 2. If so, what is the simplest way to do that and provide an object of the appropriate type? I'd greatly appreciate a working code example. Examples and best practices for defining and handling external propery maps in general would be helpful. TIA, Joachim -- Interval Container Library [Boost.Icl] http://www.joachim-faulhaber.de

2 5

Re: [Boost-users] [boost.test] Missing entry point when statically linking
by Tan, Tom (Shanghai) 04 Jul '12

04 Jul '12

> Date: Tue, 3 Jul 2012 19:25:50 +0000 (UTC) > From: Gennadiy Rozental <rogeeff(a)gmail.com> > >Tan, Tom (Shanghai <TTan <at> husky.ca> writes: > > #include <boost/test/unit_test.hpp> > using namespace boost::unit_test::framework; using namespace > boost::unit_test; ? > test_suite* init_unit_test_suite(int argc, char *argv[]) { ??? > BOOST_TEST_MESSAGE("hello test."); ? > ??? return 0; > } > With the same build options: > cl.exe /EHsc /MT main.cpp > ? > VC2010 compiles fine. VC2012 outputs: > LINK : fatal error LNK1561: entry point must be defined. >Don't you need to link with static library? Can you try using single header variants? >Gennadiy I am trying to use the static library, because I was under the impression that the feature in this variant would be more complete than others. With VC++ I do not have to explicitly specify the static file name in the command line if it's what you mean. And if this is the problem, the error would be like LINK : fatal error LNK1104: cannot open file 'libboost_unit_test_framework-vc110-mt-s-1_50.lib' I had a re-read of the single header variant documentation. Seems I can just switch to it. But it still seems strange that the static variant works with VC10 but not VC11.

2 1

Re: [Boost-users] [boost.test] Missing entry point when statically linking
by Tan, Tom (Shanghai) 04 Jul '12

04 Jul '12

>Date: Tue, 3 Jul 2012 19:52:31 +0100 >rom: Marco Craveiro <marco.craveiro(a)gmail.com> > >Hi Tom, > >shouldn't it be > >#include <boost/test/included/unit_test.hpp> > >on the include? Thanks, Marco. I was intending to use the library variant because I recall reading somewhere the header only variant missing some test tools. Judging from this link: (http://www.boost.org/doc/libs/1_50_0/libs/test/doc/html/utf/user-guide/ usage-variants/single-header-variant.html) I just read, I seem to be wrong. The code in question was in place since around 2005. I never thought of changing it until it's rejected by vc11. Thanks for the suggestion.

1 0

Hello, I am using boost graph, I have a questions about disable edge in one graph
by mingliang zou 03 Jul '12

03 Jul '12

I created a graph. And use add_edge to add some edges, I wanna disable some edges, and add some edges. and use boost graph algorithm for enable edges How can I do this? not create new graph.

2 5

Compilation Error related to 'range'
by VimalMathew＠Eaton.com 03 Jul '12

03 Jul '12

Hi, I have this line of code in my header file: project(C, range(0, A_rows), range(0, A_cols)) = A; I've specified: #include <boost/numeric/ublas/storage.hpp> using namespace boost::numeric::ublas; at the beginning of the header file When I compile my .cpp file, I get an error message saying: "c:\users\c9995799\desktop\level 1 problem for mpi\dmatrix.hpp(34): error C2784: 'const boost::numeric::ublas::matrix_range<M> boost::numeric::ublas::project(const boost::numeric::ublas::matrix_range<M> &,const matrix_range<M>::range_type &,const matrix_range<M>::range_type &)' : could not deduce template argument for 'const boost::numeric::ublas::matrix_range<M> &' from 'boost::numeric::ublas::matrix<T>'" This error goes away if I substitute boost::numeric::ublas::range instead of just range here: project(C, range(0, A_rows), range(0, A_cols)) = A; How do I get this to work the way it currently is? Thanks, Vimal

2 1

[boost.test] Missing entry point when statically linking to VC2012 but no problem with VC2010
by Tan, Tom (Shanghai) 03 Jul '12

03 Jul '12

I have been using a source template for unit test with boost.test, which used to be working well until I started to use VC2012 RC. Here's a minimal repo: #include <boost/test/unit_test.hpp> using namespace boost::unit_test::framework; using namespace boost::unit_test; test_suite* init_unit_test_suite(int argc, char *argv[]) { BOOST_TEST_MESSAGE("hello test."); return 0; } With the same build options: cl.exe /EHsc /MT main.cpp VC2010 compiles fine. VC2012 outputs: LINK : fatal error LNK1561: entry point must be defined. Added BOOST_TEST_MAIN caused errors for both compilers. error C2084: function 'boost::unit_test::test_suite *init_unit_test_suite(int,char *[])' already has a body I tested on both 1.49 and 1.50. And the results are the same. I suspect there is a bug of version check against MSVC but could not locate it.

3 2

boost-spirit: need help with simple parser
by Allan Nielsen 03 Jul '12

03 Jul '12

Hi I would like to use boost::spirit for parsing ipv4 addresses. Here is what I have tried to do: struct Ipv4 { Ipv4() { raw.as_int = 0; } Ipv4( const Ipv4& i ) { raw.as_int = i.raw.as_int; } Ipv4& operator=(const Ipv4& i ) { raw.as_int = i.raw.as_int; return *this; } Ipv4(const boost::tuple<uint8_t, uint8_t, uint8_t, uint8_t>& v) { raw.as_char[3] = v.get<0>(); raw.as_char[2] = v.get<1>(); raw.as_char[1] = v.get<2>(); raw.as_char[0] = v.get<3>(); } union { uint32_t as_int; uint16_t as_short[2]; uint8_t as_char[4]; } raw; }; struct DecOctet : qi::grammar<const char *, uint8_t()> { DecOctet() : DecOctet::base_type(start) { start %= qi::uint_parser<uint8_t, 10, 1, 3>(); } qi::rule<const char *, uint8_t()> start; } dec_octet; struct Ipv4Address : qi::grammar<const char *, Ipv4()> { Ipv4Address() : Ipv4Address::base_type(start) { start %= dec_octet >> qi::lit('.') >> dec_octet >> qi::lit('.') >> dec_octet >> qi::lit('.') >> dec_octet ; } qi::rule<const char *, Ipv4()> start; } ipv4_address; bool parse(const const_string& s, Ipv4& i) { Ipv4 _i; const char * iter = s.begin(); bool r = qi::parse(iter, s.end(), ipv4_address, _i); if( !r || iter != s.end() ) return false; i = _i; return true; } But unfortunately if I parse an address such as "1.2.3.4", I end up with the address "1.0.0.0" in my Ipv4 struct. The IPv4 struct is legacy code, and the union member can therefor not be changed. I can add other constructors, but I prefer non-intrusive changes. So here are my questions: - What have I done wrong? - How should this has been done if I did not have a constructor accepting the tuple? - How would you have done? Best regards Allan W. Nielsen

3 7

FW: Does the boost library free the memory occupied by the vector automatically when I call erase method provided by list class?
by Gordon HUYUE 03 Jul '12

03 Jul '12

From: huyuevip(a)hotmail.com To: boost-users(a)lists.boost.org Subject: Does the boost library free the memory occupied by the vector automatically when I call erase method provided by list class? Date: Tue, 3 Jul 2012 10:03:34 +0000 Hi all, Currently I am using "boost/interprocess" to manage shared memory between parent process and child process, the OS is AIX 6.1. The boost library is really cool and it works well, but I still have something to worry about, because the program is server side application and should be available 24/7. I apply memory at the beginning of the program, the size of memory is big enough; I use a list object provided by boost, the element type of the list object is a request object, the request object has a member with property of vector, Here is my concern: Does the boost library free the memory occupied by the vector automatically when I call erase method provided by list class? if it does not , the memory will be run out soon, because the program will add and delete object from list frequently. I'd like to make sure whether the boost library can deal with it. If it cann't, Is there any other solutions? some tips when reading demo file Line 55: definition of RequestObject Line 67: this is a member variable inside RequestObject interfaceobject_vector myvector; Line 79: definition of List, the element of this List is RequestObject Line 139: we add a request object into list. myRequestObjectList->push_front(*myRequestObject); Line 268: we delete a request objest from list, in this case , Does boost library free the memory occupied by myvector(which is a member variable inside RequestObject) automatically? myRequestObjectList->erase(myIterator); The file attached is a demo cpp, I hope it will be helpful for everybody to understand my question easily. If we add InterfaceObject_sh object into myvector when initializing, and add request object(which include myvector) into list, finally we call erase methed provided by list, Does boost library free the memory occupied by myvector automatically? Best Regards, Gordon

1 0

[Phoenix] Simple if_ issue
by Aaron_Wright＠selinc.com 02 Jul '12

02 Jul '12

I'm trying to do a simple if/else statement using boost::phoenix and I seem to mis-understanding something. namespace bp = boost::phoenix; namespace bpa = bp::arg_names; boost::function< std::string () > test1 = bp::val("true"); boost::function< std::string (bool) > test2 = bp::if_(bpa::arg1) [ bp::val("true") ] .else_ [ bp::val("false") ]; The first one works, but the second one doesn't. I get an error about not being able to convert void to std::string: cannot convert parameter 1 from 'void' to 'const std::basic_string<_Elem,_Traits,_Ax> & What do I need to do in the second test to get it to compile? Can I tell if_ that its return type is not void? --- Aaron Wright

3 3

[exception] Passing existing exception hierarchies between threads
by Szymon Gatner 02 Jul '12

02 Jul '12

Hi, I am trying to pass Poco::Exeption from worker thread to a client thread/future. Idea is simple: try { operationThatMyThrowPocoException(); } catch (const Poco::Exception& e) { // rethrow with exception_ptr support so can be passed between threads BOOST_THROW_EXCEPTION(e); } but this causes compilation error because Poco::Exception defines clone() method on its own: error C2555: 'boost::exception_detail::clone_impl<T>::clone': overriding virtual function return type differs and is not covariant from 'Poco::Exception::clone' c:\devel\boost_1_50_0\boost\exception\exception.hpp 468 Is there a way to use BOOST_THROW_EXCEPTION / enable_current_exception() with existing exception hierarchies that define clone() already? Regards, Szymon -- Szymon Gatner The Lordz Games Studio www.thelordzgamesstudio.com

2 1

Compilations problem when including boost/spirit/include/qi.hpp
by Allan Nielsen 02 Jul '12

02 Jul '12

Hi, I'm trying to use boost spirit for an embedded application running on mips32 hardware, compiled with a gcc 4.6.3 toolchain. The toolchain is build with newlib and libstdc++ with -fno-exceptions. When I try to include iq.hpp I get the following compiler error. In file included from /data/anielsen/boost_1_49_0/boost/spirit/home/support/utf8.hpp:17:0, from /data/anielsen/boost_1_49_0/boost/spirit/home/support/info.hpp:18, from /data/anielsen/boost_1_49_0/boost/spirit/home/qi/domain.hpp:16, from /data/anielsen/boost_1_49_0/boost/spirit/home/qi/meta_compiler.hpp:15, from /data/anielsen/boost_1_49_0/boost/spirit/home/qi/action/action.hpp:14, from /data/anielsen/boost_1_49_0/boost/spirit/home/qi/action.hpp:14, from /data/anielsen/boost_1_49_0/boost/spirit/home/qi.hpp:14, from /data/anielsen/boost_1_49_0/boost/spirit/include/qi.hpp:16, from ../../vtss_appl/misc/string.cxx:5: /data/anielsen/boost_1_49_0/boost/type_traits/make_unsigned.hpp: In instantiation of ‘boost::detail::make_unsigned_imp<wchar_t>’: /data/anielsen/boost_1_49_0/boost/type_traits/make_unsigned.hpp:130:1: instantiated from ‘boost::make_unsigned<wchar_t>’ /data/anielsen/boost_1_49_0/boost/spirit/home/support/utf8.hpp:35:52: instantiated from ‘boost::spirit::utf8_string boost::spirit::to_utf8(Char) [with Char = wchar_t, boost::spirit::utf8_string = std::basic_string<char>]’ /data/anielsen/boost_1_49_0/boost/spirit/home/support/info.hpp:54:42: instantiated from here /data/anielsen/boost_1_49_0/boost/type_traits/make_unsigned.hpp:39:1: error: invalid application of ‘sizeof’ to incomplete type ‘boost::STATIC_ASSERTION_FAILURE<false>’ I do know that this is not the most typical setup, but I have had other problems which was solved just by adding a define, or avoid an include file. Any hints will be appreciated Regards Allan W. Nielsen

1 0

Boost Graph library migration 1.48 => 1.49 (1.50)
by Gregory 02 Jul '12

02 Jul '12

Hi, All! I am newbie in boost. The code fragment compiled without errors with boost 1.48.0 in MS Visual Studio 2008 , but returns compiler error with boost 1.49 and 1.50 : error C2784: 'E boost::detail::get(boost::detail::underlying_edge_desc_map_type<E>, const boost::detail::reverse_graph_edge_descriptor<EdgeDesc> &)' : could not deduce template argument for 'boost::detail::underlying_edge_desc_map_type<E>' from 'double *' c:\program files\boost\boost_1_50_0\boost\graph\dijkstra_shortest_paths.hpp 140 . typedef boost::adjacency_list<vecS,vecS,directedS, no_property, property < edge_weight_t, double > > Graph; Graph g(100); typedef graph_traits < Graph >::vertex_descriptor vertex_descriptor; typedef graph_traits< Graph >::edge_descriptor edge_descriptor; property_map< Graph, edge_weight_t>::type weightmap = get(edge_weight, g); /* graph filling code */ std::vector<vertex_descriptor> predesessor(num_vertices(g)); std::vector<double> distances(num_vertices(g)); vertex_descriptor startV = vertex(startIx, g); property_map<Graph, vertex_index_t>::type indexmap = get(vertex_index, g); dijkstra_shortest_paths(g,startV,&predesessor[0],&distances[0], weightmap, indexmap, std::less<double>(), closed_plus<double>(), (std::numeric_limits<double>::max)(), 0, default_dijkstra_visitor()); WBW&R, Gregory

2 1

statechart XCode 4.5 compilation error
by Антон Бычков 02 Jul '12

02 Jul '12

Hi. The following source code does not compile in XCode 4.5 (it is developer preview 2 version at this moment). I've got answer from one of the apple guys: "It's a known issue that when using libc++ in C++11 mode, instantiating std::list causes instantiation of the element type more aggressively than other std::list implementations. This probably won't be fixed for Xcode 4.5." Source code: #include <functional> #include <iostream> #include <boost/statechart/state.hpp> #include <boost/statechart/state_machine.hpp> class InitialState; class StateMachine : public boost::statechart::state_machine<StateMachine, InitialState> { public: StateMachine() { } }; class InitialState : public boost::statechart::simple_state<InitialState, StateMachine> { public: InitialState() { } }; int main(int argc, char const* argv[]) { std::cout << "Hello, World!\n"; StateMachine s; return 0; } Errors: In file included from /Users/developer/Downloads/Sandbox/Sandbox/main.cpp:12: In file included from /usr/local/boost_1_50_0/boost/statechart/state.hpp:11: In file included from /usr/local/boost_1_50_0/boost/statechart/simple_state.hpp:13: /usr/local/boost_1_50_0/boost/statechart/detail/leaf_state.hpp:26:27: error: base class has incomplete type class leaf_state : public state_base< Allocator, RttiPolicy > ~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/type_traits:1889:54: note: in instantiation of template class 'boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>' requested here decltype(_VSTD::move(_Tp(_VSTD::declval<_Args>()...)), true_type()) ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/type_traits:1890:1: note: while substituting deduced template arguments into function template '__is_constructible_test' [with _Tp = std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>>, _Args = <no value>] __is_constructible_test(_Tp&&, _Args&& ...); ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/type_traits:1949:14: note: in instantiation of template class 'std::__1::__is_constructible<false, std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>>, std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>> &&>' requested here : public __is_constructible<is_scalar<_Tp>::value || is_reference<_Tp>::value, ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/type_traits:1975:14: note: in instantiation of template class 'std::__1::__is_constructible_void_check<false, std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>>, std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>> &&>' requested here : public __is_constructible_void_check<__contains_void<_Tp, _Args...>::value ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/type_traits:2455:34: note: in instantiation of template class 'std::__1::is_constructible<std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>>, std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>> &&>' requested here : __is_nothrow_constructible<is_constructible<_Tp, _Args...>::value, _Tp, _Args...> ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/type_traits:2590:14: note: (skipping 3 contexts in backtrace; use -ftemplate-backtrace-limit=0 to see all) : public is_nothrow_constructible<_Tp, typename add_rvalue_reference<_Tp>::type> ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/list:513:52: note: in instantiation of template class 'std::__1::__compressed_pair<unsigned long, std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>>>' requested here __compressed_pair<size_type, __node_allocator> __size_alloc_; ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/list:770:15: note: in instantiation of template class 'std::__1::__list_imp<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, std::__1::allocator<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>>>' requested here : private __list_imp<_Tp, _Alloc> ^ /usr/local/boost_1_50_0/boost/statechart/detail/state_base.hpp:139:16: note: in instantiation of template class 'std::__1::list<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, std::__1::allocator<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>>>' requested here typename state_list_type::iterator & statesEnd, ^ /usr/local/boost_1_50_0/boost/statechart/state_machine.hpp:510:22: note: in instantiation of template class 'boost::statechart::detail::state_base<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>' requested here typedef typename state_base_type::node_state_base_ptr_type ^ /Users/developer/Downloads/Sandbox/Sandbox/main.cpp:17:29: note: in instantiation of template class 'boost::statechart::state_machine<StateMachine, InitialState, std::__1::allocator<void>, boost::statechart::null_exception_translator>' requested here class StateMachine : public boost::statechart::state_machine<StateMachine, InitialState> ^ /usr/local/boost_1_50_0/boost/statechart/detail/state_base.hpp:57:7: note: definition of 'boost::statechart::detail::state_base<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>' is not complete until the closing '}' class state_base : ^ In file included from /Users/developer/Downloads/Sandbox/Sandbox/main.cpp:12: In file included from /usr/local/boost_1_50_0/boost/statechart/state.hpp:11: In file included from /usr/local/boost_1_50_0/boost/statechart/simple_state.hpp:13: /usr/local/boost_1_50_0/boost/statechart/detail/leaf_state.hpp:44:44: error: no type named 'iterator' in 'std::__1::list<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, std::__1::allocator<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>>>' typename base_type::state_list_type::iterator listPosition ) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~ /usr/local/boost_1_50_0/boost/statechart/detail/leaf_state.hpp:53:44: error: no type named 'iterator' in 'std::__1::list<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, std::__1::allocator<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>>>' typename base_type::state_list_type::iterator & statesEnd, ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~ /usr/local/boost_1_50_0/boost/statechart/detail/leaf_state.hpp:73:42: error: no type named 'iterator' in 'std::__1::list<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, std::__1::allocator<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>>>' typename base_type::state_list_type::iterator listPosition_; ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~ In file included from /Users/developer/Downloads/Sandbox/Sandbox/main.cpp:12: In file included from /usr/local/boost_1_50_0/boost/statechart/state.hpp:11: /usr/local/boost_1_50_0/boost/statechart/simple_state.hpp:505:27: error: no type named 'direct_state_base_ptr_type' in 'boost::statechart::detail::rtti_policy::rtti_derived_type<InitialState, boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>' typename base_type::direct_state_base_ptr_type & pSelf, ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~ /Users/developer/Downloads/Sandbox/Sandbox/main.cpp:25:29: note: in instantiation of template class 'boost::statechart::simple_state<InitialState, StateMachine, boost::mpl::list<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>, 0>' requested here class InitialState : public boost::statechart::simple_state<InitialState, StateMachine> ^ In file included from /Users/developer/Downloads/Sandbox/Sandbox/main.cpp:12: In file included from /usr/local/boost_1_50_0/boost/statechart/state.hpp:11: In file included from /usr/local/boost_1_50_0/boost/statechart/simple_state.hpp:11: In file included from /usr/local/boost_1_50_0/boost/statechart/event.hpp:11: In file included from /usr/local/boost_1_50_0/boost/statechart/event_base.hpp:15: In file included from /usr/local/boost_1_50_0/boost/intrusive_ptr.hpp:16: /usr/local/boost_1_50_0/boost/smart_ptr/intrusive_ptr.hpp:96:23: error: no matching function for call to 'intrusive_ptr_release' if( px != 0 ) intrusive_ptr_release( px ); ^~~~~~~~~~~~~~~~~~~~~ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/memory:1621:23: note: in instantiation of member function 'boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy> >::~intrusive_ptr' requested here __p->~_Tp(); ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/memory:1522:14: note: in instantiation of function template specialization 'std::__1::allocator_traits<std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>> >::__destroy<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>> >' requested here {__destroy(__has_destroy<allocator_type, _Tp*>(), __a, __p);} ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/list:685:34: note: in instantiation of function template specialization 'std::__1::allocator_traits<std::__1::allocator<std::__1::__list_node<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, void *>> >::destroy<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>> >' requested here __node_alloc_traits::destroy(__na, _VSTD::addressof(__n.__value_)); ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/list:664:5: note: in instantiation of member function 'std::__1::__list_imp<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, std::__1::allocator<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>> >::clear' requested here clear(); ^ /Developer4/Xcode45-DP2.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../lib/c++/v1/list:769:23: note: in instantiation of member function 'std::__1::__list_imp<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>, std::__1::allocator<boost::intrusive_ptr<boost::statechart::detail::leaf_state<std::__1::allocator<void>, boost::statechart::detail::rtti_policy>>> >::~__list_imp' requested here class _LIBCPP_VISIBLE list ^ /Users/developer/Downloads/Sandbox/Sandbox/main.cpp:20:5: note: in instantiation of member function 'boost::statechart::state_machine<StateMachine, InitialState, std::__1::allocator<void>, boost::statechart::null_exception_translator>::state_machine' requested here StateMachine() ^ /usr/local/boost_1_50_0/boost/statechart/detail/state_base.hpp:165:13: note: candidate template ignored: failed template argument deduction inline void intrusive_ptr_release( ^ 6 errors generated. *** So, it looks like it became boost's problem. Any help? WBR, Anton.

1 0

[statechart] history in the different state hierarchies
by Vlad Orlov 02 Jul '12

02 Jul '12

Hello everybody. I have a problem similar to the one described in the Statechart tutorial, but a little different. My state machine has two states (let's call them A and B) in the different state hierarchies and a third state C that can be transited to from either A or B. The transition from C must be done to either A or B, depending on where we came to C from. So I've decided to use the history. The difference between this problem and what's described in the tutorial is that A and B don't belong to the same composite state (they only belong to the same state machine). I can't simply declare "has_xxx_history" in the outer state like it's done in the tutorial. Here's what I've tried to do: #include <iostream> #include <boost/statechart/shallow_history.hpp> #include <boost/statechart/simple_state.hpp> #include <boost/statechart/state_machine.hpp> #include <boost/statechart/transition.hpp> namespace sc = boost::statechart; // events struct transfer_to_B : sc::event<transfer_to_B> {}; struct visit_C : sc::event<visit_C> {}; struct exit_to_history : sc::event<exit_to_history> {}; // forward declarations struct state_A; struct substate_A; struct substate_B; struct state_C; // state machine struct test_fsm : sc::state_machine<test_fsm, state_A> {}; // composite state A struct state_A : sc::simple_state<state_A, test_fsm, substate_A, sc::has_shallow_history> {}; struct substate_A : sc::simple_state<substate_A, state_A> { typedef boost::mpl::list < sc::transition<transfer_to_B, substate_B> , sc::transition<visit_C, state_C> > reactions; substate_A() { std::cout << "Entered A" << std::endl; } ~substate_A() { std::cout << "Exited A" << std::endl; } }; // composite state B struct state_B : sc::simple_state<state_B, test_fsm, substate_B, sc::has_shallow_history> {}; struct substate_B : sc::simple_state<substate_B, state_B> { typedef sc::transition<visit_C, state_C> reactions; substate_B() { std::cout << "Entered B" << std::endl; } ~substate_B() { std::cout << "Exited B" << std::endl; } }; // simple state C struct state_C : sc::simple_state<state_C, test_fsm> { typedef sc::transition < exit_to_history, sc::shallow_history<substate_A> > reactions; state_C() { std::cout << "Entered C" << std::endl; } ~state_C() { std::cout << "Exited C" << std::endl; } }; int main() { test_fsm fsm; fsm.initiate(); fsm.process_event(visit_C()); fsm.process_event(exit_to_history()); fsm.process_event(transfer_to_B()); fsm.process_event(visit_C()); fsm.process_event(exit_to_history()); } Unfortunately, this doesn't work as intended. The transition to history always leads to substate_A and never to substate_B: Entered A Exited A Entered C Exited C Entered A Exited A Entered B Exited B Entered C Exited C Entered A Exited A Can anyone please clarify if I've got something wrong or made a mistake somewhere? Is history supposed to work in the different state hierarchies?

2 2