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

Build boost 1.52 on Mac OS X 10.8.2 with Clang c++11
by Kikohs x 15 Nov '12

15 Nov '12

Hello, I cannot compile boost with clang 3.1 on Mac os x 10.8.2. This is what I did: ./boostrap.sh --with-toolset=clang ./b2 toolset=clang cxxflags="-std=c++11 -stdlib=libc++" linkflags="-stdlib=libc++" I also tried without chrono, test, wave and signals. I tried a user-config.jam with using clang-darwin This is the error I have for almost every file: /boost/config/select_stdlib_config.hpp:18:12: fatal error: 'cstddef' file not found It is kind of similar to [ http://stackoverflow.com/questions/8486077/how-to-compile-link-boost-with-c… ] I do have the latest Xcode 4.5.2 with the command line tools installed. Here is part of the console output: Kikohs:trunk kikohs$ ./b2 toolset=clang cxxflags="-std=c++11 -stdlib=libc++" linkflags="-stdlib=libc++" Performing configuration checks - 32-bit : no - 64-bit : yes - x86 : yes - has_icu builds : no warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - gcc visibility : yes - long double support : no warning: skipping optional Message Passing Interface (MPI) library. note: to enable MPI support, add "using mpi ;" to user-config.jam. note: to suppress this message, pass "--without-mpi" to bjam. note: otherwise, you can safely ignore this message. Building the Boost C++ Libraries. - iconv (libc) : no - iconv (separate) : yes - icu : no - icu (lib64) : no Component configuration: - atomic : building - chrono : building - context : building - date_time : building - exception : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - signals : building - system : building - test : building - thread : building - timer : building - wave : building ...patience... ...patience... ...patience... ...patience... ...found 8672 targets... ...updating 1127 targets... common.mkdir bin.v2/libs/atomic common.mkdir bin.v2/libs/atomic/build common.mkdir bin.v2/libs/atomic/build/clang-darwin-4.2.1 common.mkdir bin.v2/libs/atomic/build/clang-darwin-4.2.1/debug clang-darwin.compile.c++ bin.v2/libs/atomic/build/clang-darwin-4.2.1/debug/lockpool.o In file included from libs/atomic/src/lockpool.cpp:1: ./boost/atomic.hpp:10:10: fatal error: 'cstddef' file not found #include <cstddef> ^ 1 error generated. "clang++" -x c++ -O0 -g -std=c++11 -stdlib=libc++ -O0 -fno-inline -Wall -g -DBOOST_ALL_NO_LIB=1 -DBOOST_ATOMIC_DYN_LINK=1 -DBOOST_ATOMIC_SOURCE -I"." -c -o "bin.v2/libs/atomic/build/clang-darwin-4.2.1/debug/lockpool.o" "libs/atomic/src/lockpool.cpp" Any help would be greatly appreciated, Thank you, Kikohs

2 2

A Special Note for Boost 1.52.0 and Higher - how this affects me?
by Adam Romanek 15 Nov '12

15 Nov '12

Hi, I've just read the Special Note for Boost 1.52.0 and Higher. I must say that I don't fully understand what's going on and how this affects me. I'm using some of Boost's libraries with gcc on Ubuntu. Most often it's gcc 4.4.3, sometimes 4.6.3 but without C++0x mode. Does the change in boost::result_of affect me in any way? Can it make my code fail to compile or make it behave in a different way than before? I just don't understand whether a switch from Boost 1.51.0 to 1.52.0 may do any harm to my code. WBR, Adam Romanek

3 2

[fusion] remove_if and as_vector with Placeholder Expression as predicate
by Felipe Magno de Almeida 15 Nov '12

15 Nov '12

Hello, I'm trying to remove_if a few elements from a fusion sequence. But it is instantiating my predicate with the placeholder from MPL later on. Including with as_vector. The following code generates the error code I'm pasting by the end of the message. I'm using GCC 4.7.2 and Linux x86_64. If I wrap meta_func<mpl::_1> in a mpl::lambda<>::type then the errors following the first error messages is what I get. I'm not sure if I'm doing something wrong here. If anyone could please shed some light, I would really appreciate it. #include <boost/fusion/include/as_vector.hpp> #include <boost/fusion/include/remove_if.hpp> namespace mpl = boost::mpl; namespace fusion = boost::fusion; struct element { typedef mpl::false_ type; }; template <typename T> struct meta_func { typedef typename T::type type; }; int main() { fusion::vector<element, element> e; fusion::as_vector(fusion::remove_if<meta_func<mpl::_1> >(e)); } -- main.cpp: In instantiation of ‘struct meta_func<mpl_::arg<1> >’: ../boost/boost_1_51_0/boost/mpl/aux_/nested_type_wknd.hpp:26:31: required from ‘struct boost::mpl::aux::nested_type_wknd<meta_func<mpl_::arg<1> > >’ ../boost/boost_1_51_0/boost/mpl/not.hpp:39:8: required from ‘struct boost::mpl::not_<meta_func<mpl_::arg<1> > >’ ../boost/boost_1_51_0/boost/fusion/container/vector/detail/preprocessed/as_vector10.hpp:48:36: required from ‘static typename boost::fusion::detail::as_vector<2>::apply<I0>::type boost::fusion::detail::as_vector<2>::call(const Iterator&) [with Iterator = boost::fusion::filter_iterator<boost::fusion::forward_traversal_tag, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0>, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 2>, boost::mpl::not_<meta_func<mpl_::arg<1> > > >; typename boost::fusion::detail::as_vector<2>::apply<I0>::type = boost::fusion::vector2<element, element>]’ ../boost/boost_1_51_0/boost/fusion/container/vector/convert.hpp:43:44: required from ‘typename boost::fusion::result_of::as_vector<const Sequence>::type boost::fusion::as_vector(const Sequence&) [with Sequence = boost::fusion::filter_view<const boost::fusion::vector<element, element>, boost::mpl::not_<meta_func<mpl_::arg<1> > > >; typename boost::fusion::result_of::as_vector<const Sequence>::type = boost::fusion::vector2<element, element>]’ main.cpp:22:62: required from here main.cpp:16:28: error: no type named ‘type’ in ‘struct mpl_::arg<1>’ In file included from ../boost/boost_1_51_0/boost/mpl/is_sequence.hpp:17:0, from ../boost/boost_1_51_0/boost/fusion/support/detail/is_mpl_sequence.hpp:12, from ../boost/boost_1_51_0/boost/fusion/support/tag_of.hpp:13, from ../boost/boost_1_51_0/boost/fusion/iterator/next.hpp:10, from ../boost/boost_1_51_0/boost/fusion/container/vector/vector10.hpp:13, from ../boost/boost_1_51_0/boost/fusion/container/vector/vector_fwd.hpp:14, from ../boost/boost_1_51_0/boost/fusion/container/vector/vector.hpp:10, from ../boost/boost_1_51_0/boost/fusion/container/vector/detail/as_vector.hpp:18, from ../boost/boost_1_51_0/boost/fusion/container/vector/convert.hpp:10, from ../boost/boost_1_51_0/boost/fusion/include/as_vector.hpp:10, from main.cpp:2: ../boost/boost_1_51_0/boost/mpl/not.hpp: In instantiation of ‘struct boost::mpl::not_<meta_func<mpl_::arg<1> > >’: ../boost/boost_1_51_0/boost/fusion/container/vector/detail/preprocessed/as_vector10.hpp:48:36: required from ‘static typename boost::fusion::detail::as_vector<2>::apply<I0>::type boost::fusion::detail::as_vector<2>::call(const Iterator&) [with Iterator = boost::fusion::filter_iterator<boost::fusion::forward_traversal_tag, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0>, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 2>, boost::mpl::not_<meta_func<mpl_::arg<1> > > >; typename boost::fusion::detail::as_vector<2>::apply<I0>::type = boost::fusion::vector2<element, element>]’ ../boost/boost_1_51_0/boost/fusion/container/vector/convert.hpp:43:44: required from ‘typename boost::fusion::result_of::as_vector<const Sequence>::type boost::fusion::as_vector(const Sequence&) [with Sequence = boost::fusion::filter_view<const boost::fusion::vector<element, element>, boost::mpl::not_<meta_func<mpl_::arg<1> > > >; typename boost::fusion::result_of::as_vector<const Sequence>::type = boost::fusion::vector2<element, element>]’ main.cpp:22:62: required from here ../boost/boost_1_51_0/boost/mpl/not.hpp:39:8: error: ‘value’ is not a member of ‘boost::mpl::aux::nested_type_wknd<meta_func<mpl_::arg<1> > >’ -- -*- mode: compilation; default-directory: "~/dev/test/" -*- Compilation started at Mon Nov 12 15:09:15 bjam -q -j8 ...patience... ...found 584 targets... ...updating 2 targets... gcc.compile.c++ bin/gcc-4.7.2/debug/main.o In file included from ../boost/boost_1_51_0/boost/mpl/is_sequence.hpp:17:0, from ../boost/boost_1_51_0/boost/fusion/support/detail/is_mpl_sequence.hpp:12, from ../boost/boost_1_51_0/boost/fusion/support/tag_of.hpp:13, from ../boost/boost_1_51_0/boost/fusion/iterator/next.hpp:10, from ../boost/boost_1_51_0/boost/fusion/container/vector/vector10.hpp:13, from ../boost/boost_1_51_0/boost/fusion/container/vector/vector_fwd.hpp:14, from ../boost/boost_1_51_0/boost/fusion/container/vector/vector.hpp:10, from ../boost/boost_1_51_0/boost/fusion/container/vector/detail/as_vector.hpp:18, from ../boost/boost_1_51_0/boost/fusion/container/vector/convert.hpp:10, from ../boost/boost_1_51_0/boost/fusion/include/as_vector.hpp:10, from main.cpp:2: ../boost/boost_1_51_0/boost/mpl/not.hpp: In instantiation of ‘struct boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> >’: ../boost/boost_1_51_0/boost/mpl/aux_/preprocessed/gcc/apply_wrap.hpp:36:8: required from ‘struct boost::mpl::apply_wrap1<boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> >, element>’ ../boost/boost_1_51_0/boost/mpl/aux_/preprocessed/gcc/bind.hpp:144:21: required from ‘struct boost::mpl::bind1<boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> >, boost::mpl::bind1<boost::mpl::quote1<boost::fusion::result_of::value_of>, mpl_::arg<1> > >::apply<boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0> >’ ../boost/boost_1_51_0/boost/mpl/aux_/preprocessed/gcc/apply_wrap.hpp:36:8: required from ‘struct boost::mpl::apply_wrap1<boost::mpl::bind1<boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> >, boost::mpl::bind1<boost::mpl::quote1<boost::fusion::result_of::value_of>, mpl_::arg<1> > >, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0> >’ ../boost/boost_1_51_0/boost/mpl/aux_/preprocessed/gcc/apply.hpp:42:8: required from ‘struct boost::mpl::apply1<boost::mpl::bind1<boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> >, boost::mpl::bind1<boost::mpl::quote1<boost::fusion::result_of::value_of>, mpl_::arg<1> > >, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0> >’ ../boost/boost_1_51_0/boost/fusion/algorithm/query/detail/find_if.hpp:33:35: required from ‘struct boost::fusion::detail::apply_filter<boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0>, boost::mpl::bind1<boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> >, boost::mpl::bind1<boost::mpl::quote1<boost::fusion::result_of::value_of>, mpl_::arg<1> > > >’ ../boost/boost_1_51_0/boost/mpl/if.hpp:67:11: [ skipping 10 instantiation contexts ] ../boost/boost_1_51_0/boost/fusion/support/tag_of.hpp:69:16: required from ‘struct boost::fusion::traits::tag_of<boost::fusion::filter_iterator<boost::fusion::forward_traversal_tag, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0>, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 2>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > >, void>’ ../boost/boost_1_51_0/boost/fusion/support/tag_of.hpp:77:16: required from ‘struct boost::fusion::detail::tag_of<boost::fusion::filter_iterator<boost::fusion::forward_traversal_tag, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0>, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 2>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > > >’ ../boost/boost_1_51_0/boost/fusion/iterator/distance.hpp:60:16: required from ‘struct boost::fusion::result_of::distance<boost::fusion::filter_iterator<boost::fusion::forward_traversal_tag, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 0>, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 2>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > >, boost::fusion::filter_iterator<boost::fusion::forward_traversal_tag, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 2>, boost::fusion::vector_iterator<const boost::fusion::vector<element, element>, 2>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > > >’ ../boost/boost_1_51_0/boost/fusion/view/filter_view/detail/size_impl.hpp:27:20: required from ‘struct boost::fusion::extension::size_impl<boost::fusion::filter_view_tag>::apply<const boost::fusion::filter_view<const boost::fusion::vector<element, element>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > > >’ ../boost/boost_1_51_0/boost/fusion/sequence/intrinsic/size.hpp:68:16: required from ‘struct boost::fusion::result_of::size<const boost::fusion::filter_view<const boost::fusion::vector<element, element>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > > >’ ../boost/boost_1_51_0/boost/fusion/container/vector/convert.hpp:23:82: required from ‘struct boost::fusion::result_of::as_vector<const boost::fusion::filter_view<const boost::fusion::vector<element, element>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > > >’ ../boost/boost_1_51_0/boost/fusion/container/vector/convert.hpp:40:5: required by substitution of ‘template<class Sequence> typename boost::fusion::result_of::as_vector<const Sequence>::type boost::fusion::as_vector(const Sequence&) [with Sequence = boost::fusion::filter_view<const boost::fusion::vector<element, element>, boost::mpl::not_<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> > >]’ main.cpp:22:81: required from here ../boost/boost_1_51_0/boost/mpl/not.hpp:39:8: error: ‘value’ is not a member of ‘boost::mpl::aux::nested_type_wknd<boost::mpl::protect<boost::mpl::bind1<boost::mpl::quote1<meta_func, mpl_::void_>, mpl_::arg<1> >, 0> >’ Thanks in advance, -- Felipe Magno de Almeida

4 4

Am I building 64-bit Boost correctly?
by Ramon F Herrera 15 Nov '12

15 Nov '12

I have finally decided to get my feet wet, when it comes to the 64-bit world. Honestly, all my fears turned out to be valid, and then some. I have a MSVS-2010 Solution that includes several varied projects: GUI, libraries (both kids) and Shell Extensions. Since a couple of my projects depend on Boost (the greatest set of libraries ever known to man! Boost rocks! Boost rules!!... but I digress): I decided to start there. Since I am getting some boost-related error messages, I figure that step number zero is to make sure that my Boost installation is healthy. This is how I build it: .\bootstrap.bat .\bjam.exe --with-date_time --with-filesystem --with-regex --with-system --stagedir=. --build-type=complete toolset=msvc-10.0 address-model=64 Notice that the above commands have served me well for years (minus the last parameter, which I am now using for the first time). Is that all I need? TIA, -Ramon

4 5

read_graphml: read more than 1 graph from the same graphml file
by Bartha Attila 15 Nov '12

15 Nov '12

Hello ! Is there a way a to read more than one graph from a .graphml file using read_graphml ? Here's what I tried: -open an input stream to the graphml file; -call a function to read the graph from the file (the function uses read_graphml) and print the graph to stdout; -call the same function again, hoping that the second graph from the file will be read; -close the file input stream. If I call the function once, it works fine and returns the first graph defined in the graphml file. If I call the function the twice, I get the following runtime exception: 'boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::property_tree::ptree_bad_path> >' what(): No such node (graphml) The graphml file looks like this : <graphml ....header stuff... > <key id= ...key definitions...> <graph id="TestSite1" edgedefault="undirected"> <node id="node0"> <data key="map">map1</data> <data key="x">5.0</data> <data key="y">1.0</data> </node> <node id="node1"> <data key="map">map1</data> <data key="x">5.0</data> <data key="y">4.0</data> </node> <edge source="node0" target="node1"/> </graph> <graph id="TestSite2" edgedefault="undirected"> <node id="node0"> <data key="map">map3</data> <data key="x">6.0</data> <data key="y">2.0</data> </node> <node id="node1"> <data key="map">map4</data> <data key="x">7.0</data> <data key="y">9.0</data> </node> <edge source="node0" target="node1"/> </graph></graphml> I can correctly get the data of TestSite1 graph if I call the function once. How can I get the TestSite2 graph from the same file, or, for that matter, how can I get one specific graph (ex TestSiteN) ? Thanx for any help, -attoparsec-

2 2

Further Boost.MPI development
by Matthias Troyer 15 Nov '12

15 Nov '12

Dear Boost.MPI users, With the MPI-3 standard having been finalized we want to intensify Boost.MPI development as soon as my crazy teaching schedule this fall gives me time from the middle of next month. With the deprecation of the - little used - official MPI C++ API in MPI-3 Boost.MPI has a chance of becoming a de facto standard C++ API for MPI. We first want to focus on features from MPI-2 and MPI-3 that are widely used or useful. For this purpose I would like to collect suggestions. Can you please reply and mention the functions of MPI that you would most like to see supported by Boost.MPI. Best regards Matthias

6 5

[coroutine] errors compiling with clang 3.2
by Marco Craveiro 14 Nov '12

14 Nov '12

Hi boost-users, As reported by Eugene Yakubovich[1], I am seeing problems compiling boost coroutine with clang 3.1 on debian testing. I got my sources from git://gitorious.org/boost-dev/boost-dev.git at commit c083660c54b88ca1ce9a940f4a71bc6c3ab89003. The error I get is: /boost/coroutine/detail/coroutine_object.hpp:54:46: error: expected expression Context * ctx( hldr->data.get().get< 0 >() ); ^ The same code compiles and runs fine with gcc 4.7. In both cases I'm using C++11. I just want to double-check that this is some kind of problem with clang - since 3.2 is on the wings I was wondering if this would be resolved by the upgrade. If anyone has managed to get it working with 3.1 I'd appreciate some pointers. Many thanks for your time, Marco -- So young, and already so unknown -- Pauli blog: http://mcraveiro.blogspot.com [1] http://boost.2283326.n4.nabble.com/Review-Coroutine-reviewstarts-today-Sept…

2 6

boost asio: boost::asio::deadline_timer blocking ?
by Avi Bahra 14 Nov '12

14 Nov '12

Answers: 1. I doubt this is really an issue is with deadline_timer accuracy. 2. Are you double-scheduling the same timer? Or are you just doing some extra work, every time a single expiry event crosses a minute boundary? I wouldn't double-schedule the same timer, if that's what you're doing. >> No. I record the next minute boundary, when the timer fires, I check the current >> time against the minute boundary. So no double scheduling. 3. The timer may be susceptible to time changes on your system. It needn't be, but don't assume that means it's not. It might be worth looking at the implementation, to make sure. >> The problem occurs independent of the time change. 4. Slow disk could be an issue, but only if your io_service thread(s) are blocking on disk activity (either direct disk access or page faults). The file descriptors you're talking about have nothing to do with disk files, in this case. >> The current server is single threaded, so my this was my first suspect. >> I log every client request to a log file. I had suspected that a slow >> file system, would block when logging the client request, and affect the timer. >> I added extra instrumentation to time the logging. However this was not the cause 5. Depends on your accuracy needs and the load on the rest of the system. On a system under moderate loads, I'd expect no problems using ASIO to perform processing on a one-second granularity. Just be sure to compute the next expiry based the current time, rather than sleeping for 1 second. If you want to make this resilient to time change, you can use a monotonic timebase. Matt ================================================================ The client is designed to cancel long running connection to the server.. ( > 20seconds) This timeout is based on boost asio example: http://www.boost.org/doc/libs/1_47_0/doc/html/boost_asio/example/timeouts/a… What I have noticed is that the 1 second timer in the server does not fire, *when* client request have been cancelled. It appears that some of chain of async handlers that are being called in the server, during this process, cause the timer to hang ? For example if the client cancels after 20 seconds, then something in the server must been blocking, for that period ? When the client cancels, the server::handle_write(..), closes both end of the socket. So I see the following message logged: shutdown: Transport endpoint is not connected Here is the async' functions in the server: void server::start_accept() { connection_ptr new_conn( new connection( io_service_ ) ); acceptor_.async_accept( new_conn->socket(), boost::bind( &server::handle_accept, this, boost::asio::placeholders::error, new_conn ) ); } void server::handle_accept( const boost::system::error_code& e, connection_ptr conn ) { if (!acceptor_.is_open()) { if (serverEnv_.debug()) cout << " server::handle_accept: acceptor is closed, returning\n"; return; } if ( !e ) { conn->async_read( inbound_request_, boost::bind( &server::handle_read, this, boost::asio::placeholders::error,conn ) ); } else { if (e != boost::asio::error::operation_aborted) { // An error occurred. Log it LogToCout toCoutAsWell; LOG(Log::ERR, " server::handle_accept error occurred " << e.message()); } } start_accept(); } void server::handle_read( const boost::system::error_code& e,connection_ptr conn ) { if ( !e ) { try { // Service the in bound request, handling the request will populate the outbound_response_ // Note:: Handle request will first authenticate outbound_response_.set_cmd( inbound_request_.handleRequest( this ) ); } catch (exception& e) { outbound_response_.set_cmd( PreAllocatedReply::error_cmd( e.what() )); } // *Reply* back to the client: conn->async_write( outbound_response_, boost::bind(&server::handle_write, this, boost::asio::placeholders::error, conn ) ); } else { LOG(Log::ERR, "server::handle_read error occurred : " << e.message()); } } void server::handle_write( const boost::system::error_code& e, connection_ptr conn ) { boost::system::error_code ec; conn->socket().shutdown(boost::asio::ip::tcp::socket::shutdown_both,ec); if (ec) { ecf::LogToCout logToCout; LOG(Log::ERR,"server::handle_write: socket shutdown both failed: " << ec.message()); return; } } I had noticed that I was not checking error code in the server::handle_write(..) but I'm not sure if this would account, for why the timer does not fire temporarily. Ta, Avi

1 0

[msm] Why does it take so many bytes to represent a state machine?
by ☂Josh Chia (谢任中) 13 Nov '12

13 Nov '12

Hi, I'm using msm to store the state of many small objects. Each one is around 24 bytes on its own. However, I just found out from experimentation that a MSM state machine takes many bytes to store. For the following program, the print out is: entering: State1 104 48 This indicates that the very simple one-state, no-transition, machine is 104 bytes, and takes 48 bytes even to serialized. The front::state_machine_def, however, is only 1 byte, though I suspect thet real state is stored only in the 104-byte back::state_machine. Even the SimpleTutorial.cpp example, when I adapt it to print the size, shows 128 bytes. Theoretically, all this information take no more than a few bits to store, and one byte is generous. What's the internal representation of a state machine and how can I optimize the size of the representation? This matters for my use case because I have many small objects for which I want to maintain state, that are only ~20 bytes each. I thought perhaps I could mitigate this size problem by storing the serialized bytes but even the serialized bytes are many. I'm using boost 1.51 and gcc 4.7.2 on 64-bit Linux. Josh #include <iostream> #include <strstream> #include <boost/archive/text_oarchive.hpp> #include <boost/msm/back/state_machine.hpp> #include <boost/msm/front/functor_row.hpp> #include <boost/msm/front/state_machine_def.hpp> using namespace std; namespace mpl = boost::mpl; namespace msm = boost::msm; using namespace msm::front; struct Event { }; struct state_ : public msm::front::state_machine_def<state_> { struct State1 : public msm::front::state<> { // optional entry/exit methods template <class Event,class FSM> void on_entry(Event const&, FSM& f) { std::cout << "entering: State1" << std::endl; } template <class Event,class FSM> void on_exit(Event const&,FSM& ) { std::cout << "leaving: State1" << std::endl; } }; typedef State1 initial_state; struct transition_table : mpl::vector< > {}; }; typedef msm::back::state_machine<state_> State; int main() { State state; state.start(); cout << sizeof(state) << endl; ostrstream os; { boost::archive::text_oarchive oa(os); oa << state; } cout << os.pcount() << endl; return 0; }

2 4

[msm] How to cause no_transition for cases of guard returning false?
by ☂Josh Chia (谢任中) 13 Nov '12

13 Nov '12

Hi, I want no_transition() to be called whenever no row matches, even if there is a row that does not match only because the guard returns false. How can I achieve this? I want to be strict about the input events. I can probably workaround this by putting guardless rows at the top whose action is to call no_transition(), but I'm hoping to find a cleaner solution. If I get this behavior in msm, then the following code should output "no transition..." as its last line. Right now, with boost 1.51, it doesn't. It just prints "entering State1". Josh #include <iostream> #include <boost/msm/back/state_machine.hpp> #include <boost/msm/front/functor_row.hpp> #include <boost/msm/front/state_machine_def.hpp> using namespace std; namespace mpl = boost::mpl; namespace msm = boost::msm; using namespace msm::front; struct Event { Event(bool data) : data(data) { } bool data; }; struct state_ : public msm::front::state_machine_def<state_> { struct MyGuard { template <class EVT, class FSM, class SourceState, class TargetState> bool operator()(EVT const& e, FSM&, SourceState&, TargetState&) { return e.data; } }; struct State1 : public msm::front::state<> { // optional entry/exit methods template <class Event,class FSM> void on_entry(Event const&, FSM& f) { std::cout << "entering: State1" << std::endl; } template <class Event,class FSM> void on_exit(Event const&,FSM& ) { std::cout << "leaving: State1" << std::endl; } }; struct State2 : public msm::front::state<> { // optional entry/exit methods template <class Event,class FSM> void on_entry(Event const&, FSM& f) { std::cout << "entering: State2" << std::endl; } template <class Event,class FSM> void on_exit(Event const&,FSM& ) { std::cout << "leaving: State2" << std::endl; } }; typedef State1 initial_state; struct transition_table : mpl::vector< Row< State1, Event , State2, none, MyGuard > > {}; template <class FSM, class Event> void no_transition(Event const& e, FSM&, int state) { std::cout << "no transition from state " << state << " on event " << typeid(e).name() << std::endl; } }; typedef msm::back::state_machine<state_> State; int main() { State state; state.start(); state.process_event(Event(false)); return 0; }

2 2