On Thu, 3 Jul 2008, Steven Watanabe wrote:
Exactly the same errors? Including the third line of the error message? I've marked that parts I would expect to be different.
/usr/local/include/boost-1_35/boost/bind/bind_template.hpp:15: instantiated from ?boost::_bi::bind_t< **boost::_bi::unspecified** // void?? , void (com_client::*)(command_t, const boost::system::error_code&, boost::asio::ip::basic_resolver_iterator<boost::asio::ip::tcp>), //Something involving _mfi::?? ^^^^^^^^^^^ boost::_bi:: list3<boost::_bi::value<com_client*>, boost::arg<1> (*)(), boost::_bi:: value<boost::asio::ip::basic_resolver_iterator<boost::asio::ip::tcp>
?
Thank you for taking your time to solve my problem. I've reproduced the output. Apparently, all of the outputs are the same. ------------------------------------------------------- core dev/uleDFS/uleDFS% diff original.txt explicit.txt core dev/uleDFS/uleDFS% diff original.txt mem_fn.txt -------------------------------------------------------
What is the type of boost::mem_fn(&com_client::handle_connect)? I usually get this information using
# include <boost/mpl/assert.hpp> # include <boost/type_traits/is_same.hpp>
BOOST_MPL_ASSERT((boost::is_same<__typeof__(boost::mem_fn(&com_client::handle_connect)), void>)) ;
I've added the code with the following results: ---------------------------------------------------------------------- ../intercom/com_client.cpp:40: error: no matching function for call to âassertion_failed(mpl_::failed************ boost::is_same<boost::_mfi::mf3<void, com_client, command_t, const boost::system::error_code&, boost::asio::ip::basic_resolver_iterator<boost::asio::ip::tcp> >, void>::************)â ---------------------------------------------------------------------- Since I am not familiar with static assertion macros, I have no clue why it is complaining about 'no matching function for call'. -V