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

Ranges
by Robert Jones 29 Jul '17

29 Jul '17

I realise this isn't strictly about Boost, but I'd appreciate if someone could say a few words about the current state of ranges in the standard, Boost or elsewhere. I'm familiar with the current Boost.Range, but thought there was a newer and rather different range library from Eric Neibler which was Boost compatible but not formally part of Boost, is that right? Are either of these part of the C++ standard, either now or planned, or is there anything else planned for the standard? Thx. Kind Regards Rob.

2 1

[filesystem] Strange "Function not implemented" exception from directory_iterator
by Robert Dailey 28 Jul '17

28 Jul '17

I'm using a recursive_directory_iterator on an Android ARM device (armeabi-v7a, clang compiler, API 15, LLVM STL). The exception I get comes from directory_iterator_increment in operations.cpp (when it does the dir_itr_increment() call and checks the `temp_ec` variable, there is a throw below that). The what() of the exception says: boost::filesystem::directory_iterator::operator++: Function not implemented: "/data/ziosk/content/Common/DemoMode/font" I doubt this is a permissions issue. Which function is not implemented? Is this a POSIX / LIBC issue? I have no idea at this point...

2 4

Boost.ProgramOptions issues porting from 1.56 to 1.64
by Dominique Devienne 28 Jul '17

28 Jul '17

I have an SVN-like "multi-command" single executable, i.e. exe [global-options] command [command-options] It uses two levels of option parsing. First level: typedef std::vector<std::string> UnparsedArgs; inline boost::program_options::typed_value<UnparsedArgs>* anyArgs() { return boost::program_options::value<UnparsedArgs>(); } options_description global_all_desc("Global Options", columns); global_all_desc.add_options() ("command", txtArg(), "Command to execute") ("cmdargs", anyArgs(), "Arguments for command") ...; // from http://stackoverflow.com/questions/15541498 // see also https://gist.github.com/randomphrase/10801888 po::positional_options_description pos; pos .add("command", 1) .add("cmdargs", -1); variables_map global_args; parsed_options parsed = po::command_line_parser(argc, argv) .options(global_all_desc) .positional(pos) // for implicit command and cmdargs above .allow_unregistered() // for command-specific arguments. .run(); po::store(parsed, global_args); std::vector<std::string> cmd_args = po::collect_unrecognized( parsed.options, po::include_positional ); Second level parsed_options reparsed = po::command_line_parser(cmd_args) .options(cmd_all_desc) .run(); po::store(reparsed, args_); // JIRA FOO-426 for (const auto& option : reparsed.options) { if (option.position_key >= 0) { std::ostringstream oss; for (const auto& token : option.original_tokens) { oss << token << ' '; } auto s = oss.str(); s.resize(s.size() - 1); err() << "Error: Too many commands: " << command() << ' ' << s << endl; return 1; } } in this particular case, the option that fails is ( "new", txtArgOpt(), "Creates a new group" ), with txtArgOpt() as below: inline boost::program_options::typed_value<std::string>* txtArg() { return boost::program_options::value<std::string>(); } inline boost::program_options::typed_value<std::string>* txtArgOpt(const std::string& implicit_value = "") { return txtArg()->implicit_value(implicit_value); } in the case that fails, the first parsing works fine, and remains ["--new", "groupA"] as cmd_args. in 1.56, reparsed.options contains 1 element: - [0] {string_key="new" position_key=-1 value={ size=1 } ...} boost::program_options::basic_option<char> + string_key "new" std::basic_string<char,std::char_traits<char>,std::allocator<char> > position_key -1 int - value { size=1 } std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > [size] 1 __int64 [capacity] 1 __int64 + [0] "GroupA" std::basic_string<char,std::char_traits<char>,std::allocator<char> > + [Raw View] 0x0000000009fae6c0 {...} std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > * - original_tokens { size=2 } std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > [size] 2 __int64 [capacity] 2 __int64 + [0] "--new" std::basic_string<char,std::char_traits<char>,std::allocator<char> > + [1] "GroupA" std::basic_string<char,std::char_traits<char>,std::allocator<char> > + [Raw View] 0x0000000009fae6e0 {...} std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > * unregistered false bool case_insensitive false bool but in 1.64, it contains 2 elements: - [0] {string_key="new" position_key=-1 value={ size=0 } ...} boost::program_options::basic_option<char> + string_key "new" std::basic_string<char,std::char_traits<char>,std::allocator<char> > position_key -1 int - value { size=0 } std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > [capacity] 0 __int64 + [allocator] allocator std::_Compressed_pair<std::_Wrap_alloc<std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,std::_Vector_val<std::_Simple_types<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,1> + [Raw View] {...} std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > - original_tokens { size=1 } std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > [capacity] 1 __int64 + [allocator] allocator std::_Compressed_pair<std::_Wrap_alloc<std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,std::_Vector_val<std::_Simple_types<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,1> + [0] "--new" std::basic_string<char,std::char_traits<char>,std::allocator<char> > + [Raw View] {...} std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > unregistered false bool case_insensitive false bool - [1] {string_key="" position_key=0 value={ size=1 } ...} boost::program_options::basic_option<char> + string_key "" std::basic_string<char,std::char_traits<char>,std::allocator<char> > position_key 0 int - value { size=1 } std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > [capacity] 1 __int64 + [allocator] allocator std::_Compressed_pair<std::_Wrap_alloc<std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,std::_Vector_val<std::_Simple_types<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,1> + [0] "GroupA" std::basic_string<char,std::char_traits<char>,std::allocator<char> > + [Raw View] {...} std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > - original_tokens { size=1 } std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > [capacity] 1 __int64 + [allocator] allocator std::_Compressed_pair<std::_Wrap_alloc<std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,std::_Vector_val<std::_Simple_types<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > >,1> + [0] "GroupA" std::basic_string<char,std::char_traits<char>,std::allocator<char> > + [Raw View] {...} std::vector<std::basic_string<char,std::char_traits<char>,std::allocator<char> >,std::allocator<std::basic_string<char,std::char_traits<char>,std::allocator<char> > > > unregistered false bool case_insensitive false bool This is copy/pasted from VS, sorry, a little hard to read, but basically 1.56 has #0 string_key = "new" position_key = -1 value = ["groupA"] original_tokens = ["--new", "groupA"] unregistered = false case_insensitive = false while 1.64 has 2 items: #0 string_key = "new" position_key = -1 value = [] original_tokens = ["--new"] unregistered = false case_insensitive = false #1 string_key = "" position_key = 0 value = ["groupA"] original_tokens = ["groupA"] unregistered = false case_insensitive = false as-if the arg to --new was now a positional parameter, instead of an optional arg to --new. And this triggers the work-around code that errors out I had put in place to catch cases when the old 1.56 code wouldn't complain about extra arguments (e.g. "exe ... cmd1 cmd1_args cmd2" would be silently accepted, despite the extra cmd2, or "exe ... cmd --arg1 read-only" was accepted, when "exe ... cmd --arg1 --read-only" was expected), and this even though the second parsing doesn't have .allow_unregistered(). I'm trying to understand what's going on; obviously there's some kind of semantic change with optional argument to switches. Could anyone shed some light on this please? I'm not sure how to proceed now. TIA, -DD

2 4

error: 'function' in namespace 'boost' does not name a template type
by jupiter 28 Jul '17

28 Jul '17

Hi, Cannot I define a following boost function? Any workarounds? typedef boost::function<bool (const uint32_t, const std::shared_ptr<boost::asio::streambuf> &)> Subscriber_t; Thank you. Kind regards,

2 2

using ssl::context in boost 1.53 versions
by dipti Burli 27 Jul '17

27 Jul '17

Hi , I am currently using boost 1.53 version. cannot upgrade to latest version. Using ssl asio. Here is my requirement. I need to support tls1.1.and tls1.2 protocol in the server, but not tls1.0 . As there are no options for tls1.1. and tls1.2 ,and context is not present with relevant tls1.1 and tls1.2 versions, I created the ssl::context with tlsv1 method and used long ssl_disallowed = SSL_OP_NO_SSLv2 | SSL_OP_NO_SSLv3 | SSL_OP_NO_TLSv1 | SSL_OP_NO_TLSv1_1 | SSL_OP_NO_TLSv1_2; ssl_disallowed &= ~SSL_OP_NO_TLSv1_2; ssl_disallowed &= ~SSL_OP_NO_TLSv1_1; SSL_CTX_set_options(myBoostSslcontext.native_handle(), ssl_disallowed|SSL_OP_SINGLE_DH_USE); But handshake seems to be failing for any other versions other than tlsv1. Can you please let me know how to I set the options so that my sserver can accept tls connections on tls1.1 and tls1.2 with boost version 1.53. Thanks in advance. Dipti

1 0

[mpl] [msm] wrong number of template arguments (120, should be at least 0)
by Alessandro Marzialetti 27 Jul '17

27 Jul '17

Hello, I'm working on a msm with a big transition table (120 elements) I already tried with #define BOOST_MPL_CFG_NO_PREPROCESSED_HEADERS then #define BOOST_MPL_LIMIT_LIST_SIZE <custom value> But I can't go over a size of 50 (including "boost/mpl/vector/vector50.hpp") Any idea on how I can make a bigger table? Thanks, Alessandro <http://www.boost.org/doc/libs/1_63_0/libs/mpl/doc/refmanual/cfg-no-preproce…>

3 2

[Boost Graph Dijkstra Shortest Path]: Could not deduce template argument
by Choppin, Simon 26 Jul '17

26 Jul '17

Hello all, I use boost graph library for some point cloud processing and have had great success. However, I'm struggling to compile Dijkstra shorted path on MSVC v140. I am using boost library 1.53 and compiling in 64 bit. I used the example as a starting point but when I try to compile I get the error: Error C2784 'E boost::detail::get(boost::detail::underlying_edge_desc_map_type<E>,const boost::detail::reverse_graph_edge_descriptor<EdgeDesc> &)': could not deduce template argument for 'boost::detail::underlying_edge_desc_map_type<E>' from 'double *' I understand the fundamental problem that the template can't deduce type, however I'm struggling to source the problem. My graph type is: typedef adjacency_list < vecS, vecS, undirectedS, no_property, property <edge_weight_t, double> > WeightedGraph; Because I'm using MSVC I use the suggested non parameter name version: property_map<WeightedGraph, vertex_index_t>::type indexmap = get(vertex_index, GraphW); property_map<WeightedGraph, edge_weight_t>::type weightmap; std::vector<Vertex> p(num_vertices(GraphW)); std::vector<double> d(num_vertices(GraphW)); Vertex s = vertex(indices.first, GraphW); Vertex s_end = vertex(indices.second, GraphW); dijkstra_shortest_paths (GraphW, s, &p[0], &d[0], weightmap, indexmap, std::less<double>(), closed_plus<double>(), (double)(std::numeric_limits<double>::max)(), (double)0, Custom_visitor(s_end) ); I'm using a custom visitor to stop processing early as in this stackoverflow post: https://stackoverflow.com/questions/32047840/make-boost-dijkstra-algorithm-… Any ideas? All help greatly appreciated. Simon C

1 0

how to generate PDF formate documentations of Boost?
by easior 23 Jul '17

23 Jul '17

Hi, all in the list. I plan to build boost documentation in pdf format for latest version of boost. However, it's no luck to me even following the link: http://www.boost.org/doc/libs/1_40_0/doc/html/boostbook/getting/started.html. I can only find HTML formatted documentation for boost. I don't know what about the relationship between boost and doxygen. I also have no idea about the mechanism of the boostbook. Any suggection? Thanks in advance, Easior Lars

4 4

Boost Regex - Alternation documentation example
by Nick 21 Jul '17

21 Jul '17

According to the Boost Regex documentation for Alternation (http://www.boost.org/doc/libs/1_64_0/libs/regex/doc/html/boost_regex/syntax…) Quoting a piece of the documentation: ----- |abc is not a valid expression, but (?:)|abc is and is equivalent, also the expression: (?:abc)?? has exactly the same effect. ----- Is the last expression: (?:abc)?? correct? Why does it need two '?' operators instead of only one? If I try this expression with the input "abc" the Boost engine does not match "abc" as I'd have expected. However the expression: (?:abc)? matches as expected. Nick

2 2

MS controlled email domains - not going to work
by Michael Caisse 20 Jul '17

20 Jul '17

The irony in sending this message is that the people who need to see it probably wont get it. We are having trouble with hotmail.com, live.com, msn.com, and outlook.com. Microsoft is filtering the dedicated IP address used by the mail lists and most recently has responded with: Not qualified for mitigation [ip address] Our investigation has determined that the above IP(s) do not qualify for mitigation. These IP(s) have previously received mitigations from deliverability support, and have failed to maintain patterns within our guidelines, so they are ineligible for additional mitigation at this time. We have tried to explain multiple times that the IP address has a new owner but we seem to be stuck in almost an auto-response loop. We will continue to try and get service unblocked; however, I would recommend that you dump your MS controlled accounts for Boost mail lists and use another service. michael -- Michael Caisse Ciere Consulting ciere.com

2 1