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

Caching the iterator of async_resolve()?
by Kaspar Fischer 18 Dec '13

18 Dec '13

Hi everybody, Just to be on the safe side: I assume that I can cache the iterator returned by async_resolve<http://www.boost.org/doc/libs/1_49_0/doc/html/boost_asio/reference/ip__basi…>'s handler, correct? The fact that it's a forward iterator suggests so... Thanks! Kaspar

2 4

[MPL] How to generate pre-generated header files for a mpl::list containing more than 50 entries?
by Klaus.Kempf＠industronic.de 18 Dec '13

18 Dec '13

Hello MPL experts, I want to code a state machine which has a reaction list containing more than 50 entries. I found here [http://svn.boost.org/svn/boost/trunk/libs/mpl/preprocessed/] some python scripts to generate header files for a mpl::list containing more than 50 entries. But I cannot manage to generate a single header file. Can someone please explain to me how to use these scripts? I also didn't find any help in boost documention. Command line messages of the related script were also not helpful for me: preprocess_list.py Usage: preprocess_list.py <mode> <boost_root> [<source_file>] Purpose: updates preprocessed version(s) of the header(s) in "boost\mpl\list\aux_\preprocessed" directory Example: the following command will re-generate and update all 'apply.hpp' headers: preprocess_list.py all f:\cvs\boost apply.cpp What is the meaning of [<source_file>] here? And how/where do I have to specify the count of list entries in order to generate the header files "list60.hpp", "list70.hpp" and so on? Many thanks for any help you could provide. Best regards, Klaus

2 1

async_send handler problem
by Alexander Carôt 17 Dec '13

17 Dec '13

Hello all, I am new to boost and asio in particular. For now I am implementing a simple UDP sender. The sending process itself works fine but for some reason the send handler does not execute. The call itself looks like this: In my class sender.cpp I have a functions called void sender::sendIt(){ sj->dFC->s->async_send_to(boost::asio::buffer( this->charBuffer,sendBytes), *sj->dFC->e, boost::bind(&sender::sendHandler,this, boost::asio::placeholders::error, boost::asio::placeholders::bytes_transferred); } and the corresponding handler is this: void sender::sendHandler(const boost::system::error_code& error,std::size_t bytes_transferred){ cout << "TRIGGER" << endl; } Can anyone give me a hint what the reason for the not-working handler might be ? Thanks in advance, best Alex

5 16

[Asio] io_service(std::size_t concurrency_hint) constructor
by maks 16 Dec '13

16 Dec '13

Hello All In what cases using "io_service(std::size_t concurrency_hint)" ctor is more effective? 1. Use multiple threads - multiple io_service 2. Use multiple threads on one io_service object Thanks.

2 1

Delegating to boost::function with arbitrary signature
by Alexander Lamaison 16 Dec '13

16 Dec '13

I've asked this question on Stack Overflow but not found a solution yet: http://stackoverflow.com/q/20578575/67013. It's Boost.Function/MPL-related so I'll ask here too. I'm trying to create something like a `boost::function`, but with an extra 'smart handle' tucked inside, which controls the lifetime of a resource the functions needs to execute correctly. If I didn't need the function signature to be completely generic, this would be easy. I would just create a functor with the correct signature, and keep a `boost::function` and the handle as members. However, I do need generic signatures. The code below is as close as I've got but gets a compile error, presumably, because I'm not able to unpack a list of arguments like this: template<typename Signature> class library_function { public: library_function( library_handle handle, boost::function<result_type(arg1_type, arg2_type)> function) : m_handle(handle), m_function(function) {} typename result_type operator()(arg1_type arg1, arg2_type arg2) { return m_function(arg1, arg2); } // I don't think I can declare the 'params' like this ... typename boost::function_types::result_type<Signature>::type operator()( boost::function_types::parameter_types<Signature> params) { return m_function(params); // ... nor unpack them like this } private: boost::function<Signature> m_function; library_handle m_library; }; I think `params` is an MPL list, so what I've actually done is declare a call operator with a single MPL-list parameter. My MPL-foo is not good. Is there a way to convert the list to a legal definition of multiple function paramters? A suggested solution on SO is to use `boost::bind`, but I still don't see how to bind an arbitrary number of arguments. All advice greatly appreciated. Alex -- Swish - Easy SFTP for Windows Explorer (http://www.swish-sftp.org)

4 9

[asio][openssl]Boost SSL with Visual Studio 2012 and OpenSSL
by lx 16 Dec '13

16 Dec '13

hello: I use : windows 7 64bit, vs 2012 , boost 1.5.4 , Win64OpenSSL_Light-1_0_1e. the codes is: ######################## #include <boost/asio.hpp> #include <boost/asio/ssl.hpp> ######################## When I complie it, the wrong messages is: ########################################## 1>gtest.obj : error LNK2019: unresolved external symbol _CRYPTO_cleanup_all_ex_data referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::~do_init(void)" (??1do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _CRYPTO_num_locks referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::do_init(void)" (??0do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _CRYPTO_set_locking_callback referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::do_init(void)" (??0do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _CRYPTO_set_id_callback referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::do_init(void)" (??0do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _CONF_modules_unload referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::~do_init(void)" (??1do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _OPENSSL_add_all_algorithms_noconf referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::do_init(void)" (??0do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _EVP_cleanup referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::~do_init(void)" (??1do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _SSL_load_error_strings referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::do_init(void)" (??0do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _SSL_library_init referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::do_init(void)" (??0do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _ERR_reason_error_string referenced in function "public: virtual class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > __thiscall boost::asio::error::detail::ssl_category::message(int)const " (?message@ssl_category@detail@error@asio@boost@@UBE?AV?$basic_string@DU ?$char_traits@D@std@@V?$allocator@D@2@@std@@H@Z) 1>gtest.obj : error LNK2019: unresolved external symbol _ERR_free_strings referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::~do_init(void)" (??1do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _ERR_remove_state referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::~do_init(void)" (??1do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>gtest.obj : error LNK2019: unresolved external symbol _ENGINE_cleanup referenced in function "public: __thiscall boost::asio::ssl::detail::openssl_init_base::do_init::~do_init(void)" (??1do_init@openssl_init_base@detail@ssl@asio@boost@@QAE@XZ) 1>D:\program\gdnscenter-1.12.2\src\Debug\gtest.exe : fatal error LNK1120: 13 unresolved externals ========== Build: 0 succeeded, 1 failed, 3 up-to-date, 0 skipped ========== ########################################## the simiar question in stackoverflow : http://stackoverflow.com/questions/9357751/boost-ssl-with-visual-studio-201… . I use the openssl win64. So, Maybe a bug in asio? Thank you.

2 1

Crash in VS2013, bug in compiler, boost or my code ? (flyweight, variant and initializer list)
by Olivier Tristan 16 Dec '13

16 Dec '13

Hello Boost users, Using the following sample code I have some crash in VS2013 but it works fine in LLVM on OSX Is this is a mistake on my side or an issue elsewhere ? #include <string> #include <cstdint> #include <vector> #include <boost/flyweight/flyweight.hpp> #include <boost/flyweight/no_tracking.hpp> #include <boost/flyweight/static_holder.hpp> #include <boost/flyweight/set_factory.hpp> #include <boost/flyweight/simple_locking.hpp> #include <boost/variant.hpp> typedef boost::flyweights::flyweight< std::string, boost::flyweights::no_tracking, boost::flyweights::set_factory<>, boost::flyweights::static_holder, boost::flyweights::simple_locking > string_flyweight; typedef boost::variant< bool, double, string_flyweight > Variant; int main(void) { std::vector<Variant> v = { 1., true, string_flyweight("toto") }; return 0; } Thanks, -- Olivier TRISTAN uvi.net

5 8

library choice
by Mihir Thakkar 15 Dec '13

15 Dec '13

I am new to boost. I would like to contribute to development. I looked through the libraries and got confused from where to start understanding and reading such a large codebase. Is it that all the libraries are independent of each other and I've to look at only those which I want to work with? Please guide me on how to begin understanding. Thanks! :)

3 2

Boost Geometry - RTree with 1D Segments
by Adam Baxter 13 Dec '13

13 Dec '13

Hello all, I've been using boost::icl for interval searching. So far it's been working great. I am using it for closed interval searches for chemical masses. Unfortunately, I've reached a point where I've too much data, I think. The use of sets has started to kill my memory usage. I'd like to switch over to Boost::Geometry, but there's precious little about indexing 1D segments (I don't even mind 2D segments). Can someone point me in the right direction? Thanks! Adam

1 0

Threading question
by Davies, John 13 Dec '13

13 Dec '13

I have the following code and it terminates as expected. When I call the destructor it interrupts the thread. But if I change the this_thread::sleep to this_thread::yield the join() never happens and the program hangs. I must be misunderstanding yield. But I really don't want a sleep if possible. Thanks, John MessageQueueHandler::~MessageQueueHandler() { // Terminate the thread pMessageQueueInputThread->interrupt(); pMessageQueueInputThread->join(); delete pMessageQueueInputThread; } void MessageQueueHandler::MessageQueueInputThread() { unsigned int receivedSize; unsigned int priority; char buffer[queueMaximumMessageSize]; boost::this_thread::interruption_enabled(); try { while(1) { // Process all messages in the queue while(inputMessageQueue->try_receive(buffer, queueMaximumMessageSize, receivedSize, priority)) { BaseMessage * msg = reinterpret_cast<BaseMessage*>(buffer); callbackTable->DispatchMessage(msg); boost::this_thread::interruption_point(); } // Give other threads a chance to run // This is also an interruption point boost::this_thread::sleep(boost::posix_time::millisec(50)); <==Here } } catch(boost::thread_interrupted const&) { return; } } ___________________________________ John Davies Contractor Home Respiratory Care Philips Home Healthcare Solutions 1740 Golden Mile Highway Monroeville, PA 15146 Email: john.davies(a)philips.com Fax: 724-387-4109 ________________________________ The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

4 5