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

Using async_pipe as named pipe in windows
by parean 20 Mar '19

20 Mar '19

I have this code: boost::asio::io_service ios; std::vector<char> buf(20); bp::async_pipe ap(ios, "\\\\.\\pipe\\SamplePipe"); boost::asio::async_read(ap, boost::asio::buffer(buf), [](const boost::system::error_code &ec, std::size_t size) {}); ios.run(); Now, I execute "echo 42 > \\.\pipe\SamplePipe" in the cmd and expect an asynchronous read to the buffer to occur. But instead I get the following error: "All pipe instances are busy." I'm sure I'm doing something wrong. Can you please tell me what should I add to my code for it to work? -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

2 1

multi_index reserve but allocate
by Olivier Tristan 20 Mar '19

20 Mar '19

Hi, Looks like that even if I call reserve on a multi_index, it stills allocate memory while I am still below the reserve size. Is this the intended behavior ? If so, what is the best way to avoid allocation in a fixed sized multi_index Thanks ! -- Olivier Tristan Research & Development www.uvi.net

2 4

Call to boost::beast::http::write() Failing with Exception "Uninitialized"
by Osman Zakir 19 Mar '19

19 Mar '19

Hi, everyone. I really need some help here. I tried looking at the Boost documentation as well, but I only saw that "http::write" from Boost.Beast throws a "system_error" exception on failure. I can't figure out why it's failing or what exactly is uninitialized. I did look in the debugger and I added the SSL stream object and the request object to the watch to check their respective values. I have this source code file: https://github.com/DragonOsman/currency_converter/blob/master/currency_conv… and this is the root_certificate.hpp file: https://github.com/DragonOsman/currency_converter/blob/master/root_certific… . Is there anything wrong in the root certificate verification code and such in the header file? And I'm trying to make a HTTPS GET request in the functions "cache_storage::query_rate" and "cache_storage::query_list" using those certificates through SSL context but my try-catch block in that second-mentioned function is catching a "system_error" from "http::write()". The "what" string is "Uninitialized", and from looking at the HTTP request object's value member, I noticed that it's just an empty string. I also tried to print out the request body before but got nothing from the request object in my app's console window at all (by "console" I of course mean the kind opened for Windows Console Applications). So could it be that the request object is uninitialized? I have this for that: " std::string host{ "bankersalgo.com" }, api_endpoint{ "/currencies_list" }, key{ currencykey }; std::string target = api_endpoint + '/' + key; std::string port{ "443" }; int version = 11; " and " // Set up an HTTP GET request message http::request<http::string_body> req{ http::verb::get, target, version }; req.set(http::field::host, host); req.set(http::field::content_type, "application/json"); req.set(http::field::accept, "application/json"); req.set(http::field::user_agent, BOOST_BEAST_VERSION_STRING); //req.set(http::field::content_encoding, "gzip"); // Send the HTTP request to the remote host http::write(stream, req); " The line setting the content encoding is commented out because I wanted to see what happens if I don't set the encoding to "gzip" (on bankersalgo.com, it shows that the content encoding for the HTTP response for each request endpoint is "gzip"). Also it seems the call to "http::write()" isn't necessarily failing since I do get a "200 OK" response. There's just an empty string both for the request object value and request body, and for the response body. But is it really the request object that's uninitialized? If so, why? I did add the code to set and I also did it exactly as shown in the example. It's also possible that the stream is what's uninitialized since there's a pending read and a pending write on it and both of them have empty data objects. How do I fix this stuff? Someone please help. Full app source code is here: https://github.com/DragonOsman/currency_converter . My entire Watch in the debugger: " Name Value Type ◢ ctx {handle_=0x0000024ea54ca760 {method=0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {...} ...} ...} boost::asio::ssl::context boost::asio::ssl::context_base {...} boost::asio::ssl::context_base boost::asio::detail::noncopyable {...} boost::asio::detail::noncopyable ◢ handle_ 0x0000024ea54ca760 {method=0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {...} ...} ssl_ctx_st * ▶ method 0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {version=65536 flags=...} const ssl_method_st * cipher_list 0x0000024ea54882d0 {...} stack_st_SSL_CIPHER * cipher_list_by_id 0x0000024ea5488300 {...} stack_st_SSL_CIPHER * tls13_ciphersuites 0x0000024ea5488270 {...} stack_st_SSL_CIPHER * ◢ cert_store 0x0000024ea5488bc0 {cache=1 objs=0x0000024ea5488120 {...} get_cert_methods=0x0000024ea5488180 {...} ...} x509_store_st * cache 1 int objs 0x0000024ea5488120 {...} stack_st_X509_OBJECT * get_cert_methods 0x0000024ea5488180 {...} stack_st_X509_LOOKUP * ◢ param 0x0000024ea5472420 {name=0x0000000000000000 <NULL> check_time=0 inh_flags=0 ...} X509_VERIFY_PARAM_st * ▶ name 0x0000000000000000 <NULL> char * check_time 0 __int64 inh_flags 0 unsigned int flags 0 unsigned long purpose 0 int trust 0 int depth -1 int auth_level -1 int policies 0x0000000000000000 <NULL> stack_st_ASN1_OBJECT * hosts 0x0000000000000000 <NULL> stack_st_OPENSSL_STRING * hostflags 0 unsigned int ▶ peername 0x0000000000000000 <NULL> char * ▶ email 0x0000000000000000 <NULL> char * emaillen 0 unsigned __int64 ▶ ip 0x0000000000000000 <NULL> unsigned char * iplen 0 unsigned __int64 verify 0x0000000000000000 int(*)(x509_store_ctx_st *) verify_cb 0x0000000000000000 int(*)(int, x509_store_ctx_st *) get_issuer 0x0000000000000000 int(*)(x509_st * *, x509_store_ctx_st *, x509_st *) check_issued 0x0000000000000000 int(*)(x509_store_ctx_st *, x509_st *, x509_st *) check_revocation 0x0000000000000000 int(*)(x509_store_ctx_st *) get_crl 0x0000000000000000 int(*)(x509_store_ctx_st *, X509_crl_st * *, x509_st *) check_crl 0x0000000000000000 int(*)(x509_store_ctx_st *, X509_crl_st *) cert_crl 0x0000000000000000 int(*)(x509_store_ctx_st *, X509_crl_st *, x509_st *) check_policy 0x0000000000000000 int(*)(x509_store_ctx_st *) lookup_certs 0x0000000000000000 stack_st_X509 *(*)(x509_store_ctx_st *, X509_name_st *) lookup_crls 0x0000000000000000 stack_st_X509_CRL *(*)(x509_store_ctx_st *, X509_name_st *) cleanup 0x0000000000000000 int(*)(x509_store_ctx_st *) ▶ ex_data {sk=0x0000000000000000 <NULL> } crypto_ex_data_st references 1 volatile int lock 0x0000024ea5488150 void * ▶ sessions 0x0000024ea542e350 {dummy={d1=0x0000024ea5484bf0 d2=2772978672 d3=-1521988624 } } lhash_st_SSL_SESSION * session_cache_size 20480 unsigned __int64 ▶ session_cache_head 0x0000000000000000 <NULL> ssl_session_st * ▶ session_cache_tail 0x0000000000000000 <NULL> ssl_session_st * session_cache_mode 2 unsigned int session_timeout 7200 long new_session_cb 0x0000000000000000 int(*)(ssl_st *, ssl_session_st *) remove_session_cb 0x0000000000000000 void(*)(ssl_ctx_st *, ssl_session_st *) get_session_cb 0x0000000000000000 ssl_session_st *(*)(ssl_st *, const unsigned char *, int, int *) ▶ stats {sess_connect=0 sess_connect_renegotiate=0 sess_connect_good=0 ...} <anonymous-tag> references 3 volatile int app_verify_callback 0x0000000000000000 int(*)(x509_store_ctx_st *, void *) app_verify_arg 0x0000000000000000 void * default_passwd_callback 0x0000000000000000 int(*)(char *, int, int, void *) default_passwd_callback_userdata 0x0000000000000000 void * client_cert_cb 0x0000000000000000 int(*)(ssl_st *, x509_st * *, evp_pkey_st * *) app_gen_cookie_cb 0x0000000000000000 int(*)(ssl_st *, unsigned char *, unsigned int *) app_verify_cookie_cb 0x0000000000000000 int(*)(ssl_st *, const unsigned char *, unsigned int) gen_stateless_cookie_cb 0x0000000000000000 int(*)(ssl_st *, unsigned char *, unsigned __int64 *) verify_stateless_cookie_cb 0x0000000000000000 int(*)(ssl_st *, const unsigned char *, unsigned __int64) ▶ ex_data {sk=0x0000000000000000 <NULL> } crypto_ex_data_st ▶ md5 0x00007ff6a3e65f00 {currency_converter.exe!evp_md_st md5_md} {type=4 pkey_type=8 md_size=16 ...} const evp_md_st * ▶ sha1 0x00007ff6a3e65fa0 {currency_converter.exe!evp_md_st sha1_md} {type=64 pkey_type=65 md_size=20 ...} const evp_md_st * extra_certs 0x0000000000000000 <NULL> stack_st_X509 * comp_methods 0x0000024ea542bdd0 {...} stack_st_SSL_COMP * info_callback 0x0000000000000000 void(*)(const ssl_st *, int, int) ca_names 0x0000024ea5488330 {...} stack_st_X509_NAME * client_ca_names 0x0000024ea5488360 {...} stack_st_X509_NAME * options 1179652 unsigned int mode 4 unsigned int min_proto_version 771 int max_proto_version 771 int max_cert_list 102400 unsigned __int64 ▶ cert 0x0000024ea54cab50 {key=0x0000024ea54cab70 {x509=0x0000000000000000 <NULL> privatekey=0x0000000000000000 <NULL> ...} ...} cert_st * read_ahead 0 int msg_callback 0x0000000000000000 void(*)(int, int, int, const void *, unsigned __int64, ssl_st *, void *) msg_callback_arg 0x0000000000000000 void * verify_mode 1 unsigned int sid_ctx_length 0 unsigned __int64 ▶ sid_ctx 0x0000024ea54ca8c8 "" unsigned char[32] default_verify_callback 0x0000000000000000 int(*)(int, x509_store_ctx_st *) generate_session_id 0x0000000000000000 int(*)(ssl_st *, unsigned char *, unsigned int *) ▶ param 0x0000024ea5472570 {name=0x0000000000000000 <NULL> check_time=0 inh_flags=0 ...} X509_VERIFY_PARAM_st * quiet_shutdown 0 int ▶ ctlog_store 0x0000024ea5466400 {logs=0x0000024ea54881b0 {...} } ctlog_store_st * ct_validation_callback 0x0000000000000000 int(*)(const ct_policy_eval_ctx_st *, const stack_st_SCT *, void *) ct_validation_callback_arg 0x0000000000000000 void * split_send_fragment 16384 unsigned __int64 max_send_fragment 16384 unsigned __int64 max_pipelines 0 unsigned __int64 default_read_buf_len 0 unsigned __int64 ▶ client_cert_engine 0x0000000000000000 <NULL> engine_st * client_hello_cb 0x0000000000000000 int(*)(ssl_st *, int *, void *) client_hello_cb_arg 0x0000000000000000 void * ▶ ext {servername_cb=0x0000000000000000 servername_arg=0x0000000000000000 tick_key_name=0x0000024ea54ca968 ";þ†ßO^¿\x1f^\t³‹ÉÚü... ...} <anonymous-tag> psk_client_callback 0x0000000000000000 unsigned int(*)(ssl_st *, const char *, char *, unsigned int, unsigned char *, unsigned int) psk_server_callback 0x0000000000000000 unsigned int(*)(ssl_st *, const char *, unsigned char *, unsigned int) psk_find_session_cb 0x0000000000000000 int(*)(ssl_st *, const unsigned char *, unsigned __int64, ssl_session_st * *) psk_use_session_cb 0x0000000000000000 int(*)(ssl_st *, const evp_md_st *, const unsigned char * *, unsigned __int64 *, ssl_session_st * *) ▶ srp_ctx {SRP_cb_arg=0x0000000000000000 TLS_ext_srp_username_callback=0x0000000000000000 SRP_verify_param_callback=...} srp_ctx_st ▶ dane {mdevp=0x0000000000000000 {???} mdord=0x0000000000000000 <NULL> mdmax=0 '\0' ...} dane_ctx_st srtp_profiles 0x0000000000000000 <NULL> stack_st_SRTP_PROTECTION_PROFILE * not_resumable_session_cb 0x0000000000000000 int(*)(ssl_st *, int) lock 0x0000024ea54881e0 void * keylog_callback 0x0000000000000000 void(*)(const ssl_st *, const char *) max_early_data 0 unsigned int recv_max_early_data 16384 unsigned int record_padding_cb 0x0000000000000000 unsigned __int64(*)(ssl_st *, int, unsigned __int64, void *) record_padding_arg 0x0000000000000000 void * block_padding 0 unsigned __int64 generate_ticket_cb 0x0000000000000000 int(*)(ssl_st *, void *) decrypt_ticket_cb 0x0000000000000000 int(*)(ssl_st *, ssl_session_st *, const unsigned char *, unsigned __int64, int, void *) ticket_cb_data 0x0000000000000000 void * num_tickets 2 unsigned __int64 allow_early_data_cb 0x0000000000000000 int(*)(ssl_st *, void *) allow_early_data_cb_data 0x0000000000000000 void * pha_enabled 0 int ▶ init_ {ref_=shared_ptr {...} [4 strong refs] [default] } boost::asio::ssl::detail::openssl_init<1> ▶ ec {val_=0 failed_=false cat_=0x0000024ea6dfbc70 default } boost::system::error_code ▶ results {...} boost::asio::ip::basic_resolver_results<boost::asio::ip::tcp> ◢ req allocator boost::beast::http::message<1,boost::beast::http::basic_string_body<char,std::char_traits<char>,std::allocator<char> >,boost::beast::http::basic_fields<std::allocator<char> > > ◢ [Raw View] {...} boost::beast::http::message<1,boost::beast::http::basic_string_body<char,std::char_traits<char>,std::allocator<char> >,boost::beast::http::basic_fields<std::allocator<char> > > ◢ boost::beast::http::header<1,boost::beast::http::basic_fields<std::allocator<char> > > {version_=11 method_=get (2) } boost::beast::http::header<1,boost::beast::http::basic_fields<std::allocator<char> > > ◢ boost::beast::http::basic_fields<std::allocator<char> > {set_={...} list_={data_={root_plus_size_={m_header={...} } } } method_={ptr_=0x0000000000000000 <NULL> ...} ...} boost::beast::http::basic_fields<std::allocator<char> > ◢ boost::empty_::empty_value<std::allocator<char>,0,1> {...} boost::empty_::empty_value<std::allocator<char>,0,1> std::allocator<char> {...} std::allocator<char> ◢ set_ {...} boost::intrusive::multiset_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,unsigned __int64,1,void> ◢ boost::intrusive::bstree_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,unsigned __int64,1,5,void> {...} boost::intrusive::bstree_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,unsigned __int64,1,5,void> ◢ boost::intrusive::bstbase<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,1,unsigned __int64,5,void> {...} boost::intrusive::bstbase<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,1,unsigned __int64,5,void> ◢ boost::intrusive::bstbase_hack<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,1,unsigned __int64,5,void> {...} boost::intrusive::bstbase_hack<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,1,unsigned __int64,5,void> ◢ boost::intrusive::detail::size_holder<1,unsigned __int64,void> {size_=4 } boost::intrusive::detail::size_holder<1,unsigned __int64,void> size_ 4 unsigned __int64 ◢ boost::intrusive::bstbase2<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,5,void> {...} boost::intrusive::bstbase2<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,void,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,5,void> ◢ boost::intrusive::detail::ebo_functor_holder<boost::intrusive::tree_value_compare<boost::beast::http::basic_fields<std::allocator<char> >::element *,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,boost::move_detail::identity<boost::beast::http::basic_fields<std::allocator<char> >::element>,bool,1>,0> {...} boost::intrusive::detail::ebo_functor_holder<boost::intrusive::tree_value_compare<boost::beast::http::basic_fields<std::allocator<char> >::element *,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,boost::move_detail::identity<boost::beast::http::basic_fields<std::allocator<char> >::element>,bool,1>,0> ◢ boost::intrusive::tree_value_compare<boost::beast::http::basic_fields<std::allocator<char> >::element *,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,boost::move_detail::identity<boost::beast::http::basic_fields<std::allocator<char> >::element>,bool,1> {...} boost::intrusive::tree_value_compare<boost::beast::http::basic_fields<std::allocator<char> >::element *,boost::beast::http::basic_fields<std::allocator<char> >::key_compare,boost::move_detail::identity<boost::beast::http::basic_fields<std::allocator<char> >::element>,bool,1> ◢ boost::intrusive::detail::ebo_functor_holder<boost::beast::http::basic_fields<std::allocator<char> >::key_compare,0> {...} boost::intrusive::detail::ebo_functor_holder<boost::beast::http::basic_fields<std::allocator<char> >::key_compare,0> ◢ boost::beast::http::basic_fields<std::allocator<char> >::key_compare {...} boost::beast::http::basic_fields<std::allocator<char> >::key_compare boost::beast::iless {...} boost::beast::iless ◢ boost::intrusive::bstbase3<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,5,void> {holder={root={...} } } boost::intrusive::bstbase3<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,5,void> ◢ holder {root={...} } boost::intrusive::bstbase3<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3>,5,void>::holder_t ◢ boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3> {...} boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node_traits<void *,0>,0,boost::intrusive::dft_tag,3> boost::intrusive::bhtraits_base<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node<void *> *,boost::intrusive::dft_tag,3> {...} boost::intrusive::bhtraits_base<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::rbtree_node<void *> *,boost::intrusive::dft_tag,3> ◢ root {...} boost::intrusive::detail::default_header_holder<boost::intrusive::rbtree_node_traits<void *,0> > ◢ boost::intrusive::rbtree_node<void *> {parent_=0x0000024ea6dd1d10 {parent_=0x0000005f727ff0f8 {parent_=0x0000024ea6dd1d10 {parent_=0x0000005f727ff0f8 {...} ...} ...} ...} ...} boost::intrusive::rbtree_node<void *> ▶ parent_ 0x0000024ea6dd1d10 {parent_=0x0000005f727ff0f8 {parent_=0x0000024ea6dd1d10 {parent_=0x0000005f727ff0f8 {...} ...} ...} ...} boost::intrusive::rbtree_node<void *> * ▶ left_ 0x0000024ea54f5140 {parent_=0x0000024ea6dd1d10 {parent_=0x0000005f727ff0f8 {parent_=0x0000024ea6dd1d10 {...} ...} ...} ...} boost::intrusive::rbtree_node<void *> * ▶ right_ 0x0000024ea6dd3300 {parent_=0x0000024ea6dd1d10 {parent_=0x0000005f727ff0f8 {parent_=0x0000024ea6dd1d10 {...} ...} ...} ...} boost::intrusive::rbtree_node<void *> * color_ red_t (0) boost::intrusive::rbtree_node<void *>::color ◢ list_ {data_={root_plus_size_={m_header={...} } } } boost::intrusive::list_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node_traits<void *>,0,boost::intrusive::dft_tag,1>,unsigned __int64,0,void> ◢ data_ {root_plus_size_={m_header={...} } } boost::intrusive::list_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node_traits<void *>,0,boost::intrusive::dft_tag,1>,unsigned __int64,0,void>::data_t ◢ boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node_traits<void *>,0,boost::intrusive::dft_tag,1> {...} boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node_traits<void *>,0,boost::intrusive::dft_tag,1> boost::intrusive::bhtraits_base<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node<void *> *,boost::intrusive::dft_tag,1> {...} boost::intrusive::bhtraits_base<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node<void *> *,boost::intrusive::dft_tag,1> ◢ root_plus_size_ {m_header={...} } boost::intrusive::list_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node_traits<void *>,0,boost::intrusive::dft_tag,1>,unsigned __int64,0,void>::root_plus_size boost::intrusive::detail::size_holder<0,unsigned __int64,void> {...} boost::intrusive::detail::size_holder<0,unsigned __int64,void> ◢ m_header {...} boost::intrusive::detail::default_header_holder<boost::intrusive::list_node_traits<void *> > ◢ boost::intrusive::list_node<void *> {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {...} ...} ...} ...} ...} boost::intrusive::list_node<void *> ◢ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ next_ 0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ prev_ 0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ next_ 0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=0x0000024ea6dd26c0 {next_=0x0000005f727ff118 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ▶ prev_ 0x0000005f727ff118 {next_=0x0000024ea54f5130 {next_=0x0000024ea6dd32f0 {next_=0x0000024ea6dd1d00 {next_=...} ...} ...} ...} boost::intrusive::list_node<void *> * ◢ method_ {ptr_=0x0000000000000000 <NULL> len_=0 } boost::basic_string_view<char,std::char_traits<char> > ◢ ptr_ 0x0000000000000000 <NULL> const char * <Unable to read memory> const char len_ 0 unsigned __int64 ◢ target_or_reason_ {ptr_=0x0000024ea6d99c50 " /currencies_list/5c8a4f26806e9/b764b53a14eff3867b09f39375f436b" len_=63 } boost::basic_string_view<char,std::char_traits<char> > ◢ ptr_ 0x0000024ea6d99c50 " /currencies_list/5c8a4f26806e9/b764b53a14eff3867b09f39375f436b" const char * 32 ' ' const char len_ 63 unsigned __int64 version_ 11 unsigned int method_ get (2) boost::beast::http::verb ◢ boost::empty_::empty_value<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,0,0> {value_="" } boost::empty_::empty_value<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,0,0> ◢ value_ "" std::basic_string<char,std::char_traits<char>,std::allocator<char> > [size] 0 unsigned __int64 [capacity] 15 unsigned __int64 ◢ [allocator] allocator std::_Compressed_pair<std::allocator<char>,std::_String_val<std::_Simple_types<char> >,1> ◢ [Raw View] {_Myval2={_Bx={_Buf=0x0000005f727ff150 "" _Ptr=0x0000000000000000 <NULL> _Alias=0x0000005f727ff150 "" } ...} } std::_Compressed_pair<std::allocator<char>,std::_String_val<std::_Simple_types<char> >,1> std::allocator<char> {...} std::allocator<char> ◢ _Myval2 {_Bx={_Buf=0x0000005f727ff150 "" _Ptr=0x0000000000000000 <NULL> _Alias=0x0000005f727ff150 "" } _Mysize=...} std::_String_val<std::_Simple_types<char> > std::_Container_base0 {...} std::_Container_base0 ◢ _Bx {_Buf=0x0000005f727ff150 "" _Ptr=0x0000000000000000 <NULL> _Alias=0x0000005f727ff150 "" } std::_String_val<std::_Simple_types<char> >::_Bxty ◢ _Buf 0x0000005f727ff150 "" char[16] [0] 0 '\0' char [1] 0 '\0' char [2] 0 '\0' char [3] 0 '\0' char [4] 0 '\0' char [5] 0 '\0' char [6] 0 '\0' char [7] 0 '\0' char [8] -17 'ï' char [9] 109 'm' char [10] -59 'Å' char [11] -93 '£' char [12] -10 'ö' char [13] 127 '' char [14] 0 '\0' char [15] 0 '\0' char ▶ _Ptr 0x0000000000000000 <NULL> char * ▶ _Alias 0x0000005f727ff150 "" char[16] _Mysize 0 unsigned __int64 _Myres 15 unsigned __int64 ◢ [Raw View] {...} std::basic_string<char,std::char_traits<char>,std::allocator<char> > ▶ std::_String_alloc<std::_String_base_types<char,std::allocator<char> > > {_Mypair=allocator } std::_String_alloc<std::_String_base_types<char,std::allocator<char> > > ◢ stream {next_layer_={...} core_={engine_={ssl_=0x0000024ea54cdbe0 {version=772 method=0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {...} ...} ...} ...} } boost::asio::ssl::stream<boost::asio::basic_stream_socket<boost::asio::ip::tcp> > boost::asio::ssl::stream_base {...} boost::asio::ssl::stream_base boost::asio::detail::noncopyable {...} boost::asio::detail::noncopyable ◢ next_layer_ {...} boost::asio::basic_stream_socket<boost::asio::ip::tcp> ◢ boost::asio::basic_socket<boost::asio::ip::tcp> {...} boost::asio::basic_socket<boost::asio::ip::tcp> ◢ boost::asio::basic_io_object<boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp>,1> {service_=0x0000024ea6e05450 {...} implementation_={protocol_={family_=2 } } } boost::asio::basic_io_object<boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp>,1> ◢ service_ 0x0000024ea6e05450 {...} boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp> * ◢ boost::asio::detail::service_base<boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp> > {...} boost::asio::detail::service_base<boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp> > ◢ boost::asio::io_context::service {...} boost::asio::io_context::service ◢ boost::asio::execution_context::service {key_={type_info_=0x00007ff6a3f237c0 {currency_converter.exe!class boost::asio::detail::typeid_wrapper<class boost::asio::detail::reactive_socket_service<class boost::asio::ip::tcp> > `RTTI Type Descriptor'} {...} ...} ...} boost::asio::execution_context::service boost::asio::detail::noncopyable {...} boost::asio::detail::noncopyable ◢ __vfptr 0x00007ff6a3eb77f0 {currency_converter.exe!void(* boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp>::`vftable'[6])()} {...} void * * [0] 0x00007ff6a3c5d0c0 {currency_converter.exe!boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp>::`scalar deleting destructor'(unsigned int)} void * [1] 0x00007ff6a3c21360 {currency_converter.exe!boost::intrusive::list_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node_traits<void *>,0,boost::intrusive::dft_tag,1>,unsigned __int64,0,void>::~list_impl<boost::intrusive::bhtraits<boost::beast::http::basic_fields<std::allocator<char> >::element,boost::intrusive::list_node_traits<void *>,0,boost::intrusive::dft_tag,1>,unsigned __int64,0,void>(void)} void * [2] 0x00007ff6a3c259d0 {currency_converter.exe!boost::asio::io_context::service::notify_fork(boost::asio::execution_context::fork_event)} void * ◢ key_ {type_info_=0x00007ff6a3f237c0 {currency_converter.exe!class boost::asio::detail::typeid_wrapper<class boost::asio::detail::reactive_socket_service<class boost::asio::ip::tcp> > `RTTI Type Descriptor'} {...} ...} boost::asio::execution_context::service::key ▶ type_info_ 0x00007ff6a3f237c0 {currency_converter.exe!class boost::asio::detail::typeid_wrapper<class boost::asio::detail::reactive_socket_service<class boost::asio::ip::tcp> > `RTTI Type Descriptor'} {...} const type_info * ▶ id_ 0x0000000000000000 <NULL> const boost::asio::execution_context::id * ▶ owner_ {service_registry_=0x0000024ea5468420 {mutex_={crit_section_={DebugInfo=0xffffffffffffffff {Type=??? ...} ...} } ...} } boost::asio::execution_context & ▶ next_ 0x0000024ea6ddbe20 {scheduler_={one_thread_=false mutex_={mutex_={crit_section_={DebugInfo=0xffffffffffffffff {...} ...} } ...} ...} ...} boost::asio::execution_context::service * {boost::asio::detail::select_reactor} ◢ boost::asio::detail::reactive_socket_service_base {io_context_={init_={...} impl_={one_thread_=false mutex_={mutex_={crit_section_={DebugInfo=0xffffffffffffffff {...} ...} } ...} ...} } ...} boost::asio::detail::reactive_socket_service_base ◢ io_context_ {init_={...} impl_={one_thread_=false mutex_={mutex_={crit_section_={DebugInfo=0xffffffffffffffff {Type=...} ...} } ...} ...} } boost::asio::io_context & ▶ boost::asio::execution_context {service_registry_=0x0000024ea5468420 {mutex_={crit_section_={DebugInfo=0xffffffffffffffff {Type=??? ...} ...} } ...} } boost::asio::execution_context ◢ init_ {...} boost::asio::detail::winsock_init<2,0> boost::asio::detail::winsock_init_base {...} boost::asio::detail::winsock_init_base ◢ impl_ {one_thread_=false mutex_={mutex_={crit_section_={DebugInfo=0xffffffffffffffff {Type=??? CreatorBackTraceIndex=...} ...} } ...} ...} boost::asio::detail::scheduler & ▶ boost::asio::detail::execution_context_service_base<boost::asio::detail::scheduler> {...} boost::asio::detail::execution_context_service_base<boost::asio::detail::scheduler> boost::asio::detail::thread_context {...} boost::asio::detail::thread_context one_thread_ false const bool ▶ mutex_ {mutex_={crit_section_={DebugInfo=0xffffffffffffffff {Type=??? CreatorBackTraceIndex=??? CriticalSection=...} ...} } ...} boost::asio::detail::conditionally_enabled_mutex ▶ wakeup_event_ {event_={events_=0x0000024ea5499b10 {0x0000000000000110, 0x0000000000000114} state_=1 } } boost::asio::detail::conditionally_enabled_event ▶ task_ 0x0000024ea6ddbe20 {scheduler_={one_thread_=false mutex_={mutex_={crit_section_={DebugInfo=0xffffffffffffffff {...} ...} } ...} ...} ...} boost::asio::detail::select_reactor * ▶ task_operation_ {...} boost::asio::detail::scheduler::task_operation task_interrupted_ true bool ▶ outstanding_work_ 0 std::atomic<long> ▶ op_queue_ {front_=0x0000024ea5499b30 {next_=0x0000000000000000 <NULL> func_=0x0000000000000000 task_result_=0 } ...} boost::asio::detail::op_queue<boost::asio::detail::scheduler_operation> stopped_ false bool shutdown_ false bool concurrency_hint_ -1 const int ◢ reactor_ {scheduler_={one_thread_=false mutex_={mutex_={crit_section_={DebugInfo=0xffffffffffffffff {Type=??? ...} ...} } ...} ...} ...} boost::asio::detail::select_reactor & ▶ boost::asio::detail::execution_context_service_base<boost::asio::detail::select_reactor> {...} boost::asio::detail::execution_context_service_base<boost::asio::detail::select_reactor> ▶ scheduler_ {one_thread_=false mutex_={mutex_={crit_section_={DebugInfo=0xffffffffffffffff {Type=??? CreatorBackTraceIndex=...} ...} } ...} ...} boost::asio::detail::scheduler & ▶ mutex_ {crit_section_={DebugInfo=0xffffffffffffffff {Type=??? CreatorBackTraceIndex=??? CriticalSection=??? ...} ...} } boost::asio::detail::win_mutex ▶ interrupter_ {read_descriptor_=364 write_descriptor_=356 } boost::asio::detail::socket_select_interrupter ▶ op_queue_ 0x0000024ea6ddbe88 {{operations_={size_=0 values_={ size=0 } spares_={ size=0 } ...} }, {operations_=...}, ...} boost::asio::detail::reactor_op_queue<unsigned __int64>[4] ▶ fd_sets_ 0x0000024ea6ddbf68 {{fd_set_=0x0000024ea6da77f0 {fd_count=0 fd_array=0x0000024ea6da77f8 {0} } capacity_=...}, ...} boost::asio::detail::win_fd_set_adapter[3] ▶ timer_queues_ {first_=0x0000024ea6d907f8 {impl_={timers_=0x0000000000000000 <NULL> heap_={ size=0 } } } } boost::asio::detail::timer_queue_set shutdown_ false bool ◢ implementation_ {protocol_={family_=2 } } boost::asio::detail::reactive_socket_service<boost::asio::ip::tcp>::implementation_type ▶ boost::asio::detail::reactive_socket_service_base::base_implementation_type {socket_=432 state_=16 '\x10' reactor_data_={...} } boost::asio::detail::reactive_socket_service_base::base_implementation_type ▶ protocol_ {family_=2 } boost::asio::ip::tcp boost::asio::socket_base {...} boost::asio::socket_base ◢ core_ {engine_={ssl_=0x0000024ea54cdbe0 {version=772 method=0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {...} ...} ...} ...} boost::asio::ssl::detail::stream_core ▶ engine_ {ssl_=0x0000024ea54cdbe0 {version=772 method=0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {...} ...} ...} boost::asio::ssl::detail::engine ▶ pending_read_ {...} boost::asio::basic_deadline_timer<boost::posix_time::ptime,boost::asio::time_traits<boost::posix_time::ptime> > ▶ pending_write_ {...} boost::asio::basic_deadline_timer<boost::posix_time::ptime,boost::asio::time_traits<boost::posix_time::ptime> > ▶ output_buffer_space_ { size=17408 } std::vector<unsigned char,std::allocator<unsigned char> > ▶ output_buffer_ {data_=0x0000024ea6e40000 size_=17408 } const boost::asio::mutable_buffer ▶ input_buffer_space_ { size=17408 } std::vector<unsigned char,std::allocator<unsigned char> > ▶ input_buffer_ {data_=0x0000024ea6e44440 size_=17408 } const boost::asio::mutable_buffer ▶ input_ {data_=0x0000000000000000 size_=0 } boost::asio::const_buffer req.body() This expression has side effects and will not be evaluated. stream.next_layer a pointer to a bound function may only be used to call the function ▶ stream.core_ {engine_={ssl_=0x0000024ea54cdbe0 {version=772 method=0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {...} ...} ...} ...} boost::asio::ssl::detail::stream_core ▶ stream.core_.engine_.ssl_ 0x0000024ea54cdbe0 {version=772 method=0x00007ff6a3e39640 {currency_converter.exe!ssl_method_st TLS_client_method_data} {...} ...} ssl_st * " Thanks in advance for any help (and I hope this time I won't be ignored like I've felt I've been lately).

1 0

Re: [Boost-users] [boost] [release] Boost 1.70.0 Beta 1 is now available
by Marshall Clow 19 Mar '19

19 Mar '19

On Tue, Mar 19, 2019 at 2:43 AM Rainer Deyke via Boost < boost(a)lists.boost.org> wrote: > On 13.03.19 15:49, Marshall Clow via Boost wrote: > > For details of what's in the release, see < > > https://www.boost.org/users/history/version_1_70_0.html>. > > > > Please download the beta, give it a try, and report any problems you > > encounter. > > I want to report a problem. > > Boost.Test is broken when cross-compiling for Windows on Linux using a > case-sensitive file system because it #includes <Windows.h> instead of > <windows.h> on line 32 of boost/test/utils/timer.hpp. > I did a quick grep through the boost sources, and found: * About 250 #includes of "windows.h" (all lower case) * Zero #includes of "Windows.h" (upper-case 'W') (and a reference to changing one instance in Boost.Test from "Windows.h" to "windows.h" for 1.67.0) We may or may not be correct, but we're quite consistent. -- Marshall

2 1

Networking TS + Beast, NEW Tutorials, Read this to learn std::net !!!
by Vinnie Falco 18 Mar '19

18 Mar '19

Fellow C++, Boost, and WG21 Enthusiasts, lend me your ear! I write to inform you about exciting developments in C++ networking. First, a bit of background. Networking comes in three flavors: * Networking TS <https://cplusplus.github.io/networking-ts/draft.pdf> * Boost.Asio <https://www.boost.org/doc/libs/1_69_0/doc/html/boost_asio.html> * Standalone Asio <https://github.com/chriskohlhoff/asio> These three are for the most part identical, except that Asio flavors have additional features like ssl::stream and signal_set which are not in the TS, but will very likely appear in a future update or version. We've had Asio for over a decade now, but there is a shortage of experts. Some people believe this shortage is because Asio in particular (and thus, Networking TS since they have identical interfaces) is "difficult to use." I believe it is wrong to blame Asio for this. Concurrent programs in general are hard to write. This is applicable: "Unfortunately, today's reality is that only thoughtful experts can write explicitly concurrent programs that are correct and efficient. This is because today's programming models for concurrency are subtle, intricate, and fraught with pitfalls that easily (and frequently) result in unforeseen races (i.e., program corruption) deadlocks (i.e., program lockup) and performance cliffs (e.g., priority inversion, convoying, and sometimes complete loss of parallelism and/or even worse performance than a single-threaded program). And even when a correct and efficient concurrent program is written, it takes great care to maintain — it's usually brittle and difficult to maintain correctly because current programming models set a very high bar of expertise required to reason reliably about the operation of concurrent programs, so that apparently innocuous changes to a working concurrent program can (and commonly do, in practice) render it entirely or intermittently nonworking in unintended and unexpected ways. Because getting it right and keeping it right is so difficult, at many major software companies there is a veritable priesthood of gurus who write and maintain the core concurrent code." - Herb Sutter, "The Trouble with Locks", <http://www.drdobbs.com/cpp/the-trouble-with-locks/184401930> Although this was written in 2005 it is still relevant today. It is understandable that Asio will be the first target of anger and frustration when writing concurrent programs, since it is on the "front line" so to speak. There has also been a distinct shortage of *good* tutorials and examples for Asio. Articles or blog posts which teach you step by step, explaining everything, and giving example code which demonstrates best practices. Boost.Beast is my low-level HTTP/WebSocket library which builds on Boost.Asio: <https://github.com/boostorg/beast> In the original release of Beast, the documentation stated "prior understanding of Boost.Asio is required." However, field experience has shown that users ignore that requirement and attempt to write complex, concurrent programs as their first-time introduction to both Beast and Asio. Based on feedback from committee members, and to serve users better, the scope of Beast has been enlarged to include first-time users of networking. The upcoming Boost 1.70 release reflects this new scope and I am excited to announce some very nice things which you can access today. First of all, Beast documentation and examples no longer use the "boost::asio" namespace, they the namespace alias "net::". While this is cosmetic, it reinforces the notion when inspecting code that it is equally applicable to Boost.Asio, Asio, and Networking TS (identifiers which are not in the TS, such as signal_set, are still qualified with boost::asio). A new documentation page explains the three flavors of networking: <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/using_io.ht…> This is also explained in my 2018 CppCon presentation: <https://youtu.be/7FQwAjELMek?t=444> I have added a "Networking Refresher", a complete overview of networking from soup to nuts. No prior knowledge or understanding of networking is required, everything is explained in detail so if you want to learn this is the place to start. I also kept it short, but it is loaded with hyperlinks for further learning: <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/using_io/as…> There was a recent paper in Kona, P1269R0 ("Three Years with the Networking TS") about difficulty of implementing timeouts. To address this, Beast now has a stream class which implements configurable timeouts for you, and callers no longer have to fiddle with timers manually anymore. Everything "Just Works." It achieves the P1269R0 author's goal of having timeouts "built-in to asynchronous operations", but in a way that fits in with the design of the TS: <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/using_io/ti…> I feel that this `beast::basic_stream` serves as an existence proof that the current design of Networking TS is sound - the TS offers a flexible toolbox which lets you build your own framework the way that you want it, without making odd choices for you. We are still discovering ways of leveraging it to maximum use. The beast::websocket::stream also has built-in timeouts, but they are enhanced to support "idle pings" (keeping client connections alive) and everything is fully configurable: <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/using_webso…> All you need to do to get sensible, suggested websocket timeouts is add one line of code after creating your stream: ws.set_option(websocket::stream_base::timeout::suggested( beast::role_type::server)); To address the cumbersome boilerplate of writing composed operations (specifically the need to propagate the associated allocator and associated executor, and to avoid invoking the completion handler from within the initiating function when the operation would complete immediately) Beast adds two new utility base classes, with plentiful documentation and examples throughout: <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/using_io/wr…> There are two well-rounded examples which show you step by step how to write these things in a safe way: <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/using_io/wr…> <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/using_io/wr…> I have a big, new open source project which implements a server, that uses the `system_context`, taking full advantage of native Windows and Mac OS system-level execution context features. To support this use case and industry feedback, the examples in Beast now default to being always thread-safe. All examples use a "strand", and leverage P1322R0 ("Networking TS enhancement to enable custom I/O executors"). Yes, this paper which was approved in Kona, is now implemented in both Boost.Beast, and Boost.Asio, including all of the Beast examples, so if you pick up Boost 1.70 (or the master branches from github) you can start playing with this as soon as you're done reading this message!! <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p1322r0.html> We have an active #beast channel in the C++ Slack (https://slack.cpp.al) where experienced users can help, no question is too small! I hope you will join me and the rest of the Beast and Asio community in exploring what the very powerful Networking TS and Asio libraries have to offer, and build something great together! Regards P.S. Don't forget to star the repository! <https://github.com/boostorg/beast>

14 37

boost::endian::native_to_big_inplace fails with char
by Martijn Otto 18 Mar '19

18 Mar '19

I am having issues with boost::endian:native_to_big_inplace when used with a char. Whatever you try to 'reverse' comes out as 0. Looking through the code, on little endian machines it calls endian_reverse (as expected). This function has no overload for a char and it then gets promoted to an int. Since the int _is_ actually larger than 1 byte, something gets reversed. The native_to_big_inplace then returns it as a char, narrowing the int and throwing away all the relevant bits, resulting in a 0. I found an issue on github about this: https://github.com/boostorg/endi an/issues/10 about exactly this issue. The bug is easily shown if you try to compile static_assert(sizeof(boost::endian::endian_reverse('y')) == sizeof('y'))

1 0

Re: [Boost-users] [boost] Networking TS + Beast, NEW Tutorials, Read this to learn std::net !!!
by Vinnie Falco 17 Mar '19

17 Mar '19

> Somebody(tm) (ASIO or Beast) maybe should make buffer that has has member fn content() that returns a range with begin and end. Yes that is in Boost.Beast 1.70: <https://www.boost.org/doc/libs/master/libs/beast/doc/html/beast/ref/boost__…>

1 0

numeric_limits<float128_t> return incorrect values
by Gero Peterhoff 16 Mar '19

16 Mar '19

Hello, your implementation in /boost/math/cstdfloat/cstdfloat_limits.hpp return incorrect values for: - has_denorm - denorm_min - is_bounded - signaling/quiet_NaN ? Are the other values correct? See https://github.com/gcc-mirror/gcc/blob/master/libquadmath/quadmath.h thx Gero

2 1

Boost library name formats
by Damien 15 Mar '19

15 Mar '19

Hello, For several years now we've built Boost libraries on Windows with a minimal set of tags in the library and dll names. Our dlls and libs have looked like this: boost_atomic-mt-gd.dll boost_atomic-mt-gd.lib etc. We just upgraded from 1.65.1 to 1.69 and the same bjam command (with a new bootstrapped bjam) is now giving us an extra x64 tag: boost_atomic-mt-gd-x64.dll boost_atomic-mt-gd-x64.lib This is on VS2017 15.9.9. The bjam command we've used for years is: bjam.exe --toolset=msvc address-model=64 --stagedir=./stage64debug --build-dir=./build64debug --layout=tagged --without-mpi variant=debug link=shared threading=multi runtime-link=shared install --prefix=./win64debug/indep --exec-prefix=./win64debug/bin --libdir=./win64debug/lib --includedir=./win64debug/include Has a default setting in bjam been changed? What can we add to the bjam command to get back to the old minimal names? Thanks in advance. Damien

2 2

Help Needed with C++ SSL-using code
by Osman Zakir 15 Mar '19

15 Mar '19

I followed the Boost.Beast examples for the SSL, sync server and client code and loaded root certificates from the Windows root cert store (or at least tried to), but now I can't even get to my app in my browser anymore for some reason. Here's the link to the GitHub repository with all of the source code: https://github.com/DragonOsman/currency_converter . Any help would be appreciated. [https://avatars0.githubusercontent.com/u/18173932?s=400&v=4]<https://github.com/DragonOsman/currency_converter> GitHub - DragonOsman/currency_converter: Application for Computer Science course<https://github.com/DragonOsman/currency_converter> Google Maps + Currency Converter Web Application. Application for Computer Science course. This is a currency converter web application with the frontend and a backend. github.com

1 0

Re: [Boost-users] [boost] Networking TS + Beast, NEW Tutorials, Read this to learn std::net !!!
by Vinnie Falco 15 Mar '19

15 Mar '19

On Thu, Mar 14, 2019 at 5:09 PM Ivan Matek <libbooze(a)gmail.com> wrote: > Quite a weird pattern, where buffer does not have member begin, end. > Maybe a sentence or two describing the rationale and complexity would be nice. > I know it is O(1), but it is weird that begin/end are called on pointer. Yeah, well... that's a sore subject. First of all I did not invent these buffer concepts, they are part of Asio and Networking TS. And they *used* to have begin() and end(), but then the C++ Standards Committee decided that they didn't like `const_buffers_1` and `mutable_buffers_1`, so they got rid of them in the TS draft. Then they realized that having `const_buffer::begin()` would be confusing. Does it refer to the beginning of the buffer sequence, or does it refer to the first byte of that buffer? They decided to get rid of begin/end entirely for the buffer types and add buffer_sequence_begin and buffer_sequence_end in its place. And this is why we can't have nice things. > > std::size_t read_line > I am tired, but is this function O(n^2)? It starts over from the beginning of the range so there can be some overlap of the searching, yes. > cb += bytes_transferred; // adjust the pointer and size > I would maybe switch to write instead of write_some to keep the code shorter, and mention write_some as another option in text. Well the purpose of this example is to show the looping. > [](error_code ec, std::size_t bytes_transferred) > For learning purposes I would capture something in lambda by value and note that reference capture would be buggy. That is something I might consider!! Remember though I"m stuck in C++11 so no lambda capture assignment expressions. Appreciate the feedback! Regards

2 1

Coordinating Boost Releases with compiler releases
by Marshall Clow 14 Mar '19

14 Mar '19

In the thread "MSVC 2019 and 1.70 beta", there has been a discussion about what to do about support for MSVC 2019, which is due to be released right about the same time that Boost 1.70. One person suggested that we delay the boost release until after the MSVC release (I think the suggestion was "May"). This general question has been discussed before (several times), since tools get released fairly often - and so does Boost. In general, I am not in favor of delaying boost releases in order to add support for 'about to be released' development tools. There are two main reasons for this: * There's always another compiler / tool about to be released. Clang 8 is imminent - currently at RC5. GCC 9.1 is scheduled to be released in early May. * Boost releases happen every four months. August is not really that far off. People who want support for tool XXXX can use "the trunk", getting it either from git or from bintray. [ Everyone knows about the tarballs at bintray, right? https://dl.bintray.com/boostorg/master/ ] Also, if we were to delay the boost release until May, then what would happen to the August release? The release process for 1.71.0 is scheduled to start at the end of June. -- Marshall

3 3

(no subject)
by Marshall Clow 13 Mar '19

13 Mar '19

Boost release 1.70.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.70.0.beta1/source/> The SHA256 checksums are as follows: dbf89645e509acb2e53eac3c633834f1dec80bd8622e6e652a9741dcf0807f17 ./boost_1_70_0_b1.7z 957b984b58656a3ec00661ecad7ef82e3a094bad36e37b9e6624843237854679 ./boost_1_70_0_b1.tar.bz2 76d149c1fb9e8a5ceb3bc1e5587edc40fa79a43e8b990d877c2210f0382b9421 ./boost_1_70_0_b1.tar.gz 71e990b2c26880521fd98459b184ee172ce1c46dcf554b6eaab7776b8b6369a6 ./boost_1_70_0_b1.zip For details of what's in the release, see < https://www.boost.org/users/history/version_1_70_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

2 1

Issue with boost::geometry::intersection
by Heriberto Delgado 13 Mar '19

13 Mar '19

I'm having an issue while using boost::geometry to find the intersection of two specific polygons, and looking at the evidence in front of me I can't help but think this might be a bug in the library. The two polygons in question are: POLYGON((16.8739 0.353458,8.80872e-14 5.50545e-15,0.266003 -12.6988,17.1399 -12.3454,16.8739 0.353458)) POLYGON((-4.53257e-19 2.16383e-17,9.99781 0.209424,10.1459 -6.86009,0.148086 -7.06952,-4.53257e-19 2.16383e-17)) Both of them look like two slightly rotated rectangles, first one being bigger than the other. They intersect at their upper left corner. In order to verify that these polygons CAN be intersected, I ran the following SQL sentence through SQL Server Management Studio (17.9.1): SELECT geometry::STGeomFromText('POLYGON((16.8739 0.353458,8.80872e-14 5.50545e-15,0.266003 -12.6988,17.1399 -12.3454,16.8739 0.353458))', 0) .STIntersection( geometry::STGeomFromText('POLYGON((-4.53257e-19 2.16383e-17,9.99781 0.209424,10.1459 -6.86009,0.148086 -7.06952,-4.53257e-19 2.16383e-17))', 0) ).STAsText() The resulting WKT is: POLYGON ((0.1480860710144043 -7.0695199966430664, 10.145899772644043 -6.8600900173187256, 9.997809886932373 0.20942401885986328, 0 0, 0.1480860710144043 -7.0695199966430664)) which looks about right for the requested intersection rectangle. SSMS itself displays a nice rectangle when you remove ".STAsText()" from that sentence. However, when I tried to duplicate that result using the following program using Visual Studio 2017 (15.9.8) to create an x64 console app, using boost 1.69 as a NuGet: ----------------------------------------------------------------------------------------------------------------- #include <boost/geometry.hpp> #include <vector> #include <iostream> int main(int argc, char** argv) { boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double>> first; boost::geometry::read_wkt("POLYGON((16.8739 0.353458,8.80872e-14 5.50545e-15,0.266003 -12.6988,17.1399 -12.3454,16.8739 0.353458))", first); boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double>> second; boost::geometry::read_wkt("POLYGON((-4.53257e-19 2.16383e-17,9.99781 0.209424,10.1459 -6.86009,0.148086 -7.06952,-4.53257e-19 2.16383e-17))", second); std::vector<boost::geometry::model::polygon<boost::geometry::model::d2::point_xy<double>>> results; boost::geometry::intersection(first, second, results); for (auto& result : results) { std::cout << boost::geometry::wkt(result) << std::endl; std::cout << boost::geometry::is_valid(result) << std::endl; } return 0; } ----------------------------------------------------------------------------------------------------------------- the resulting polygon is: POLYGON((0 -8.88178e-16,0.148086 -7.06952,0.148086 -7.06952,0 -8.88178e-16)) which you can easily see it's not a valid polygon, even though boost::geometry returns "1" when is_valid() is called upon it. I was planning to use boost::geometry on a large scale server application that processes quite large amounts of geometry in a similar way, and this is seriously impairing my ability to do so. Do you guys know what is going on here, and if there is a solution or workaround for it?

3 7

[release] Boost 1.70.0 Beta 1 is now available
by Marshall Clow 13 Mar '19

13 Mar '19

[ resending with a non-empty subject line ] Boost release 1.70.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.70.0.beta1/source/> The SHA256 checksums are as follows: dbf89645e509acb2e53eac3c633834f1dec80bd8622e6e652a9741dcf0807f17 ./boost_1_70_0_b1.7z 957b984b58656a3ec00661ecad7ef82e3a094bad36e37b9e6624843237854679 ./boost_1_70_0_b1.tar.bz2 76d149c1fb9e8a5ceb3bc1e5587edc40fa79a43e8b990d877c2210f0382b9421 ./boost_1_70_0_b1.tar.gz 71e990b2c26880521fd98459b184ee172ce1c46dcf554b6eaab7776b8b6369a6 ./boost_1_70_0_b1.zip For details of what's in the release, see < https://www.boost.org/users/history/version_1_70_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.70.0 Beta 1 Release Candidate 3
by Marshall Clow 12 Mar '19

12 Mar '19

A new release candidates for the first 1.70.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.70.0.beta1.rc3/source/ Changes since RC2: * Relative paths for --prefix, --libdir, etc. are now bound relative to the current working directory, instead of being relative to the Jamfile. Thanks to Tom Kent for the report, and Steven and Peter for the fixes. Changes since RC1: * The Jamfile for Boost.Predef has been updated to allow running the tests from /status. Thanks to mike.dev(a)gmx.de for the report, and to Rene for the fix. The release notes are not yet available. The SHA256 checksums are as follows: dbf89645e509acb2e53eac3c633834f1dec80bd8622e6e652a9741dcf0807f17 ./boost_1_70_0_b1_rc3.7z 957b984b58656a3ec00661ecad7ef82e3a094bad36e37b9e6624843237854679 ./boost_1_70_0_b1_rc3.tar.bz2 76d149c1fb9e8a5ceb3bc1e5587edc40fa79a43e8b990d877c2210f0382b9421 ./boost_1_70_0_b1_rc3.tar.gz 71e990b2c26880521fd98459b184ee172ce1c46dcf554b6eaab7776b8b6369a6 ./boost_1_70_0_b1_rc3.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Boost Release Managers

2 3

convert separate year, month, day, hour, minute, secs, ms to milliseconds since epoch
by Victor Yankee 11 Mar '19

11 Mar '19

I am using C++14 and boost 1.64.0 (could move to newest boost), and need to convert date and time pieces to a single value for milliseconds since the epoch. This is what I have: int64_t msSinceEpoch(int year,int month,int day,int hour,int minute,int second,int ms) { struct std::tm t; t.tm_sec = second; t.tm_min = minute; t.tm_hour = hour; t.tm_mday = day; t.tm_mon = month-1; t.tm_year = year-1900; t.tm_isdst = 0; return (1000* timegm(&t))+ms; // is timegm cross-platform? } Is there a better way? Could not figure out how to use boost::chrono :( Something else? Kind Regards, Vic

5 8

SSL handshake: invalid file handle
by Osman Zakir 11 Mar '19

11 Mar '19

I have a problem with using SSL to switch from HTTP to HTTPS in a web server app I have. The code is here:https://github.com/DragonOsman/currency_converter/blob/master/currency… and my server_certificate.hpp file is herehttps://github.com/DragonOsman/currency_converter/blob/master/server_ce…. The app uses Boost 1.69.0, for Boost.Beast. I took synchronous HTTP SSL server example code and synchronous HTTP example client code from the Boost.Beast repository on here. I got the certificate from Let's Encrypt using the TXT record method, and it's a domain-specific certificate. I was told by the guys at Let's Encrypt forums that it doesn't require DH parameters, but I'd like to confirm here if it's true or not. I didn't get DH parameters. It's a certificate issued via acme.sh. The domain name is a subdomain I got for free from dynu.com; the .cer files I have are ca.cer, {DOMAIN}.cer, and fullchain.cer. I was told that I'd need fullchain.cer so I put that in as the value for the `cert` string (it consists of two certificates and I used both). The private key I have is in a .key file rather than a .pem file and I'm wondering if that's a problem. I also need to ask what I need to do with the ctx.set_options and ctx.set_password_callback methods. Could you please help me (if this is good to ask here)? When I try to visit my app in the browser while my server is running (I'm hosting it on my computer), I get this error in my console window: " handshake: The file handle supplied is not valid " And before, I also got this error: " handshake: An operation was attempted on something that is not a socket " And I also get an error page in my browser saying, "Cannot connect securely to this page". I'm using the MS Edge browser. My private key is an RSA key and the filename is {DOMAIN}.key rather than {DOMAIN}.pem. I'm sorry for repeating this. Thanks in advance for any help or replies.

1 0

Boost Log without ASIO or OpenSSL
by Macumber, Daniel 11 Mar '19

11 Mar '19

Hello, I am using Boost Log but not using any of the ASIO related functionality (that I know of). It seems that Boost ASIO depends on OpenSSL which is giving me some problems. Is there any way to either: * use Boost Log without ASIO * use Boost ASIO without OpenSSL Thanks a lot, Dan

3 6

Question on Posix timezone string
by Mats Webjörn/WIKAB 10 Mar '19

10 Mar '19

I'm using Boost 1.66 and use the following code to get a Posix string to set my uCLinux TZ environment variable to get a local time from an UTC time #include <boost/date_time/local_time/tz_database.hpp> #include <boost/date_time/local_time/local_time.hpp> tz_database tz_db; tz_db.load_from_file("./date_time_zonespec.csv"); time_zone_ptr nyc = tz_db.time_zone_from_region("Europe/Stockholm"); auto s = nyc->to_posix_string(); // "CET+01CEST+01,M3.5.0/02:00,M10.5.0/03:00" setenv("TZ", s.c_str(), 1); The odd thing is that my localtime becomes incorrect, and is actually 1 hr wrong on the opposite side of UTC. But, when I read https://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html it says "The offset specifies the time value you must add to the local time to get a Coordinated Universal Time value". Not add to UTC time, which seems like the Boost Posix string assumes !!!!! Which explains why 16:00 UTC give 15:00 CET instead of 17:00 which is the correct value, when using localtime_r(). Am I missing something fundamentally, or what? Regards Mats Webjörn Webjörn IngenjörsKonsult AB Solhemsbackarna 75A SE-163 56 SPÅNGA Sweden

3 9

[Release] Boost 1.70.0 Beta 1 Release Candidate 2
by Marshall Clow 09 Mar '19

09 Mar '19

A new release candidates for the first 1.70.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.70.0.beta1.rc2/source/ Changes since the last RC: * The Jamfile for Boost.Predef has been updated to allow running the tests from /status. Thanks to mike.dev(a)gmx.de for the report, and to Rene for the fix. The release notes are not yet available. The SHA256 checksums are as follows: 26dba8156ad08041c6da52c84a2654aefda292180afe3546a9a74dda0dfb3781 ./boost_1_70_0_b1_rc2.7z ee794d98429bc2bfae054f2fab6fde53ea95f7c5967d8b267e57c894a4d46e57 ./boost_1_70_0_b1_rc2.tar.bz2 bca5f189d87b26ab903838dee2fd4c54e9043bd35d27b8923cdef42651ae7261 ./boost_1_70_0_b1_rc2.tar.gz 6c8f3af4e64d3a04a3d3a5e98499d2f6bb460ad82c1f33ff7da800b5ab182b0b ./boost_1_70_0_b1_rc2.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Boost Release Managers

1 0

SSL handshake error "The file handle supplied is not valid"
by Osman Zakir 09 Mar '19

09 Mar '19

@chris@kohlhoff.com<mailto:chris@kohlhoff.com> I also opened an issue about this on GitHub here: https://github.com/chriskohlhoff/asio/issues/376 and I tried to make sure to provide all of the necessary information. Except I've just now updated the line numbers in my .cpp file to document the errors meaning that now the error I have reads: " Lines 576 and 577: handshake: The file handle supplied is not valid " Aside from that and the fact that I changed the datatype of "doc_root" in main and do_session to std::string, it's the same. Source code is here: https://github.com/DragonOsman/currency_converter . If I should put all of the info I have in the issue opened on GitHub here as well, please let me know and I'll do it.

1 0

[release] Boost 1.70.0 Beta 1 Release Candidate 1
by Marshall Clow 09 Mar '19

09 Mar '19

The release candidates for the first 1.70.0 beta release are now available at: https://dl.bintray.com/boostorg/beta/1.70.0.beta.1.rc1/source/ The release notes are not yet available. The SHA256 checksums are as follows: a7c570d6307d05dc8d45a3b4c69a0afdcba2b22eac0c4da4d496559f53db7b89 ./boost_1_70_0_b1_rc1.7z 4b91b9a203cf12f6001cf39de83c7cc005fbc5390e2b4b2fc29ce7b19c0537a7 ./boost_1_70_0_b1_rc1.tar.bz2 460dd6499bba9df04c6bfa219b26097bad803b8758304ba45f2fc291aa42c96e ./boost_1_70_0_b1_rc1.tar.gz f209c9a086ed2c7882a0bc8755792f436eb141eaeb8c823ed57295ca9ce25b93 ./boost_1_70_0_b1_rc1.zip As always, the release managers would appreciate it if you download the candidate of your choice and give building it a try. Please report both success and failure, and anything else that is noteworthy. -- The Boost Release Managers

3 6

[boost::filesystem::path] removing components of a path
by Sean Farrow 08 Mar '19

08 Mar '19

Hi all, I'm revisiting boost::filesystem::path after not using it for a while and wondered whether there is a way to remove parts of a path deeper than a specific directory? By way of an example, assume I have the following path declared: boost::filesystem::path path ="d:\\test1\\test2\\test3.txt" what I want to do is determine whether test2 exists as part of the path and if it does remove everything after and including the found part of the path, so in this case \\test2\\test3.txt<file://test2/test3.txt> would be removed. I could do it by converting the path to a string, but wondered whether boost::filesystem could do this natively in some way. Any help appreciated. Kind regards Sean.

3 4

[Release 1.70] Master branch is now closed for the beta
by Marshall Clow 07 Mar '19

07 Mar '19

Except with explicit permission by a release manager. Do whatever you want on develop, just don't change master. We'll re-open master after the beta. As always, check the calendar at https://www.boost.org/development 6-Mar: Boost 1.70.0 closed for all changes 13-Mar: Boost 1.70.0 beta; master branch re-opened 2-Aug: Release closed for all changes, except by permission of a release manager. 3-Apr: Boost 1.70.0 closed for all changes 10-Apr: Boost 1.70.0 release -- The release managers

1 0

Using domain-based SSL certificate with Boost.Beast
by Osman Zakir 05 Mar '19

05 Mar '19

I looked at this example server certificate in the Boost.Beast repository: https://github.com/boostorg/beast/blob/develop/example/common/server_certif… . I have a free SSL certificate that I got for my Dynamic DNS subdomain name which doesn't have DH parameters but does have a certificate chain and a private key. I don't know what to put for ctx.set_options or ctx.set_password_callback. I tried asking at Let's Encrypt as well: https://community.letsencrypt.org/t/how-to-secure-dynamic-dns/87816/19 . I decided to ask here because they said they can't advise me on how to do it with Boost. I don't want to try a reverse proxy. My current web server code can be found here: https://github.com/DragonOsman/currency_converter/blob/master/currency_conv… . [https://avatars0.githubusercontent.com/u/18173932?s=400&v=4]<https://github.com/DragonOsman/currency_converter/blob/master/currency_conv…> currency_converter/currency_converter.cpp at master · DragonOsman/currency_converter · GitHub<https://github.com/DragonOsman/currency_converter/blob/master/currency_conv…> Application for Computer Science course. Contribute to DragonOsman/currency_converter development by creating an account on GitHub. github.com [https://discourse-cdn-sjc1.com/letsencrypt/uploads/default/original/3X/c/a/…]<https://community.letsencrypt.org/t/how-to-secure-dynamic-dns/87816/19> How to secure Dynamic DNS - Help - Let's Encrypt Community Support<https://community.letsencrypt.org/t/how-to-secure-dynamic-dns/87816/19> The acme.sh certs are generally in a domain folder where the acme.sh script lives (something like ~/.acme.sh/example.com). You don’t likely need to generate a new one. community.letsencrypt.org [https://avatars3.githubusercontent.com/u/3170529?s=400&v=4]<https://github.com/boostorg/beast/blob/develop/example/common/server_certif…> boostorg/beast<https://github.com/boostorg/beast/blob/develop/example/common/server_certif…> HTTP and WebSocket built on Boost.Asio in C++11. Contribute to boostorg/beast development by creating an account on GitHub. github.com

1 0

[MPL][MP11] Return value of at_c for out of range index
by Mateusz Loskot 05 Mar '19

05 Mar '19

Hi, While porting some code from MPL to MP11, the latter helped to find some bugs in the ported code [1] I looked closer at those and found 'behavioural' differences between MPL and MP11 when accessing sequences with index value that is out of range. Could anyone help me to understand the following? 1. Why this compiles? using R = at_c<range_c<int, 0, 1>, 100>::type; Tested in C++11 using GCC, clang, MSVC from VS2017/2019 2. Why this compiles in GCC and clang, but fails with MSVC? using V = at_c<vector3_c<unsigned, 1, 2, 3>, 100>::type::type; 3. For GCC and clang, why this compiles static_assert(std::is_same<R, integral_c<int, 100>>::value, ""); but this fails? static_assert(std::is_same<V, integral_c<unsigned int, 100>>::value, ""); Don't vector_c and range_c yield equivalent sequences? By the way, MP11's mp_at_c yield void, as expected, there also no ::type or ::value member, so diagnostics is clearer. [1] https://github.com/boostorg/gil/issues/249 Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2 2

Installing multiple versions of Boost libraries on Linux: Ubuntu & Debian.
by Stephen Gray 05 Mar '19

05 Mar '19

Please could someone advise how to install multiple releases of the Boost libraries on a Linux (Ubuntu & Debian) system and set the system paths to permit switching between them; so that a compiler refers to the desired version and the relevant runtime components are available to an application; e.g. the .so file for boost serialization. Thanks.

1 0

Spatial search with boost r tree
by Bozo Vazic 01 Mar '19

01 Mar '19

Hi all, I'm trying to create a boost r tree with packing algorithm that will store 2D or 3D geometric points. This will be applied in side my peridynamic software for what we call "family search". Family search is basically a simple spatial search where each point of the peridynamic mesh (cloud of geometric points) needs to find all points inside it's horizon (horizon is for 2D a circle with a specific radius and for 3D it's a sphere with a specific radius). What I've found so far were examples for distance search using a random point (not the point that is a r-tree member). I did a distance and index check using bg::index::satisfies by passing a method that checks if the index is different and is distance smaller than radius. Also I use within(box) to constrain my search, but I'm not sure that is the correct way to use r tree spatial search for the point that is a member of the same r tree. Because as far as I understand the point in the r-tree knows has the information of boxes in which it is contained, so wouldn't there be a way to query the tree member using using only the horizon value? The reason why I'm asking this question is because I need to define most optimal spatial search so that query times don't take to long. This is important as I can have several million points that need to be constantly queried. Thnx in advance for all the help. Best Regads Bozo Here is my code for 2D search of only one point #include "stdafx.h" #include <boost/function_output_iterator.hpp> #include <boost/geometry/index/rtree.hpp> #include <boost/geometry.hpp> #include <boost/geometry/geometries/point.hpp> #include <boost/geometry/geometries/box.hpp> #include <vector> #include <iostream> namespace bg = boost::geometry; namespace bgi = bg::index; typedef bg::model::point <double, 2, bg::cs::cartesian> point; typedef std::pair<point, std::size_t> pointI; typedef bg::model::box<point> box; typedef std::pair<point, unsigned> value; bool CheckIndexAndDist(pointI i, pointI j, size_t dist); std::vector<uint64_t> res; struct StoreDataCallback { template <typename Value> void operator()(Value const& v) { res.push_back(v.second); } }; int _tmain(int argc, _TCHAR* argv[]) { std::vector<point> contourCenters; // has some value std::vector<pointI> cloud; double length = 2000; double width = 2000; double dX = length/1000.0; double horizon = 3.015*dX; for(int i = 0; i < length; i++) { for(int j = 0; j < width; j++) { point p; p.set<0>((-1.0 * length / 2.0) + dX + j * dX); p.set<1>((-1.0 * width / 2.0) + dX + i * dX); contourCenters.push_back(p); } } size_t id_gen = 0; std::transform( contourCenters.begin(), contourCenters.end(), back_inserter(cloud), [&](point const& p) { return std::make_pair(p, id_gen++); } ); bgi::rtree<pointI, bgi::quadratic<16> > rtree(cloud); // spatial search box query_box(point(cloud[10].first.get<0>() - 3.2*dX, cloud[10].first.get<1>() - 3.2*dX),point(cloud[10].first.get<0>() + 3.2*dX, cloud[10].first.get<1>() + 3.2*dX)); StoreDataCallback callback; rtree.query( bgi::within(query_box) && bgi::satisfies([&](value const& v) {return CheckIndexAndDist(v, cloud[10],3.015*dX);}), boost::make_function_output_iterator(callback)); return 0; } bool CheckIndexAndDist(pointI i, pointI j, size_t dist) { if( i.second != j.second && (bg::distance(i.first, j.first) < dist)) return true; else return false; }

2 3

Boost archive import error.
by Stephen Gray 01 Mar '19

01 Mar '19

Dear boost-users, On Debian 8 I've compiled a Python extension written in c++ using pip install against Boost_1_66_0. My source code includes: #include "boost/archive/text_iarchive.hpp" #include "boost/archive/text_oarchive.hpp" #include "boost/serialization/map.hpp" #include "boost/serialization/deque.hpp" At runtime I receive the error: ImportError: /home/stephen/envs/pyclonestream/lib/python3.4/site-packages/pyclonestream.cpython-34m.so: undefined symbol: _ZN5boost7archive18text_iarchive_implINS0_13text_iarchiveEE13load_overrideERNS0_15class_name_typeEi I don't know what's wrong here. Please, any suggestions to fix the issue?

1 0

[Concept] Understanding Boost Concept library
by Robert Jones 28 Feb '19

28 Feb '19

This is a small excerpt from the Boost Concepts library, there's various rather unusual techniques employed in it, with preprocessor tricks and various compiler specific tweeks, but this one has defeated me! What is the purpose of "*********** Model:: ***********" ? Maybe it's just to generate a distinctive diagnostic, but it's very sensitive to exact numbers of asterisks! In general what's going on here is the compiler is checking that the destructor of the Model (which is a concept instantiated with a particular type), can be instantiated, but without ever running the destructor or creating an instance of the Model. struct failed {}; template <class Model> struct requirement<failed ************ Model::************> { static void failed() { ((Model*)0)->~Model(); } }; Any insight appreciated. Kind Regards Rob.

1 0

Ambiguous symbols possibly caused by Boost 1.69.0
by tim＠raisedbar.net 28 Feb '19

28 Feb '19

Hi, I'm getting several instances of the following kind of error when I build my code, which does not use boost::thread, etc., as I use the STD versions: 1>c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\include\condition_variable(1 24): error C2872: 'xtime': ambiguous symbol 1>c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\include\thr\xtimec.h(18): note: could be 'xtime' 1>c:\program files\boost\boost\thread\lock_types.hpp(31): note: or 'boost::xtime' My research turned up: https://svn.boost.org/trac10/ticket/11477?cversion=0&cnum_hist=10 So I added the following value for Windows 10 to my preprocessor: _WIN32_WINNT=0x0601; Unfortunately, this makes no difference. Can anybody advise me of a way forward, please? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

4 10

hi i am a beginner user, there are some problem when using the library, can anyone help me with that ? plz
by ching han 25 Feb '19

25 Feb '19

i am trying to use the boost polygon function for example boost::geometry::read_wkt("multipolygon(((0 0 , 3 0 , 3 2 , 0 2)))", q); however i want to use the changing input such as "multipolygon(((A B, 0 2, 0 0, 4 0, 4 0)))" and A, B are the parameters defined by my previous array, but it ends up with showing the bad lexical cast since the parameters A and B can not be used or read if there is any solution that i can use the changing parameters as my polygon input, i kept searching for the answer but still can not find it can anyone plz help me, and i will be so grateful with that. thanks again!

2 1

[release] 1.70.0 closed for major changes
by Marshall Clow 23 Feb '19

23 Feb '19

The master branch is now closed for new libraries and breaking changes, and will be closing for the beta in one week. Also, if you're ready, you can also add your libraries' changes to the release notes at: < https://github.com/boostorg/website/blob/master/feed/history/boost_1_69_0.q… > After editing the release notes, you should get a form to create a pull request, remember to submit it, otherwise I won't see your change. As always, the calendar for the release cycle is available at: https://www.boost.org/development/ Thanks, -- The Boost Release Team

2 1

Re: [Boost-users] [boost.test] Colors
by Raffi Enficiaud 23 Feb '19

23 Feb '19

On 21.02.19 17:22, Udo Steinbach via Boost-users wrote: > Am 2019-02-20 um 22:38 schrieb Raffi Enficiaud via Boost-users: >> and this was fixed in 1.69 > > I have read it, but was so far been too lazy to compile it. > I think that colors may help with many lines of output, and only then. But > the default output of boost::test should be OK, one line. Everything else > needs attention, also no colors needed. You can set an environment variable globally if you want to avoid the default behaviour. See https://www.boost.org/doc/libs/1_69_0/libs/test/doc/html/boost_test/utf_ref… The variable BOOST_TEST_COLOR_OUTPUT is there for your need. > If you want color, you have to handle colors complete, not only 'red here, > green that'. Maybe console setup or unsuitable combinations or color > blindness (system in high contrast mode) or remote console or whatever that > you have to take into account. Right, so your problem is rather the color scheme of Boost.Test that is not playing well with your color scheme. It is true that I did not adjusted the background and I made the hypothesis of the default one. > Because color is not needed for test AND handling colors is not easy, > default should be colorless mode. I respectfully disagree with this statement. I personally like having color outputs, and combining this with log levels let me parse a big amount of information/logs significantly faster. > That are my first two general thoughts. https://en.wikipedia.org/wiki/De_gustibus_non_est_disputandum > >> open an issue next time on GitHub > > I try to avoid registration on free services. > I am fine with that. I still consult this list, although in a less regular manner. If the variable BOOST_TEST_COLOR_OUTPUT is good enough for you, or if you want an improvement, let me know. Best, Raffi

1 0

Re: [Boost-users] [boost.test] Colors
by Mateusz Loskot 21 Feb '19

21 Feb '19

On Thu, 21 Feb 2019 at 17:22, Udo Steinbach via Boost-users <boost-users(a)lists.boost.org> wrote: > Am 2019-02-20 um 22:38 schrieb Raffi Enficiaud via Boost-users: > > > open an issue next time on GitHub > > I try to avoid registration on free services. FYI, GitHub also offers paid account. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

1 0

Boost Test thread safety
by Dan Field 21 Feb '19

21 Feb '19

Hi folks: I'm trying to identify whether or not the boost Test library is thread safe in the sense that multiple threads can simultaneously interact with the library's various macros and API. I'm more interested in a single test being multi-threaded than being able to run multiple test cases simultaneously. In early documentation of the Test library (version 1.58.0 and before) , there's a section in the introduction called "Open issues" that indicates that the library is not thread-safe. However, the documentation after 1.58.0 was substantially re-written, and I don't see any discussion regarding thread safety at all. The question remains. is the Test library thread-safe or not? If there is a definitive statement regarding this issue, please let me know. Thanks in advance!

3 3

Tests: Runtime type_mismatch after upgrade to 1.69
by Florian Lindner 20 Feb '19

20 Feb '19

Crosspost from boost, haven't received any reply there, see also: https://github.com/boostorg/test/issues/199 Hello, after my distribution rolled out the upgrade to Boost 1.69 I am unable to compile my application anymore. I try to get the log_level set. Minimal compiling example: #define BOOST_TEST_DYN_LINK #include <boost/test/unit_test.hpp> #include <boost/test/unit_test_parameters.hpp> bool init_unit_test() { using namespace boost::unit_test; auto logLevel = runtime_config::get<log_level>(runtime_config::btrt_log_level); return true; } int main(int argc, char* argv[]) { int retCode = boost::unit_test::unit_test_main( &init_unit_test, argc, argv ); return retCode; } which compiles fine g++ -std=c++11 -lboost_unit_test_framework boosttesting.cpp but gives an runtime error: % ./a.out Test setup error: boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level Thanks! Florian

2 1

[boost.test] Colors
by Udo Steinbach 20 Feb '19

20 Feb '19

Ahoi! I use boost.test and have now updated to boost v1.68 on Windows, working in standard console. Now Test has colored output, YEAH. The result you see in the picture https://www2.pic-upload.de/img/36193998/no_error_detected.png Notice that I don't use the standard color scheme. With set BOOST_TEST_COLOR_OUTPUT=1 text is light green on gray, bad to read. set BOOST_TEST_COLOR_OUTPUT=0 does black on gray. After that the colors are set to my scheme. Now error result with set BOOST_TEST_COLOR_OUTPUT=1: https://www2.pic-upload.de/img/36193997/failure.png Light red on gray, OK to read, but reset to dark red on gray. I have to use the color command to reset the colors. With command line options it's all the same. Hmmm, how useful can colors be, if the standard output (no error detected) is only one short line? Both pics on https://www.pic-upload.de/gal-1197957/om664y/1.html -- Fahrradverkehr in Deutschland: http://radwege.udoline.de/ GPG: A245 F153 0636 6E34 E2F3 E1EB 817A B14D 3E7E 482E

2 1

Problem with boost threads on hpux
by John Parke 20 Feb '19

20 Feb '19

Hi: I am trying to use boost threads with condition variables on hpux with aCC compiler. The compiler has incomplete support of C++11 standard. It does not have <chrono> or <thread> headers. I get the following error message when compiling a program which is using condition variables: "/usr/local/include/boost/thread/pthread/thread_data.hpp", line 344: error #2135: namespace "boost::chrono" has no member "steady_clock" void sleep_until(const chrono::time_point<chrono::steady_clock, Duration>& t) ^ The c++ code is { while (bufferIsEmpty[bufferPairNo]) { boost::unique_lock<boost::mutex> lock (bufferIsEmptyMutex[bufferPairNo]); =>> zb_bufferIsEmptyCondVar[bufferPairNo].wait_for (lock, boost::chrono::microseconds (100)); } } The version of boost I am using is 1.69.0. I build boost with: ./bjam -a -j6 install --build-dir=build address-model=64 variant=release link=static \ threading=multi runtime-link=static \ define=BOOST_THREAD_DONT_USE_CHRONO \ --with-date_time --with-filesystem \ --with-system --with-thread When I look at the boost header file, I see this: boost/thread/pthread/ thread_data.hpp #ifdef BOOST_THREAD_USES_CHRONO template <class Rep, class Period> void sleep_for(const chrono::duration<Rep, Period>& d) { hidden::sleep_for_internal(detail::platform_duration(d)); } template <class Duration> line 344 >> void sleep_until(const chrono::time_point<chrono::steady_clock, Duration>& t) { sleep_for(t - chrono::steady_clock::now()); } It appears that the define=BOOST_THREAD_DONT_USE_CHRONO, had no affect. Have I built this correctly, or is there another problem? I would greatly appreciate any help on this. Best regards, John John Parke Alebra Technologies Inc. PO Box 120390 New Brighton, MN 55112 770-425-1810

2 2

[log] Warning LNK4217 when compiling using clang-cl
by Marco Craveiro 14 Feb '19

14 Feb '19

Hi boost-users, I'm consuming boost 1.69 successfully from vcpkg, on a number of platforms, including MSVC and clang-cl on Windows. However, for some reason, whilst my MSVC is more or less clean of warnings, the clang-cl build is littered with LNK4217's. These appear to be related to boost.log, and more specifically get_tss_data and set_tss_data: warning LNK4217: locally defined symbol ?get_tss_data@detail@boost@@YAPEAXPEBX@Z (void * __cdecl boost::detail::get_tss_data(void const *)) imported in function "public: struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context * __cdecl boost::thread_specific_ptr<struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context>::get(void)const " (?get@?$thread_specific_ptr@Uformatting_context@?$basic_formatting_sink_frontend@D@sinks@v2s_mt_nt6@log@boost@@@boost@@QEBAPEAUformatting_context@?$basic_formatting_sink_frontend@D@sinks@v2s_mt_nt6@log@2@XZ) warning LNK4217: locally defined symbol ?set_tss_data@detail@boost@@YAXPEBXV?$shared_ptr@Utss_cleanup_function@detail@boost@@@2@PEAX_N@Z (void __cdecl boost::detail::set_tss_data(void const *,class boost::shared_ptr<struct boost::detail::tss_cleanup_function>,void *,bool)) imported in function "public: __cdecl boost::thread_specific_ptr<struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context>::~thread_specific_ptr<struct boost::log::v2s_mt_nt6::sinks::basic_formatting_sink_frontend<char>::formatting_context>(void)" (??1?$thread_specific_ptr@Uformatting_context@?$basic_formatting_sink_frontend@D@sinks@v2s_mt_nt6@log@boost@@@boost@@QEAA@XZ) Googling revealed that this problem indicates some issue on exports (e.g. __declsepc...), but I haven't managed to figure out exactly what is causing it. Have you seen anything of this ilk? Any pointers would be greatly appreciated. Cheers -- Marco Craveiro MD, Domain Driven Consulting about: http://about.me/marcocraveiro blog: http://mcraveiro.blogspot.co.uk twitter: https://twitter.com/MarcoCraveiro That the Ideas are themselves manifestations (of the Idea-Idea) and that the Idea-Idea is a-kind-of Manifestation-Idea—which is a-kind-of itself, so that the system is completely self-describing— would have been appreciated by Plato as an extremely practical joke [Plato]. -- Alan Key

1 0

Reading a file in reverse using boost::iostreams
by Sean Farrow 13 Feb '19

13 Feb '19

Hi, Is there an easy way to read a file in reverse using boost::iostreams? I've got a case where I need to detect whether text is present and it's closer to the end of the file than the beginning. Any help appreciated. Kind regards Sean.

5 5

Boost::Process doesn't work with #define new (boost 1.69)
by Vivek Subramanian 12 Feb '19

12 Feb '19

Hello, I did #define new for debugging memory leaks, and I get this error: "no instance of boost::process::detail::windows::windows_file_codecv operator new matches arguement list" in file boost\process\local.hpp So I did #ifdef new #undef new #endif right before it and it works fine. Hope that this could be of use to someone! Thanks and Regards, Vivek S

4 5

converting a string to base64
by Sean Farrow 08 Feb '19

08 Feb '19

Hi, Does anyone know of an open source boost.iostreams filter that will convert a string (either std::string, or std::wstring) to/from base64? I know there is some code within beest, but wondered whether this had been wrapped? Similarly, I know that there were issues with boost.serialization's base64 code (from memory, I don't think it padded correctly) and don't think there was a filter for this either. Any help appreciated. Kind regards Sean.

3 3

generalize boost macros
by Gero Peterhoff 06 Feb '19

06 Feb '19

Hello, I have some ideas for config/predef, multiprecision and others. config/predef: What bothers me is the inconsistent nomenclature of several macros. For example, integer: BOOST_HAS_INT128 BOOST_NO_INT64_T float: BOOST_FLOATx_C decimal: ? I think you should definitely generalize that: BOOST_HW_TYPE_AVAILABLE: only if TYPE is supported by the hardware (based on BOOST_HW_SIMD*), but not necessarily by the compiler or selected architecture BOOST_LIB_TYPE_AVAILABLE: TYPE is available from the c++library/compiler For example, float80_t: has HW support on x86 (BOOST_HW_FLOAT80_AVAILABLE is defined), but not on MSVC (BOOST_LIB_FLOAT80_AVAILABLE is not defined then) BOOST_SW_TYPE_AVAILABLE: there is an external emulation of TYPE For example, multiprecision A's complement fixed precision integer (TODO) or "half" by sourceforge Of course, this must be set manually. At least for int/float/decimal 8..512 this should be available. BOOST_HW_MACHINE_SIZE: the real word size of HW BOOST_ARCH_MACHINE_SIZE: the word size of the architecture For example, DOS on AMD Ryzen BOOST_HW_MACHINE_SIZE = 64 and BOOST_ARCH_MACHINE_SIZE = 16 multiprecision/float128_t: there are still many features missing most values in numeric_limits<float128_t> are not constexpr math::constants: i miss log2(2/e/pi/10) etc and i miss BOOST_COMP_VECTOR_EXTENSIONS_AVAILABLE if the compiler supports __attribute__(__vector_size__(...)) and BOOST_COMP_VECTOR_EXTENDED_EXTENSIONS_AVAILABLE if the compiler supports extendet vector extensions (currently only clang/llvm?) and BOOST_ARTIFICIAL __attribute__((artificial)) if supported thx

3 9

Boost serialization calling abort
by tim＠raisedbar.net 05 Feb '19

05 Feb '19

Hi, I'm experiencing the issue described at: https://svn.boost.org/trac10/ticket/13354 I' building using VS2017 and Boost 1.69.0 (I note that the article refers to 1.66.0). Does anybody know a fix for this, or am I best to revert back to 1.65.0? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 2

Latest Boost.Test version broke runtime_config::get
by David Sommer 05 Feb '19

05 Feb '19

Hi everyone, version 1.69 of boost.test broke the line *runtime_config::get<log_level>(runtime_config::btrt_log_level)* It works with static linking, however it breaks on dynamic linking. Error message is *boost::runtime::arg_type_mismatch: Access with invalid type for argument corresponding to parameter log_level* In particular the following program fails: * #define BOOST_TEST_MODULE example #define BOOST_TEST_DYN_LINK #include <iostream> #include <boost/test/unit_test.hpp> #include <boost/test/unit_test_parameters.hpp> BOOST_AUTO_TEST_CASE(failDyn) { using namespace boost::unit_test; std::cout << runtime_config::get<log_level>( runtime_config::btrt_log_level ) << std::endl; }* if boost.test is linked dynamically. Best regards, David Sommer

1 0

Boost, MacOSx, and 64 bit
by S. L. Garwood 04 Feb '19

04 Feb '19

I have built boost 1.68 and 1.69 on MacOSX. When I try to use the binary components in a link, I get an error about not being able to find a version for x86_64. Does anyone have any tips? Is there a 64 but specific define for the build? Boost 1.66 from MacPorts seems to be fine but they don’t have 1.68 or 1.69 available (yet). I have a lot of software build using MacPorts so a migration to Homebrew is not really doable at this time.

2 2

Windows 64 bit Libraries.
by A Z 02 Feb '19

02 Feb '19

The boost library contains links to 64 bit Windows libraries on the bintray website, at https://dl.bintray.com/boostorg/release/1.66.0/binaries/. However, these libraries are only for versions of the Microsoft Visual C++ compiler, which do not have compatible bit profiles towards GNU G++, but more particularly with 64 bit Windows TDM. Is it possible for someone at BOOST to build and post libraries for Windows 64 bit TDM C++ for public and professional downloading and usage?

1 0

issue with property_tree/json_parser
by Harikrishna 29 Jan '19

29 Jan '19

Hi All, I am trying to use boost json_parser. I have included json_parser.hpp in my cpp file, I have not included any other code. But I am getting many compilation errors like error: 'boost::spirit::classic' has not been declared and In function void boost::property_tree::json_parser::read_json_internal(std::basic_istream<typename Ptree::key_type::value_type, std::char_traits<typename Ptree::key_type::value_type> >&, Ptree&, const std::string&): [exec] /usr/include/boost/property_tree/detail/json_parser_read.hpp:288: error: \u2018classic\u2019 is not a namespace-name Can you help me resolve this issue? -- Thanks Harikrishna

3 2

[Spirit] Looking for a little Qi guidance for Unicode parsing
by Michael Powell 28 Jan '19

28 Jan '19

Hello, I am turning a corner in my JSON parser. I support ASCII through and through, but now I want to support Unicode, apparently UTF-8, part of the JSON standard. From what I can tell, this is not the entire grammar, but just for Strings. Looking for a little guidance on how to approach that issue, the elements involved, etc. Such as, are we talking about C++ std::wstring? I have also seen std::u32string referenced in some forums. To begin with, it is a somewhat naive impression, would the characters not translate to unsigned char or char, but rather to std::wstring::value_type or std::u32string::value_type? Things like that come to mind approaching the issue. Additionally, how to otherwise handle symbol tables such as escape characters, i.e. from: struct escapes_t : qi::symbols<char, char> { escapes_t() { this->add("\\b", '\b') ("\\f", '\f') ("\\n", '\n') ("\\r", '\r') ("\\t", '\t') ("\\v", '\v') ("\\\\", '\\') ("\\/", '/') ("\\'", '\'') ("\\\"", '"') ; } } char_esc; And on from there. Thanks! Best regards, Michael W Powell

2 1

ASIO: Writing Composed Operations
by Cristian Morales Vega 26 Jan '19

26 Jan '19

Hi, I was looking at https://www.boost.org/doc/libs/develop/libs/beast/doc/html/beast/using_io/w… and came up with a question I can't answer: In https://github.com/boostorg/beast/blob/develop/example/echo-op/echo_op.cpp#… why does it use the AsyncStream associated executor without even looking at the potentially different (right?) Handler associated executor? Regards.

3 13

Fwd: Help needed with include path
by David Aldrich 25 Jan '19

25 Jan '19

Hi I am using Boost on Ubuntu 18.04 LTS, which has boost 1.65.1 installed. I want to use boost 1.69, which I have installed on another server. I specify that remote boost path in my makefile and make compiles my source file with: g++ -c -Wall -m64 -I/net/simdata/OpenSourceLibs/Boost/rel-1.69.0/ -fpic -O3 SINRCalculation.cpp -o _gnuRelease/SINRCalculation.o Now that source file uses boost/multi_array.hpp. The above compiler command gives error: In file included from /usr/include/boost/multi_array.hpp:30:0, from SINRCalculation.cpp:25: /net/simdata/Hudson_OpenSourceLibs/Boost/rel-1.69.0/boost/type_traits.hpp:118:10: fatal error: boost/type_traits/is_nothrow_swappable.hpp: No such file or directory #include <boost/type_traits/is_nothrow_swappable.hpp> ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. Now my copy of boost 1.69 does contain is_nothrow_swappable.hpp so, at first sight, that error is surprising. I think what is happening is the is_nothrow_swappable.hpp is being searched for on the system library path (boost 1.65 does not have that file), not the one I specified using -I. Am I correct? If so, how can I force the compiler to use the boost 1.69 path consistently for all paths?

3 2

Memory mapped files
by Simon Giddings 24 Jan '19

24 Jan '19

Good morning, We are developing a system which heavily uses memory mapped files. These files are initially created under a unix system, but will then be used in portable systems such as Android and iOS. We are having some problems loading memory mapped files created under Unix into Android. Is this scenario even possible ? Are the memory mapped files compatible between systems ? Hope you will be able to shed some light on this. Best regards Simon

5 10

C++Now 2019 Registration is Open
by Jon Kalb 24 Jan '19

24 Jan '19

Boosters, Registration for C++Nows 2019 (aka BoostCon) is now open: http://cppnow.org/announcements/2019/01/2019-registration-is-open/ Please help us to spread the word about this announcement. Thanks. Note that the Aspen Meadows Resort online registration link is also up on the lodging page. Because there will be another group in the hotel, we’ve been allocated fewer rooms this year. Please either reserve a room very soon or plan to stay at the Lamplighter or another hotel in town. See you in Aspen in May. Jon

1 0

[Format] Formatting some string chars not encoding to hex
by Michael Powell 22 Jan '19

22 Jan '19

Hello, I've got some characters that are not formatting to hex properly. They are not being interpreted correctly by the strongly typed Format. For instance, consider the format string: const char x = '$'; // also, '_', for instance const auto s = (boost::format("\\x%1$02x") % x).str(); I would expect this to encode to: "\\x24", however, instead this encodes to "\\x0$". I would expect '_' to encode: "\\x5f", however, this encodes to "\\x0_". In a few words, the encoding is "seeing" the char as a literal char instead of as an "integer". Although I could possibly trap for this as being the case, I do not think that I should. Thoughts? Format authors? Best regards, Michael Powell

2 2

Warnings from 1.69.0
by tim＠raisedbar.net 22 Jan '19

22 Jan '19

Hi, Whilst building my application using Visual Studio 2017 I get the following warnings that I wasn't getting prior to changing to 1.69.0: 1>c:\program files\boost\boost\pending\integer_log2.hpp(7): note: This header is deprecated. Use <boost/integer/integer_log2.hpp> instead. The identified header is not referenced in my own code, but is being included by the Boost logging code. Can anybody advise me as to my best way of dealing with this situation, please, as I'm trying for a warning-free build. Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 1

[Spirit Qi] Failed to parse the following fixed format double
by Michael Powell 19 Jan '19

19 Jan '19

Hello, We've been here before, but it is still a problem. I formatted this one using Boost.Format, "%1$.20f", especially dealing with 64-bit floating point values: "-6454866677007257221799838306103363329054216765979693126687924767750184064408021645577150612734391912932504859271476290909819606665305867922002041825515395649967939044362235953753132737391831714484437364695236622971838510661738713863719312223765488747173369566663518205119012003640541309414736378162701139968.00000000000000000000" Grammar is defined: numeric_sign %= ( ('-' >> attr(numeric_sign_minus)) | ('+' >> attr(numeric_sign_plus)) ) ; float_lit %= real_parser<float_t, strict_ureal_policies<float_t>>{}; floating_point %= -numeric_sign >> float_lit; With rules defined as: qi::rule<iterator_type, numeric_sign_t()> numeric_sign; qi::rule<iterator_type, float_t()> float_lit; qi::rule<iterator_type, floating_point_number_t()> floating_point; Where float_t is a defined part of the AST: using float_t = double; And floating_point maps to the floating_point_number_t, basically mapping the Sign and Value. Seems like we've been here before with inadequate response, however, reading the Boost documentation, I do not see any reason any Qi should be rejecting this value: https://www.boost.org/doc/libs/1_69_0/libs/spirit/doc/html/spirit/qi/refere… Particularly the RealPolicies: sign = lit('+') | '-' ; nan = -lit("1.0#") >> no_case["nan"] >> -('(' >> *(char_ - ')') >> ')') ; inf = no_case[lit("inf") >> -lit("inity")] ; floating_literal = -sign >> ( nan | inf | fractional_constant >> -exponent_part | +digit >> exponent_part ) ; fractional_constant = *digit >> '.' >> +digit | +digit >> -lit('.') ; exponent_part = (lit('e') | 'E') >> -sign >> +digit ; Although the concern I have is that the RealPolicy grammar defined above is not implemented as Qi Rules, per se, but rather brute force. In other words, error prone in the ways that a brute force approach is error prone. Best regards, Michael Powell

1 2

[Format] How to format floating point values
by Michael Powell 19 Jan '19

19 Jan '19

Hello, How do I format floating point values, either double or float? I want to specify things like the precision during the formatting, i.e. how many digits to include in the fractional digits, and so forth. Currently, I am using this, for instance: General: "%1$g" Fixed: "%1$f" Scientific: "%1$e" or "%1$E" (depending on whether lower or upper case, respectively) Thanks! Best regards, Michael Powell

2 2

is boost::container::static_vector header only library?
by Sivaram L 19 Jan '19

19 Jan '19

I am working on a embedded systems project, where we are exploring options to use STL containers without dynamic memory allocation, except std::array we cannot use any of the STL, boost container has static_vector for that, on browsing the code,we found that the library has to be built, is there a way to use this library as header only library?

5 4

Atomic boost::filesystem::rename
by Lars 15 Jan '19

15 Jan '19

Hello, What is the most "atomic" way to move two files from a local disk to a server location? The meaning of atomic in this context means that either both files are moved or both files stay in original location. No intermediate files should be present once operation is finished. The two files are located in different directories; /root/file_a /root/data/file_b The solution must support both Windows and Linux environment. It appears boost::filesystem::rename(..) uses Win32 API MoveFileExW for the Windows implementation. The documentation for MoveFileExW states; "If the file is to be moved to a different volume, the function simulates the move by using the CopyFile and DeleteFile functions. If the file is successfully copied to a different volume and the original file is unable to be deleted, the function succeeds leaving the source file intact." This means boost::filesystem::rename(..) could potentially just perform a file copy which is undesirable behaviour. Our understanding is that Boost filesystem does not contain ACL permission support [1] which make it difficult to check privileges prior to performing moves. Appreciate any input on the matter. Using C++14 and Boost. [1] - https://lists.boost.org/boost-users/2018/12/89232.php

2 1

Re: [Boost-users] Server application won't bind to ports on IP address other than my internal ones
by Osman Zakir 15 Jan '19

15 Jan '19

I just tried commenting out the POST request handling code and the client_session stuff, and then tried to run it with my external IP, but the same error from bind() came up saying that the requested address is not valid in its context. I also tried using the wildcard IP 0.0.0.0 as the command line argument for the address when running the server and entering my external IP into the browser address bar, but I still couldn't visit the app in the browser (can't get to it either way). The problem is probably in the server code, and is because of Asio (probably). I need some advice on how best to confirm this and troubleshoot the problem. Thanks in advance.

8 33

C++Now 2019 Submission Deadline
by Jon Kalb 14 Jan '19

14 Jan '19

The deadline for submitting to C++Now 2019 is just a few days away. If you’ve been thinking of submitting, please do not delay: http://cppnow.org/announcements/2018/12/2019-call-for-submissions/ <http://cppnow.org/announcements/2018/12/2019-call-for-submissions/> Thanks. Jon

1 0

Boost.Optional error should be a warning
by Michael Powell 14 Jan '19

14 Jan '19

Hello, I am using Boost.Optional, and, while I do want to "include it in an output", the library which I am doing so has another mechanism to do so. Translation, for Optional purposes, the following assertion should be a warning, IMO, and not an error: BOOST_STATIC_ASSERT_MSG(sizeof(CharType) == 0, "If you want to output boost::optional, include header <boost/optional/optional_io.hpp>"); Cheers, Michael Powell

2 4

Boost.Units: Is it possible to convert on assignment without casting?
by Carel Combrink 14 Jan '19

14 Jan '19

Hi. I have two unit quantities defined as follow: static const auto Hz = boost::units::si::hertz; static const auto KHz = boost::units::si::kilo * Hz; using Hertz = boost::units::quantity<decltype( Hz ), double>; using Kilohertz = boost::units::quantity<decltype( KHz ), double>; Assigning one type to another does not compile: Kilohertz freqKhz = Kilohertz::from_value( 1.234 ); Hertz freqHz = freqKhz; >>> error: conversion from 'Kilohertz {aka boost::units::quantity<...>, double>}' to non-scalar type 'Hertz {aka boost::units::quantity<...>, double>}' requested [1] Is this possible, should it be enabled or is it not supported? I am using boost 01.67, Mingw 5.3 and MSVC 2017 (C++14) The following options work as expected: Hertz freq1 = static_cast<Hertz>( freqKhz ); Hertz freq2 = Hertz( freqKhz ); But this adds a bit more code to maintain and keep in sync, one thing one tries to avoid when using the library since one needs to keep the LHS and the RHS of the opertor= in sync. PS: The chrono library allows this type of conversion given there is no information lost (but for double as storage types this should not be the case) std::chrono::seconds sec = std::chrono::seconds { 10 }; std::chrono::nanoseconds nsec = sec; [1] https://gcc.godbolt.org/z/0sTHQQ Regards, Carel

3 2

Forcing boost to build zlib
by Simon Michalke 12 Jan '19

12 Jan '19

Hello, what is needed to force bjam to build zlib? Is the zlib.h enough? Also is there a way to make bjam fail compiling if I set "NO_ZLIB=0" and it does not find the zlib.h / source? It is really inconvenient that bjam silently switches off zlib without any error or warning why zlib is not being build. My commands are: ./bootstrap.sh --without-libraries=python --prefix=/home/simon/code/cfs/release_mingw_openblas/cfsdeps/boost/install --with-toolset=gcc --without-libraries=context --without-libraries=coroutine target-os=windows architecture=x86 address-model=64 release and ./b2 target-os=windows architecture=x86 address-model=64 release --user-config=user-config.jam toolset=gcc-mingw -s ZLIB_BINARY=\"/home/simon/code/cfs/release_mingw_openblas/lib64/MINGW_X86_64/libzlibstatic.a\" -s ZLIB_INCLUDE=\"/home/simon/code/cfs/release_mingw_openblas/include\" -s NO_ZLIB=0 threading=multi install (this is cross compiling, but I have the same problem building for Linux) Regards, Simon

4 6

Possible Boost.Variant issue with JSON AST
by Michael Powell 11 Jan '19

11 Jan '19

Hello, I've got an AST I am developing to support JSON parsing using the latest VC++ (15.9.5), however, I am having difficulty persuading the compiler with my forward declarations. i.e. 1>d:\dev\boost.org\boost_1_69_0\boost\mpl\sizeof.hpp(27): error C2027: use of undefined type 'kingdom::json::object_t' In terms of JSON AST modeling, the rub appears to be in a couple of places: defining the JSON AST Array, and making the JSON AST Object available to Value. Re: semantic terminology, Value is interchangeable with Element, in view of the JSON grammar. Here's my attempt at a flattened single source example: https://wandbox.org/permlink/83c3VXZ4W1DHoEBc I seem to recall there being future issues with C++ forward declarations, but this seems to be like a bad language design decision to restrict this, especially in light of this kind of approach. I'm not sure how better to sort this out. At minimum, at least Value needs a forward declaration depending on how I arrange my headers, includes, etc. But then I still run into Value forward declaration undefined type issues. I'm not sure it's as much a language issue as much as it is possible a Boost.Variant issue, per se. Suggestions? Thanks! Michael Powell

3 5

[Spirit] Incompatible skipper type?
by Michael Powell 10 Jan '19

10 Jan '19

Hello, I'm a bit confused here, not sure what this means: Severity Code Description Project File Line Suppression State Error C2664 'bool boost::function4<R,T0,T1,T2,T3>::operator ()(T0,T1,T2,T3) const': cannot convert argument 4 from 'const Skipper' to 'T3' Kingdom.Json.Parser.Tests d:\dev\boost.org\boost_1_69_0\boost\spirit\home\qi\nonterminal\rule.hpp 304 // If you are seeing a compilation error here stating that the // fourth parameter can't be converted to a required target type // then you are probably trying to use a rule or a grammar with // an incompatible skipper type. if (f(first, last, context, skipper)) {} Incompatible where? How? Requires clarification please. The default Skipper type, which I am using at the moment, is boost::spirit::qi::space_type. I aim to use the proven Comment Skipper that I leveraged in a previous iteration eventually, but I expect that compilation should work with the simple space type at least. Because as far as I can determine all of the rules in my Grammar have the same Skipper type. struct json_grammar : qi::grammar<It, value_t(), Skipper> { using iterator_type = It; using skipper_type = Skipper; using char_rule_type = qi::rule<It, char()>; json_grammar() : json_grammar::base_type(value_) { // ... } private: struct escapes_t : qi::symbols<char, char> { escapes_t() { this->add("\\b", '\b') ("\\f", '\f') ("\\n", '\n') ("\\r", '\r') ("\\t", '\t') ("\\v", '\v') ("\\\\", '\\') ("\\/", '/') ("\\'", '\'') ("\\\"", '"') ; } } char_esc; //qi::rule<iterator_type> line_cont; char_rule_type hex_esc, unicode_esc; qi::rule<iterator_type, str_t()> quot_str, tick_str, str_lit; qi::rule<iterator_type, std::vector<value_t>(), skipper_type> array_; qi::rule<iterator_type, boost::tuple<key_t, value_t>(), skipper_type> member; qi::rule<iterator_type, std::vector<boost::tuple<key_t, value_t>>(), skipper_type> object_; qi::rule<iterator_type, key_t(), skipper_type> member_key; qi::rule<iterator_type, value_t(), skipper_type> value_; qi::rule<iterator_type, numeric_sign_t(), skipper_type> numeric_sign; qi::rule<iterator_type, float_t(), skipper_type> float_lit; qi::rule<iterator_type, floating_point_number_t(), skipper_type> floating_point; qi::rule<iterator_type, int_t(), skipper_type> hex_int, oct_int, dec_int, int_lit; qi::rule<iterator_type, integer_number_t(), skipper_type> integer; qi::rule<iterator_type, boolean_t(), skipper_type> bool_lit; qi::rule<iterator_type, null_t(), skipper_type> null_lit; }; Best regards, Michael Powell

1 2

Server application won't bind to ports on IP address other than my internal ones
by Osman Zakir 10 Jan '19

10 Jan '19

I have a server application that I wrote. It currently doesn't bind to any ports on any IP address other than my computer's internal IP addresses (the localhost and 192.168.x.x ones). The application is the one whose source code is on GitHub here<https://github.com/DragonOsman/currency_converter/>. I used the asynchronous server and client examples from the Boost.Beast GitHub repository for the networking code (this link for the server: link<https://github.com/boostorg/beast/blob/develop/example/http/server/async/ht…>; this link for the client: link<https://github.com/boostorg/beast/blob/develop/example/http/client/async/ht…>). But when I run it using my external IP address, I get the error documented on lines 471 and 472: // Bind to the server address acceptor_.bind(endpoint, ec); if (ec) { std::cerr << "Lines 471 and 472:\n"; fail(ec, "bind"); return; } with the error itself being: bind: The requested address is not valid in its context And I've heard from whoever has tried to download and then run the server application that it just closes on its own after a while. I also tried to deploy it to Heroku as a Docker container before and found that it wouldn't bind to any ports they tried to bind it to and they had to kill it with SIGKILL. I tried to look for the code for bind in Asio, but I don't really know where to look. Some help on that would also be appreciated. I might be able to figure it from reading that code. If I can't, I'll come back here.

5 7

C++/CLI and >=VS2015
by liong＠gmx.ch 09 Jan '19

09 Jan '19

6 5

How strong is PropertyTree JSON support
by Michael Powell 09 Jan '19

09 Jan '19

Hello, I have a requirement to support parsing JSON, and while I could potentially pull together a Spirit Qi (or even X3, possibly) based grammar, I wonder with all the idiosyncrasies, i.e. particularly strings, escape sequences, Unicode, etc, is it worth it. Then there's the Boost.PropertyTree JSON support, which I think may be an adequate fit. However, just how robust is this support when it comes to handling some of the nuanced corner cases? The harder ones I think are the potential for escape sequences, Unicode, etc, embedded within a String. i.e. https://json.org/ or, http://es5.github.io/x7.html It seems with Property Tree there are also these limitations: <docs> The property tree dataset is not typed, and does not support arrays as such. Thus, the following JSON / property tree mapping is used: * JSON objects are mapped to nodes. Each property is a child node. * JSON arrays are mapped to nodes. Each element is a child node with an empty name. If a node has both named and unnamed child nodes, it cannot be mapped to a JSON representation. * JSON values are mapped to nodes containing the value. However, all type information is lost; numbers, as well as the literals "null", "true" and "false" are simply mapped to their string form. * Property tree nodes containing both child nodes and data cannot be mapped. </docs> It seems to me that much of the limitation is in adapting the PropertyTree to the JSON structure, but mostly vice versa. Not quite fitting a square peg in a round hole, but coming quite close, I think: "If a node has both named and unnamed child nodes, it cannot be mapped to a JSON representation." We're talking about the mapping from PropertyTree to JSON here? Seems like a potentially problematic issue depending on desired usage, 'all type information is lost; numbers, as well as the literals "null", "true" and "false" are simply mapped to their string form'. I'm not sure what "nodes containing both child nodes and data" means? https://www.boost.org/doc/libs/1_69_0/doc/html/property_tree/parsers.html#p… Besides these concerns, I should think a grammar is fairly straightforward to construct, if push came to shove. It's either living with the Boost.PropertyTree or rolling my own AST, which is not outside the realm of possibility for my purposes. Thoughts? Suggestions? Thanks! Michael Powell

4 3

Re: [Boost-users] How strong is PropertyTree JSON support
by Bjorn Reese 08 Jan '19

08 Jan '19

On 1/8/19 6:50 PM, Michael Powell via Boost-users wrote: > Thoughts? Suggestions? https://github.com/breese/trial.protocol http://breese.github.io/trial/protocol/trial_protocol/json.html

2 3

Boost wiki - revised Boost guidance for authors on Warnings - RFC
by Paul A. Bristow 08 Jan '19

08 Jan '19

As promised at the end of a long (hijacked!) thread on 'Warnings' http://boost.2283326.n4.nabble.com/Current-Guidance-on-Compiler-Warnings-td… starting from a query by Brian Kuhl of Wind River on Boost's policy on compiler warnings, I have spent some time revising the previous guidance document on Trac that I edited many years ago. This was a long and tedious task as Markdown, as most conveniently used on Github, is rather different from the mark-up language on Trac, leaving me slightly in fumble mode :-( I have made some updates en passant, but there is still much to do updating for the much improved granularity of warning suppression and perhaps more about other code improvement tools like Lint, UBSan. The overall structure leaves a lot to be desired, but I don't want to put any more work into this without some encouragement that it will prove useful. I have posted the result of my efforts on https://github.com/boostorg/boost/wiki/Guidelines:-Warnings and I am as promised I am starting this new thread on warning for your comments, corrections, condemnations etc. HTH Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

2 1

[Solaris 11] wrong RUNPATH after install
by Dechaux Eric CEN (BCQ STIG) 07 Jan '19

07 Jan '19

Hello, I am building boost 1.69 on a Solaris 11.4 x86_64 box. After installation the shared libraries keep the boost dependencies from the build directory. The build log is without error and attached, ldd output is the following : :/usr/local/lib$ ldd libboost_*.so.1.69.0 libboost_chrono.so.1.69.0: bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0 => (file not found) libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_context.so.1.69.0: libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_coroutine.so.1.69.0: bin.v2/libs/context/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_context.so.1.69.0 => (file not found) bin.v2/libs/thread/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_thread.so.1.69.0 => (file not found) bin.v2/libs/chrono/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_chrono.so.1.69.0 => (file not found) bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0 => (file not found) libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_system.so.1.69.0: libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 libboost_thread.so.1.69.0: bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0 => (file not found) libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 As a result I can't move the library on another box without changing the RUNPATH on the .so files with elfedit. I tried to build each library on it own but the final result is the same. What can I do ? Thanks. -- Eric Ce message électronique et tous les fichiers attachés qu'il contient sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le retourner à son émetteur. La publication, l'usage, la distribution, l'impression ou la copie non autorisée de ce message et des attachements qu'il contient sont strictement interdits. En cas d'urgence, composez le 17 ou le 112. Afin de contribuer au respect de l'environnement, merci de n'imprimer cet e-mail qu'en cas de necessite. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual to whom it is addressed. If you have received this email in error please send it back to the person that sent it to you. Unauthorized publication, use, dissemination, forwarding, printing or copying of this email and its associated attachments is strictly prohibited. In case of emergency, dial number 17 or 112. To contribute to the environmental protection, please print this e-mail only if necessary.

1 0

Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 07 Jan '19

07 Jan '19

My project-config.jam file has quotes where needed, so that's not a problem. That file isn't the problem, but probably the commands I'm running are. I'll try to see if I can get it to work without Stacktrace. ________________________________ From: Osman Zakir <osmanzakir90(a)hotmail.com> Sent: Saturday, January 5, 2019 8:50 PM To: degski Subject: Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file I'll just build Boost with MSVC then, for now. And I'll wait for work on clang-cl build to be completed. I'll check out the posts in the archive that you mentioned, too. Maybe I'll something that can help me. ________________________________ From: degski <degski(a)gmail.com> Sent: Saturday, January 5, 2019 8:44 PM To: Osman Zakir Subject: Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file Yes, I did build 1.69 successfully [with thin-lto]. That won't help you, though [as I already gave you all the info]. Getting boost to build with clang-cl has been a long-term process [I've been pushing this for close to 2 years]. It only (mostly) works since [important work, boost 1.69] has been done by Peter Dimov (relatively recent)]. You really should dig into the archives to see what progress has been made (https://lists.boost.org/Archives/boost/2018/11/244235.php, but there are many more posts), not all might be perfect yet, we are on the bleeding edge here. The whole thing of building boost with clang-cl [as clang-cl itself, which is part of the problem, while at the same time MSVC is in significant flux as well] is a WIP (work in progress), so you cannot expect things to be perfect [yet, but the commitment is there (of all parties involved) and I am sure it will be good at some point in the (near?) future]. degski -- “If something cannot go on forever, it will stop" - Herbert Stein

3 11

Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 05 Jan '19

05 Jan '19

Okay, so what commands did you use when building, then? When it also built Stacktrace. And could you also try with version 1.69.0 and let me know how that turns out? ________________________________ From: degski <degski(a)gmail.com> Sent: Saturday, January 5, 2019 6:40 PM To: Osman Zakir Subject: Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file On Sat, 5 Jan 2019 at 15:37, degski <degski(a)gmail.com<mailto:degski@gmail.com>> wrote: You need something like libboost_stacktrace_windbg_cached-vc141-mt-sgd-1_65_1.lib and libboost_stacktrace_windbg-vc141-mt-sgd-1_65_1.lib [but then for 1.69 of course and the release builds as well]. Whether that is relevant to you is for you to decide. FYI, I was able to build those libs with clang-cl. degski My guess is that the _noop_ versions do nothing [a no op(eration)], but are just stub-libs to satisfy your linker. degski -- “If something cannot go on forever, it will stop" - Herbert Stein

2 1

Re: [Boost-users] I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 05 Jan '19

05 Jan '19

The Stacktrace libs I have are: "libboost_stacktrace_noop-clangw8-mt-d-x32-1_69.lib", "libboost_stacktrace_noop-clangw8-mt-d-x64-1_69.lib", "libboost_stacktrace_noop-clangw8-mt-x32-1_69.lib", and "libboost_stacktrace_noop-clangw8-mt-x64-1_69.lib" Should I have two more of the Stacktrace libs, or is this fine? As I said in my previous message, the first error actually comes from Boost.Stacktrace and it says: "error: no member named 'GetModuleFileNameA' in namespace 'boost::winapi'; did you mean simply 'GetModuleFileNameA'?". I also still need help on this issue I opened in the Boost.Asio GitHub: https://github.com/boostorg/asio/issues/184 . [https://avatars0.githubusercontent.com/u/18173932?s=400&v=4]<https://github.com/boostorg/asio/issues/184> Server application won't bind to ports on IP address other than my internal ones · Issue #184 · boostorg/asio<https://github.com/boostorg/asio/issues/184> As the title says, my server application doesn't bind to any ports on any IP address other than my computer's internal IP addresses (the localhost and 192.168.x.x ones). The application is ... github.com

2 1

I ran b2 with the -d+2 command and redirected the output to a file
by Osman Zakir 05 Jan '19

05 Jan '19

This is a follow-up to the message where I asked for help about a failed attempt to build Boost. I ran b2 with the -d+2 command in addition to the other commands and also redirected the output to a file. It's attached to this message, as well as the project-config.jam file.

5 7

New user : Help on Solaris
by Dechaux Eric CEN (BCQ STIG) 03 Jan '19

03 Jan '19

Hello everyone, I am a Solaris user and need to build pgAgent 4.0 on a Solaris 11.4 X86_64 box. pgAgent require boost withthreading. I have build boost 1.69 with no issue : sol114:/tmp/build/boost_1_69_0$ ./b2 threading=multi -d+2 -a Performing configuration checks - default address-model : 64-bit - default architecture : x86 Building the Boost C++ Libraries. - C++11 mutex : yes - lockfree boost::atomic_flag : yes - Boost.Config Feature Check: cxx11_auto_declarations : yes - Boost.Config Feature Check: cxx11_constexpr : yes - Boost.Config Feature Check: cxx11_defaulted_functions : yes - Boost.Config Feature Check: cxx11_final : yes - Boost.Config Feature Check: cxx11_hdr_mutex : yes - Boost.Config Feature Check: cxx11_hdr_tuple : yes - Boost.Config Feature Check: cxx11_lambdas : yes - Boost.Config Feature Check: cxx11_noexcept : yes - Boost.Config Feature Check: cxx11_nullptr : yes - Boost.Config Feature Check: cxx11_rvalue_references : yes - Boost.Config Feature Check: cxx11_template_aliases : yes - Boost.Config Feature Check: cxx11_thread_local : yes - Boost.Config Feature Check: cxx11_variadic_templates : yes - has_icu builds : yes warning: Graph library does not contain MPI-based parallel components. note: to enable them, add "using mpi ;" to your user-config.jam - zlib : yes - bzip2 : yes - lzma : yes - zstd : no - icu : yes warning: non-free usage requirements <runtime-link>shared ignored warning: in main-target build_options at libs/locale/build/Jamfile.v2:414 warning: non-free usage requirements <runtime-link>shared ignored warning: in main-target build_flags at libs/locale/build/Jamfile.v2:415 - xopen-source-600-supported : yes - native-atomic-int32-supported : yes - native-syslog-supported : yes - pthread-supports-robust-mutexes : yes - compiler-supports-ssse3 : yes - compiler-supports-avx2 : yes - gcc visibility : yes - long double support : yes 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. - libbacktrace builds : no - addr2line builds : yes - WinDbg builds : no - WinDbgCached builds : no - BOOST_COMP_GNUC >= 4.3.0 : no - zlib : yes - bzip2 : yes - lzma : yes - zstd : no Component configuration: - atomic : building - chrono : building - container : building - context : building - contract : building - coroutine : building - date_time : building - exception : building - fiber : building - filesystem : building - graph : building - graph_parallel : building - iostreams : building - locale : building - log : building - math : building - mpi : building - program_options : building - python : building - random : building - regex : building - serialization : building - stacktrace : building - system : building - test : building - thread : building - timer : building - type_erasure : building - wave : building [...] "g++" -fvisibility-inlines-hidden -fPIC -m64 -pthreads -O3 -finline-functions -Wno-inline -w -fvisibility=hidden -DBOOST_ALL_DYN_LINK=1 -DBOOST_ALL_NO_LIB=1 -DNDEBUG -I"." -c -o "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/cpplexer/re2clex/cpp_re.o" "libs/wave/src/cpplexer/re2clex/cpp_re.cpp" gcc.link.dll bin.v2/libs/wave/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_wave.so.1.69.0 "g++" -L"/tmp/build/boost_1_69_0/bin.v2/libs/chrono/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/date_time/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/filesystem/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden" -L"/tmp/build/boost_1_69_0/bin.v2/libs/thread/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden" -o "bin.v2/libs/wave/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_wave.so.1.69.0" -shared "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_cpp_exprgrammar.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_cpp_grammar.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_cpp_literalgrs.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_defined_grammar.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_predef_macros.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_re2c_lexer.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/instantiate_re2c_lexer_str.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/token_ids.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/wave_config_constant.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/cpplexer/re2clex/aq.o" "bin.v2/libs/wave/build/gcc-7.3.0/release/threading-multi/visibility-hidden/cpplexer/re2clex/cpp_re.o" "bin.v2/libs/filesystem/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_filesystem.so.1.69.0" "bin.v2/libs/thread/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_thread.so.1.69.0" "bin.v2/libs/date_time/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_date_time.so.1.69.0" "bin.v2/libs/chrono/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_chrono.so.1.69.0" "bin.v2/libs/system/build/gcc-7.3.0/release/threading-multi/visibility-hidden/libboost_system.so.1.69.0" -lrt -fPIC -m64 -pthreads -fvisibility=hidden -fvisibility-inlines-hidden -mimpure-text common.copy stage/lib/libboost_wave.so.1.69.0 cp "bin.v2/libs/wave/build/gcc-7.3.0/release/threadapi-pthread/threading-multi/visibility-hidden/libboost_wave.so.1.69.0" "stage/lib/libboost_wave.so.1.69.0" ln-UNIX stage/lib/libboost_wave.so ln -f -s 'libboost_wave.so.1.69.0' 'stage/lib/libboost_wave.so' The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: /tmp/build/boost_1_69_0 The following directory should be added to linker library paths: /tmp/build/boost_1_69_0/stage/lib However, when I try to build pgAgent 4.0 I have the following errors : sol114:/tmp/build/pgAgent-4.0.0-Source$ make CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) CMake Warning at cmake/FindBoost.cmake:839 (message): New Boost version may have incorrect or missing dependencies and imported targets Call Stack (most recent call first): cmake/FindBoost.cmake:950 (_Boost_COMPONENT_DEPENDENCIES) cmake/FindBoost.cmake:1618 (_Boost_MISSING_DEPENDENCIES) CMakeLists.txt:112 (FIND_PACKAGE) -- Boost version: 1.69.0 -- Found the following Boost libraries: -- filesystem -- regex -- date_time -- thread -- system -- chrono -- atomic -- -- ================================================================================ -- Configuration summary: -- -- Project : pgagent -- Description : pgAgent is a job scheduling engine for PostgreSQL -- Version : 4.0.0 -- -- PostgreSQL version string : PostgreSQL 10.6 -- PostgreSQL version parts : 10 -- PostgreSQL path : /appli/11.4.4.4.0-20181220-10.6 -- PostgreSQL config binary : /appli/11.4.4.4.0-20181220-10.6/bin/pg_config -- PostgreSQL include path : /appli/11.4.4.4.0-20181220-10.6/include -- PostgreSQL library path : /appli/11.4.4.4.0-20181220-10.6/lib -- PostgreSQL share path : /appli/11.4.4.4.0-20181220-10.6/share/postgresql -- -- Boost version : 1.69.0 -- Boost path : /tmp/build/boost_1_69_0 -- Boost include directory : /tmp/build/boost_1_69_0 -- Boost library directory : /tmp/build/boost_1_69_0/stage/lib -- Boost Static linking : NO -- ================================================================================ -- -- Configuring done -- Generating done -- Build files have been written to: /tmp/build/pgAgent-4.0.0-Source [ 11%] Built target run [ 22%] Building CXX object CMakeFiles/pgagent.dir/connection.cpp.o In file included from /tmp/build/boost_1_69_0/boost/thread/detail/platform.hpp:17:0, from /tmp/build/boost_1_69_0/boost/thread/mutex.hpp:12, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:22, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/config/requires_threads.hpp:47:5: error: #error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" # error "Compiler threading support is not turned on. Please set the correct command line options for threading: -pthread (Linux), -pthreads (Solaris) or -mthreads (Mingw32)" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/mutex.hpp:12:0, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:22, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/detail/platform.hpp:71:9: error: #error "Sorry, no boost threads are available for this platform." # error "Sorry, no boost threads are available for this platform." ^~~~~ In file included from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:22:0, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/mutex.hpp:18:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:12:0, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/thread_only.hpp:19:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/detail/thread.hpp:21:0, from /tmp/build/boost_1_69_0/boost/thread/thread_only.hpp:22, from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:12, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/detail/thread_heap_alloc.hpp:19:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/thread_only.hpp:26:0, from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:12, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/condition_variable.hpp:18:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread/detail/thread_group.hpp:10:0, from /tmp/build/boost_1_69_0/boost/thread/thread.hpp:13, from /tmp/build/boost_1_69_0/boost/thread.hpp:13, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/shared_mutex.hpp:31:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread.hpp:17:0, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/once.hpp:31:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ In file included from /tmp/build/boost_1_69_0/boost/thread.hpp:18:0, from /tmp/build/pgAgent-4.0.0-Source/include/job.h:16, from /tmp/build/pgAgent-4.0.0-Source/include/pgAgent.h:37, from /tmp/build/pgAgent-4.0.0-Source/connection.cpp:12: /tmp/build/boost_1_69_0/boost/thread/recursive_mutex.hpp:18:2: error: #error "Boost threads unavailable on this platform" #error "Boost threads unavailable on this platform" ^~~~~ I have no idea why the boost headers won't find the availability of threads as it has built fine with pthread : $ ldd /tmp/build/boost_1_69_0/stage/lib/libboost_system.so.1.69.0 libstdc++.so.6 => /usr/lib/64/libstdc++.so.6 libm.so.2 => /lib/64/libm.so.2 librt.so.1 => /lib/64/librt.so.1 libgcc_s.so.1 => /usr/lib/64/libgcc_s.so.1 libpthread.so.1 => /lib/64/libpthread.so.1 libc.so.1 => /lib/64/libc.so.1 Can anybody help me ? Best regards -- Eric Ce message électronique et tous les fichiers attachés qu'il contient sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le retourner à son émetteur. La publication, l'usage, la distribution, l'impression ou la copie non autorisée de ce message et des attachements qu'il contient sont strictement interdits. En cas d'urgence, composez le 17 ou le 112. Afin de contribuer au respect de l'environnement, merci de n'imprimer cet e-mail qu'en cas de necessite. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual to whom it is addressed. If you have received this email in error please send it back to the person that sent it to you. Unauthorized publication, use, dissemination, forwarding, printing or copying of this email and its associated attachments is strictly prohibited. In case of emergency, dial number 17 or 112. To contribute to the environmental protection, please print this e-mail only if necessary.

2 2

ASIO vs Beast DynamicBuffer use
by Cristian Morales Vega 02 Jan '19

02 Jan '19

Hi, I have just noticed that while ASIO passes DynamicBuffers as && (https://www.boost.org/doc/libs/1_68_0/doc/html/boost_asio/reference/async_r…) Beast passes them via reference (https://www.boost.org/doc/libs/1_68_0/libs/beast/doc/html/beast/ref/boost__…) I'm guessing this happens because ASIO thinks you are going to use dynamic_string_buffer/dynamic_vector_buffer as DynamicBuffer, while Beast thinks you are going to use flat_buffer/multi_buffer. In the second case doesn't make sense to give ownership of the DynamicBuffer to the initiation function because then you would not be able to look at the received data when the operation completes. Since ASIO DynamicBuffer implementations are just adaptors over string/vectors that you keep, it makes sense to move those adaptors, you still keep the string/vector with the data. Have I got it right? But this raises the question: what should I use in my own initiating functions? Regards.

2 3

My last message
by Osman Zakir 02 Jan '19

02 Jan '19

Hi, everyone. Did you guys see my last message? I really need to get a reply ASAP.

4 9

function template with a universal reference to a specific type
by Ireneusz Szcześniak 01 Jan '19

01 Jan '19

Hi, I'm writing to ask a C++ question, not specifically Boost-related, but this list is the best place I know. How can I write a function template, which has a parameter of the universal reference to a specific type? I can write a function template like this: template <typename T> void foo(T &&t) { // The primary template implementation. cout << "Primary: " << __PRETTY_FUNCTION__ << endl; } And so I can call this function with an expression of any value category, and any type, cv-qualified or not, like this: int main() { foo(1); int i = 1; foo(i); const int ci = 1; foo(ci); } In my code I need to provide different implementations of foo for different types (and these types are templated). How can I accomplish that? Best, Irek

5 11

Error: no member named 'GetModuleFileNameA' in namespace 'boost::winapi'; did you mean simply 'GetModuleFileNameA'?
by Osman Zakir 31 Dec '18

31 Dec '18

Hi again, everyone. When trying to build Boost 1.69.0 after having placed my installation of Python 3.7.1 above the one of Python 2.7.15, I got the error mentioned in the title of this email. It says at the end, " ...failed updating 4 targets... ...skipped 8 targets... ...updated 2381 targets... " The project-config.jam file I used is attached to this message.

1 0

Errors with 1.69 when compiling with /clr on MSVC
by Stian Zeljko Vrba 30 Dec '18

30 Dec '18

I get the following warning and error when compiling a C++/CLI file that includes boost 1.69. 1>c:\quinesoftwarebase\include\boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(114): error C2764: 'C': template parameter not used or deducible in partial specialization 'boost::is_member_function_pointer<Ret(Args...)>' 1>c:\quinesoftwarebase\include\boost\type_traits\detail\is_member_function_pointer_cxx_11.hpp(125): warning C4575: '__vectorcall' incompatible with the '/clr' option: converting to '__stdcall' Is there a workaround for this? -- Stian

3 3

Re: [Boost-users] [cfe-dev] [llvm-dev] Error: ISO C++17 does not allow 'register' storage class specifier [-Wregister], when building Boost 1.69.0
by Osman Zakir 25 Dec '18

25 Dec '18

I'll build using C++14 mode, then. I wonder if Python 3.7.1 has this issue as well? If it doesn't, then maybe Boost should switch over to that version of Python. ________________________________ From: Matthieu Brucher <matthieu.brucher(a)gmail.com> Sent: Tuesday, December 25, 2018 2:56 PM To: Oleg Smolsky Cc: Craig Topper; Osman Zakir; clang developer list; cfe-users(a)lists.llvm.org; llvm-dev(a)lists.llvm.org Subject: Re: [cfe-dev] [llvm-dev] Error: ISO C++17 does not allow 'register' storage class specifier [-Wregister], when building Boost 1.69.0 The issue comes in part form the Python headers that have the keyword. Unfortunately, this also means that there is an issue while building user code. But it's not a Boost code issue for this library, but a Python one. Regards, Matthieu Le mar. 25 déc. 2018 à 02:08, Oleg Smolsky via cfe-dev <cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org>> a écrit : Yes, this keyword is no longer valid starting from C++17: https://en.cppreference.com/w/cpp/keyword/register I realize that the "why" probably doesn't help you move forth with your problem, so here are a couple suggestions how to get over it: * Build Boost in C++14 mode with -std=c++14 * Cut out "register" from the Boost source and rebuild * Try a newer Boost version, it may have been fixed Oleg. On 2018-12-23 09:26, Craig Topper via cfe-dev wrote: This seems a better question for cfe-dev or cfe-users ~Craig On Sat, Dec 22, 2018 at 12:23 PM Osman Zakir via llvm-dev <llvm-dev(a)lists.llvm.org<mailto:llvm-dev@lists.llvm.org>> wrote: When trying to build Boost using LLVM, I had this error: " error: ISO C++17 does not allow 'register' storage class specifier [-Wregister] " I attached the project-config.jam file I used to this message. Someone please help me out (if there's someone on here who can). _______________________________________________ LLVM Developers mailing list llvm-dev(a)lists.llvm.org<mailto:llvm-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev _______________________________________________ cfe-dev mailing list cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev _______________________________________________ cfe-dev mailing list cfe-dev(a)lists.llvm.org<mailto:cfe-dev@lists.llvm.org> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev -- Quantitative analyst, Ph.D. Blog: http://blog.audio-tk.com/ LinkedIn: http://www.linkedin.com/in/matthieubrucher

2 1

Problem downloading 1.69.0 for Windows
by tim＠raisedbar.net 24 Dec '18

24 Dec '18

Hi, Windows Defender is blocking my download from https://www.boost.org/users/history/version_1_69_0.html as it is identified as being unsafe. Can anybody advise, please? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 2

[Asio/Beast] Any non-obvious reasons for no bind_executor_and_allocator?
by Sorin Fetche 23 Dec '18

23 Dec '18

Hi, As I'm looking to modernize an older C++03 project based on Boost.Asio to use C++17 and the net TS api, I am not ready yet to give up on using lambdas for completion handlers. Boost.Asio and Boost.Beast have some utilities for correctly implementing asynchronous composed operations but from them only asio::bind_executor seems to be applicable to lambdas. And the problem is that it only associates an executor with a (lambda) object; I didn't find any utility for associating an allocator too. Could there be any reason for a utility that associates both an executor and an allocator with an object to not work correctly when implementing asynchronous operations? Or is it just that this utility has not been implemented yet? I did come across the paper "Networking TS Associations for Call Wrappers"[1], but I didn't see any mention there about bind_executor or something similar for allocators or why this kind of approach wouldn't work. I would be very happy if I could write something like: asio::post( socket_.get_executor(), bind_executor_and_allocator_from( handler_, [...] { self_.handler_(...); })); and, unless I'm missing something, such a utility could be implemented similarly to the existing asio::bind_executor. Thank you, Sorin [1] http://open-std.org/JTC1/SC22/WG21/docs/papers/2018/p1133r0.html

2 7

Update for C++17 register keyword error question
by Osman Zakir 23 Dec '18

23 Dec '18

This is the error I get when trying to build Boost 1.69.0 with LLVM: "error: ISO C++17 does not allow 'register' storage class specifier [-Wregister]". I've also sent an email about this to the LLVM developer mailing list. I've attached the project-config.jam file to this message. Please let me know how to fix this. Thanks in advance.

2 2

[uuid] constexpr uuid from string and ""_uuid literal
by Tobias Loew 23 Dec '18

23 Dec '18

Hi, while searching for constexpr GUID from string generators, I found https://gist.github.com/AlexBAV/b58e92d7632bae5d6f5947be455f796f . Since I still work with VS 2015, I wrote a C++11 constexpr version incl. boost-uuid generators. If there's interest adding this to boost uuid, please have a look at https://github.com/tobias-loew/constexpr-GUID-cpp-11 Tobias -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

2 1

Patch for using boost-1_69_0 and clang-cl
by JR Cary 23 Dec '18

23 Dec '18

I found that I had to apply the attached patch to build another project that uses boost with clang-cl, or else I got an error that complained about the non-existence of std::snprintf. John Cary

2 1

Error when trying to build Boost 1.69.0 with LLVM
by Osman Zakir 22 Dec '18

22 Dec '18

When trying to build Boost 1.69.0 with LLVM, I had an error about the "register" keyword, regarding the removal of it in C++17. I searched on the Web and found out that I can use the "-Wno-register" flag to calm down Clang 6.0.0. What do I do in Clang 8.0.0? The same?

1 0

boost_1_19_0 fails to build random using clang-cl
by JR Cary 21 Dec '18

21 Dec '18

This is now more of an FYI, as I can disable random and get the build I need. boost 1_69_0 clang version 8.0.0 (trunk 349323) Windows 10 Build command: ./b2 toolset=clang-win runtime-link=shared link=shared define=BOOST_TEST_DYN_LINK cxxflags='-DBOOST_THREAD_DONT_USE_CHRONO' linkflags='-DBOOST_THREAD_DONT_USE_CHRONO' address-model=64 threading=multi variant=release -s NO_COMPRESSION=1 --layout=system --abbreviate-paths -j2 --without-python --without-mpi --without-log --without-math stage The first error is Creating library bin.v2\libs\random\build\clng-win-8.0.0\rls\adrs-mdl-64\thrd-mlt\boost_random.lib and object bin.v2\libs\random\build\clng-win-8.0.0\rls\adrs-mdl-64\thrd-mlt\boost_random.exp^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptEnumProvidersA referenced in function "public: __cdecl boost::random::random_device::impl::impl(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0impl@random_device@random@boost@@QEAA@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptAcquireContextA referenced in function "public: __cdecl boost::random::random_device::impl::impl(class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > const &)" (??0impl@random_device@random@boost@@QEAA@AEBV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@@Z)^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptReleaseContext referenced in function "public: __cdecl boost::random::random_device::impl::~impl(void)" (??1impl@random_device@random@boost@@QEAA@XZ)^M random_device.obj : error LNK2019: unresolved external symbol __imp_CryptGenRandom referenced in function "public: unsigned int __cdecl boost::random::random_device::operator()(void)" (??Rrandom_device@random@boost@@QEAAIXZ)^M bin.v2\libs\random\build\clng-win-8.0.0\rls\adrs-mdl-64\thrd-mlt\boost_random.dll : fatal error LNK1120: 4 unresolved externals^M clang-cl: error: linker command failed with exit code 1120 (use -v to see invocation)^M The build succeeds upon adding --without-random to the build invocation. I tried attaching the full log, but then the message was rejected for being too large. ..................John Cary

1 0

Questions about Boost.Multiprecision..
by A Z 20 Dec '18

20 Dec '18

I want to be performing some algebraic functions work on cpp_rational which I will be using templates with the following type to configure precision (and scale?) #include <boost/multiprecision/cpp_int.hpp> in order to avoid the use of floating point types. --What is the #include statement for cpp_rational? I can't manage to find it. -When using non-floating point, is there a method to obtain a variable precision pi, or do I have to use arccos(-1); ? What is the file to import for that? -If I want to import a non-floating-point (cpp_rational) library power, nth root, trigonometry, all the useful function, what is the #include and the file in boost for that?

2 1

Having some trouble with bootstrapping Boost to use LLVM
by Osman Zakir 20 Dec '18

20 Dec '18

I changed the project-config.jam file in my Boost source tree to have Boost.Build use LLVM, but then when I used "bootstrap" command after, I saw that it was still using MSVC. When I looked at the project-config.jam file again at that point, I saw that its content had been reverted back to the default one for building with MSVC. What's going on? What do I need to do? Is there an argument I need to provide to the bootstrap command here so that it'll keep the configuration file content that I want it to? And is there no help command that would let me see what arguments, if any, I can pass to the tool? Another thing I want to ask is whether or not I need to have Boost.Built emit library files with a .bc extension to be able to link them with code I want to build using the Emscripten compiler. I ask because Emscripten needs compiled libraries to have been compiled to LLVM bitcode, and when Emscripten itself does this it adds the .bc extension instead of the .lib one.

2 2

integer_log2.hpp header deprecation using Boost
by Michael Powell 19 Dec '18

19 Dec '18

Hello, I am receiving a deprecation warning: d:\dev\boost.org\boost_1_69_0\boost\pending\integer_log2.hpp(7): note: This header is deprecated. Use <boost/integer/integer_log2.hpp> instead. The immediate includes are these: #include <boost/uuid/uuid.hpp> #include <boost/uuid/uuid_io.hpp> #include <boost/uuid/random_generator.hpp> But I am also leveraging Spirit, Format, Variant, Optional, to name a few, that I can determine. I am not including "integer_log2.hpp" directly, so I wondered which library(ies) might have this as a dependency? Spirit? Phoenix, via Spirit? Format? Thoughts? Suggestions? Cheers, Michael Powell

1 1

odeint: how to solve ODE as you go without deciding upfront what the interval is?
by Yuri 19 Dec '18

19 Dec '18

The function 'integrate' solves ODE for a pre-defined interval of time. What if I don't know what the interval is? I just need a few values, and then I would like to decide if I need more values, and when to stop. I don't want to just solve for some arbitrarily large interval, because this would waste CPU. On the other hand, choosing the shorter original interval and then continuing would introduce unnecessary errors if one would do this too many times. It seems like either the 'observer' function should have another argument: 'stop', or the interface should allow continuation. Yuri

1 0

[Spirit] X3 thread-safety
by Igor R 19 Dec '18

19 Dec '18

Hello, In my project I run x3-based parsers in parallel, using openmp. I've just moved from boost 1.64 to 1.68, and the parsers now cause segfault (heap corruption) - quite consistently, every time I run the program. OTOH, with 1.64 it never crashed. Before I begin to debug it in depth, I'd like to know if there's some known issue with Spirit's thread-safety in Boost 1.68. Did anyone encounter thread-safety issie with the recent Spirit versions? Thanks.

1 0

Build boost asio http server examples single threaded using c++03
by Eric Curtin 19 Dec '18

19 Dec '18

Hi Guys, I was wondering if anyone could help me out building all the boost asio http server examples from: https://github.com/boostorg/asio/tree/develop/example/cpp03/http But catch is, I need to use c++03/98, single threaded without dependencies on std::thread, boost::thread or posix threads. I also need static linking to all the other boost libraries. Also want to compile with g++ -O3 -flto on x86_64 Linux. How can I build these examples like this? This is also a question on stackoverflow: https://stackoverflow.com/questions/53822438/building-boost-asio-without-th… Lets say the build environment is this one: curtine/dockerfiles-fat:ubuntu18.04 Regards, Eric

2 1

[Asio] Combining use_future with strands
by Sorin Fetche 19 Dec '18

19 Dec '18

Hi, Is there a way to combine the special use_future completion token with a strand? Something with the meaning of: - the asynchronous operation should pass the result to the future it returns, and - the internal operations of it (if any) should run in a strand Code snippet: asio::io_context io_context; asio::io_context::strand strand(io_context); std::future<void> f = async_my_operation(io_context, <params>, asio::use_future); //________________________________________How to add the strand here ^^^ ? The code area where I would like to apply this is in this test program: https://github.com/sorf/cpp-dev-new/blob/abf9d831a0b82fb81751eee6cfa498d3b9… The self contained program and its output is here: https://wandbox.org/permlink/pF5Hbm6jqPOmEKbO As a background, the test program I wrote is based on these Boost.Asio examples: - for strand usage (i.e. bind_executor): https://github.com/boostorg/asio/blob/develop/example/cpp03/tutorial/timer5… - for composed operations: https://github.com/boostorg/asio/blob/develop/example/cpp11/operations/comp… and implements a composed operation that runs multiple internal operations in parallel and in series. Similar to the constructor of a socket or a timer object, the operation receives as a parameter an io_context; it doesn't offer an overload that receives a strand object directly. The operation is then tested with callback completion, callback completion in a strand, future and future + strand (where the test fails). Thank you, Sorin

5 7

How to implement a visitor pattern over an AST
by Michael Powell 19 Dec '18

19 Dec '18

Hello, I have an AST successfully building, generating text file, and subsequently Spirit Qi parsing for verification purposes. Now I want to implement a visitor pattern over that AST, somehow... For "calculators" and such, "evaluating" those expressions is one thing; however, this AST is not that. It is closer akin to a parsed Xml or Json model/tree. In other words, I'd like for it to feel sort of like an iterator if that's even possible. It should have contextual awareness where it is at all times, etc, perhaps "incrementing" is a depth first analysis. In particular I have in mind to iterate the expected and actual AST results in order to perform the verification. In other words, I might do something like this: auto expected_it = ast_visitor{&expected}; auto actual_it = ast_visitor{&actual}; REQUIRE(expected_it); REQUIRE(actual_it); REQUIRE(*expected_it == *actual_it); // Rinse and repeat ++expected_it; ++actual_it; REQUIRE(*expected_it == *actual_it); I wonder if something like this is even possible from the Boost libraries? Or interested to hear any insights on the subject. For that matter, I wonder it is more appropriate to simply implement the logical operators. Thanks! Michael Powell

4 7