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

Testing and faking ASIO I/O objects
by Cristian Morales Vega 31 Aug '18

31 Aug '18

How is people around here testing code which uses ASIO? I guess something like GIVEN("SOMETHING THAT STARTS BY DOING A NAME RESOLVER IS STARTED") fakeResolver.async_resolve("www.google.com", "80", HandlerCallingConnect); // This stores the completion handler (and an executor_work_guard) internally WHEN("THE RESOLVER RETURNS WITHOUT ERROR") fakeResolver.completeWithFakeResult("1.2.3.4", error_code()); // This post() the completion handler with the arguments you give it here io_context.poll(); THEN("A CONNECTION IS ATTEMPTED") EXPECT_CALL(fakeSocket, async_connect()); would be nice. But the "stores the completion handler" part doesn't look that simple. I have found some attempts online, but they seems to store the completion handlers into a vector of std::function and post them through std::bind, so possibly using the wrong executor, etc. There is any good set of ASIO I/O object fakes available?

2 2

linker errors with latest Visual Studio 15.8.2 update
by Damien 30 Aug '18

30 Aug '18

All, It looks like with 15.8.2 you might need to rebuild if you are linking to Boost compiled with earlier versions in the 15.6 or 15.7 series. Screens full of unresolved symbols..... Just a heads-up. Damien

1 0

[boost.test] parsing runtime arguments
by Olaf Peter 27 Aug '18

27 Aug '18

Hi, how get an 'user' API for the boost.test like this: testsuite_xyz -- --help or even testsuite_xyz -- --save-path=/foo to get the user aspects. I know I can get the args by int argc{ framework::master_test_suite().argc }; char** argv{ framework::master_test_suite().argv }; Further, at test/include/boost/test/utils/runtime/cla/parser.hpp are some utils used by boost.test self. Anyway, the problem rises to get the behaviour desribed above, simply using a global fixture with: fixture::fixture() { int argc{ utf::framework::master_test_suite().argc }; char** argv{ utf::framework::master_test_suite().argv }; for (int i = 0; i != argc; ++i) { std::cerr << "test_observer_fixture: " << argv[i] << "\n"; } } doesn't give the expected results - all the BOOST_AUTO_TEST_SUITE test cases are called even they depend on this arguments. Thanks, Olaf

2 3

Boost.Test BOOST_TEST/BOOST_REQUIRE_MESSAGE message arg problems
by Olaf Peter 27 Aug '18

27 Aug '18

Hello Boost Users, for my project I'm testing using BOOST_AUTO_TEST_SUITE and data driven test sets (BOOST_DATA_TEST_CASE). The goal is to check the proper working of a parser by checking success as such and compare the result with a "expected" data (string) vector. In case of parse error, I want to write the captured cout/cerr by boost.test into a file. In case of compare error the parsed result also shall be written to a file. The fragments show the concept/current state: namespace x3_test { // aka utils .... /* [Detect if boost test case failed]( * https://stackoverflow.com/questions/18466857/detect-if-boost-test-case-fail…) */ bool current_test_passing() { using namespace boost::unit_test; auto const id = framework::current_test_case().p_id; auto const test_results = results_collector.results(id); return test_results.passed(); } std::string report_diagnostic(fs::path const& test_case_name, std::string const& input, std::string const& result) { ... if(!x3_test::current_test_passing()) { // only write in case of failed test test_case_result_writer result_writer(test_case_name); result_writer.write(result); } return ss.str(); } } // x3_test ... BOOST_AUTO_TEST_SUITE(.... BOOST_DATA_TEST_CASE( declaration, dataset.input() ^ dataset.expect() ^ dataset.test_case_name(), code, expect_AST, test_case_name) { using attribute_type = ast::declaration; auto const parser = parser::declaration; x3_test::testing_parser<attribute_type> parse; auto [parse_ok, parsed_AST] = parse(code, parser); BOOST_TEST(parse_ok); BOOST_REQUIRE_MESSAGE(parse_ok, x3_test::report_diagnostic(test_case_name, code, parsed_AST) ); BOOST_TEST(parsed_AST == expect_AST, btt::per_element()); BOOST_REQUIRE_MESSAGE(x3_test::current_test_passing(), x3_test::report_diagnostic(test_case_name, code, parsed_AST) ); } BOOST_AUTO_TEST_SUITE_END() After some testing, the error count is twice the real (obviously here) but it's all above a work arround. It seems, that BOOST_REQUIRE_MESSAGE evaluates always the message predicate (shown by using --log_level=all) nevertheless the test case successed or failed. If failed it is streamed to the console. My first thoughs where that the message is called only in case of test failure which isn't true. The problem is now, that my report_diagnostic function write the test output (parsed_AST) to a special dir/file for later evaluating etc. The intuitive way would be: std::string report_diagnostic(fs::path const& test_case_name, std::string const& input, std::string const& result) { ... test_case_result_writer result_writer(test_case_name); result_writer.write(result); return ss.str(); } BOOST_REQUIRE_MESSAGE(parse_ok, // call diagnostic only in failure case and write then x3_test::report_diagnostic(test_case_name, code, parsed_AST) ); BOOST_REQUIRE_MESSAGE((parsed_AST == expect_AST, btt::per_element()), // call diagnostic only in failure case and write then x3_test::report_diagnostic(test_case_name, code, parsed_AST) ); Hence not depending on current_test_passing() any more. How to get this? Further, how can I get the captured std::cerr in case of '!parse_ok' inside report_diagnostic? Thanks, Olaf

2 10

[signals2] Warn unused result
by Deven 24 Aug '18

24 Aug '18

Hi, I am using boost::signals2 library for event callback mechanism. The event register callback function returns a boost::signals2::scope_connection object for optional disconnect by the function registering itself. I want to mandate using the returns result (scoped_connection) object by the user. So, I use the gcc attribute "__attribute__( ( warn_unused_result ) )" with the function. The problem is that the compiler does not warn for unused result. Any ideas, why would this happen? I am using Linux with g++ 4.8.4 and c++11 is enabled. Boost version: 1.67.0 I have attached a minimal working example. Thanks, -Deven

1 0

Setting cxxflags for intel compiler
by Michalke, Simon 23 Aug '18

23 Aug '18

Hi, in order to compile boost I need to tell the intel compiler which gcc version to use. I am trying to achive this with a user-config.jam using intel-linux : icpc : <cxxflags> -gcc-name=gcc-7 -gxx-name=g++-7 ; But none of the flags appear in the compile log. Which syntax am I supposed to use to get them working? Regards, Simon

3 2

[multi_index] Introducing C++17 terse key specification syntax
by Joaquin M López Muñoz 22 Aug '18

22 Aug '18

Following some ideas discussed about a year ago, I've added a new boost::multi_index::key construct allowing for a very terse specification of predefined key extractors in C++17 compliant environments. For instance, given struct phonebook_entry { std::string family_name; std::string given_name; std::string phone_number()const; }; int num_calls(const phonebook_entry&); a classical definition like typedef multi_index_container< phonebook_entry, indexed_by< ordered_unique< const_mem_fun<phonebook_entry,std::string,&phonebook_entry::phone_number> >, ordered_unique< global_fun<const phonebook_entry&,int,num_calls> >, ordered_non_unique< composite_key< phonebook_entry, member<phonebook_entry,std::string,&phonebook_entry::family_name>, member<phonebook_entry,std::string,&phonebook_entry::given_name> > > > > phonebook; can now be written as typedef multi_index_container< phonebook_entry, indexed_by< ordered_unique< key<&phonebook_entry::phone_number> >, ordered_unique< key<num_calls> >, ordered_non_unique< key<&phonebook_entry::family_name,&phonebook_entry::given_name> > > > phonebook; If you have a C++17 compiler, you can play with this new feature by simply copying https://github.com/boostorg/multi_index/blob/develop/include/boost/multi_in… into your local Boost installation. More info at https://www.boost.org/doc/libs/develop/libs/multi_index/doc/tutorial/key_ex… https://www.boost.org/doc/libs/develop/libs/multi_index/doc/reference/key_e… Comments and suggestions, specially before Boost 1.69 ships and this becomes more or less frozen, are most welcome. Best regards, Joaquín M López Muñoz

1 0

Where is the Wave Driver in Boost 1.86?
by Stirling Westrup 20 Aug '18

20 Aug '18

I recently tried to recompile an old version of the Wave Driver using the latest version of Boost::Wave and there were many cryptic warnings and errors. So, I figured I'd just upgrade to the latest copy of the source, only I cannot find it in the latest Boost::Wave, despite the documentation still referring to it. Nor does there appear to be an already-compiled tool supplied with the distro versions of Boost. (Something which has always been claimed by the docs, but has never been true in my experience -- which is why I was forced to originally compile it from source.) -- Stirling Westrup Programmer, Entrepreneur. https://www.linkedin.com/e/fpf/77228 http://www.linkedin.com/in/swestrup http://technaut.livejournal.com http://sourceforge.net/users/stirlingwestrup

1 0

Why I had to use-D_GLIBCXX_USE_CXX11_ABI=0 to get a Boost.Test unit test to build and run
by Arved Sandstrom 20 Aug '18

20 Aug '18

This is in the nature of a question, I am wondering *why* I had to use the -D_GLIBCXX_USE_CXX11_ABI=0 setting. This development is happening on Centos 7, where the system gcc/g++ is 4.8.5. So I recently built and installed gcc/g++ 8.2.0 from source, because I like Linux and prefer to try out C++17 stuff there rather than using a recent Visual Studio. That's just background. In any case I built the Boost Test module with ./b2 cxxflags="-stdlib=libc++ -std=c++14" linkflags="-stdlib=libc++ -std=c++14" going off suggestions I found. No evident problems there. After the install, among other things I end up with /usr/local/lib/libboost_unit_test_framework.so Now, I attempted to build a unit test with g++ -std=c++14 DocumentTest.cpp ../src/Document.cpp -I../include -L/usr/local/include -DBOOST_TEST_DYN_LINK -lboost_unit_test_framework The linker complained about an undefined reference for boost::unit_test::ut_detail::normalize_test_case_name[abi:cxx11](boost::unit_test::basic_cstring<char const>) Using nm -D on the shared library I see that the proper export symbol is there. abi:cxx11 seemed to offer some indication as to the problem, which is why after some experimentation I found that adding -D_GLIBCXX_USE_CXX11_ABI=0 to the unit test build command did the trick. The resulting a.out executes just fine (purely for debugging I made sure the unit test had a C++14 feature). I thought I sort of understood the ABI change business, gcc 5.1 before and after, but I guess I don't. What do I need to do, perhaps at the stage of building a Boost shared library, to not have to use that flag? Thanks for any wisdom. Arved Sandstrom

2 1

Specifying Compiler when invoking bootstrap.sh
by Michalke, Simon 20 Aug '18

20 Aug '18

Hello all, simple question: How do I specify the compiler that will be used to compile boost directly? I would like to provide the whole path. I have a big CMakeProject that depends on Boost. And boost should be preferably build with the same Compiler. Regards, Simon

3 5