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

[interprocess] Determine size of managed_shared_memory
by Kai Benndorf 12 Oct '19

12 Oct '19

Hi all, I want to create a managed_shared_memory in exactly the size I needed. Therefore I do something like this: size = sizeof( common_managed_shared_memory ); size += sizeof( MyClassInSharedMem ); managed_shared_memory segment(create_only, "name", size ); MyClassInSharedMem allocates itself some memory by segment->allocate(). I added this also to the size, but get a boost::interprocess::bad_alloc exception on allocating this additional memory. Are there some magic bytes I forgot to add? Many thanks in advance Kai

3 2

boost::filtered_graph filtering on vertex color... if I only had a colormap
by Brian Davis 19 Jul '19

19 Jul '19

Lets say I have a graph g (of type graph_t) and a color map (boy I wish I had a colormap): typedef boost::property_map<graph_t, boost::vertex_color_t>::type color_map_t; or is it? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); or maybe? auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::vertex_color_t>(indexmap); or possibly some goop found on the internet? boost::make_iterator_property_map(color_map.begin(), boost::get(boost::vertex_index, data_->g), color_map[0]) or other internet goop? typedef boost::property_map<GraphType, boost::vertex_color_t>::type color_map_t; color_map_t colorMap; boost::color_map(colorMap)) or other internet goop?? std::vector<int> colorMap(num_vertices(g), boost::white_color); so confused... (certainly not surprised why bgl is not a part of stl) Can someone help explain the various types and ways of specifying colormaps and the logic for each way and means? and a function (if I could get that far without VS syntax highlighter going bonkers and gobs of compiler errors.. you know the type): make_pretty(g, colormap ) which colors the graph colormap and a filter struct for boost::filtered_graph<Graph, EdgePredicate, VertexPredicate> (where I wonder why if I only want to filter vertices I have to set boost::keep_all for EdgePredicate... sigh... I know the answer... and also know how long it found me to find/figure out boost::keep_all - and if you are looking for boost::keep_all and found it here... your welcome ;-) ) and modifying (probably incorrectly) boost::filtered_graph example to: template <typename ColorMap> struct vertex_color_filter_eq { vertex_color_filter_eq() { } vertex_color_filter_eq(ColorMap colormap/*, boost::default_color_type c*/) : m_colormap(colormap)/*, m_c(c)*/ { } template <typename Vertex> bool operator()(const Vertex& v) const { return 0 < get(m_colormap, v); //return c < get(m_colormap, v); } ColorMap m_colormap; //boost::default_color_type m_c; }; auto indexmap = boost::get(boost::vertex_index, g); auto colors = boost::make_vector_property_map<boost::default_color_type>(indexmap); // some where here I would call make_pretty(g, colors) typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors); // boost::filtered_graph<graph_t, boost::keep_all, VertexPredicate> boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); // Later say if I could get it compile and better if it compiled and worked I could move on and auto color = boost::red_color; typedef property_map<graph_t, boost::vertex_color_t>::type ColorMap_t; vertex_color_filter<ColorMap_t> filter(colors, color); boost::filtered_graph<graph_t, boost::keep_all, vertex_color_filter> fg(g, filter); Maybe if I color them yellow, I can then reach the wizard pull back the curtain and ask how to create a color map... If I only had a color map.

4 6

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

Re: [Boost-users] [release] Boost 1.68.0 Beta 1 -> warnings in gil, locale, geometry, asio, ublas, interprocess, atomic
by Frédéric 09 Aug '18

09 Aug '18

Here are some more warnings while using the libraries: * gil: boost/gil/extension/toolbox/image_types/indexed_image.hpp:190:5: warning: les qualificatifs de type sont ignorés sur le type retourné par la fonction [-Wignored-qualifiers] const std::size_t num_colors() const { return _num_colors; } ^~~~~ boost/gil/extension/dynamic_image/any_image_view.hpp:41:63: warning: unused parameter 'v' [-Wunused-parameter] template <typename T> result_type operator()(const T& v) const { return num_channels<T>::value; } boost/gil/extension/dynamic_image/algorithm.hpp:147:70: warning: unused parameter 'src' [-Wunused-parameter] template <typename V, typename Value> static void apply(const V& src, const Value& val) { throw std::bad_cast();} ^ boost/gil/extension/dynamic_image/algorithm.hpp:147:88: warning: unused parameter 'val' [-Wunused-parameter] template <typename V, typename Value> static void apply(const V& src, const Value& val) { throw std::bad_cast();} ^ boost/gil/extension/dynamic_image/image_view_factory.hpp:178:140: warning: unused parameter 'cc' [-Wunused-parameter] typename color_converted_view_type<any_image_view<ViewTypes>, DstP, CC>::type color_converted_view(const any_image_view<ViewTypes>& src,CC cc) {~ ^ boost/gil/extension/dynamic_image/image_view_factory.hpp:201:144: warning: unused parameter 'cc' [-Wunused-parameter] typename color_converted_view_type<any_image_view<ViewTypes>, DstP, CC>::type any_color_converted_view(const any_image_view<ViewTypes>& src,CC cc) {~ ^ boost/gil/io/device.hpp:446:31: warning: unused parameter 'data' [-Wunused-parameter] void write( const byte_t* data ^ boost/gil/io/device.hpp:447:31: warning: unused parameter 'count' [-Wunused-parameter] , std::size_t count ) ^ boost/gil/io/device.hpp:471:35: warning: unused parameter 'data' [-Wunused-parameter] std::size_t read( byte_t* data ^ boost/gil/io/device.hpp:472:35: warning: unused parameter 'count' [-Wunused-parameter] , std::size_t count ) ^ * locale: boost/locale/utf.hpp:224:17: warning: cette instruction peut poursuivre son chemin [-Wimplicit-fallthrough=] c = (c << 6) | ( tmp & 0x3F); ^ boost/locale/utf.hpp:225:13: note: ici case 2: ^~~~ boost/locale/utf.hpp:231:17: warning: cette instruction peut poursuivre son chemin [-Wimplicit-fallthrough=] c = (c << 6) | ( tmp & 0x3F); ^ boost/locale/utf.hpp:232:13: note: ici case 1: ^~~~ * geometry: boost/geometry/formulas/vertex_longitude.hpp:340:32: warning: unused parameter 'lon1' [-Wunused-parameter] static inline CT apply(CT& lon1, ^ boost/geometry/formulas/vertex_longitude.hpp:341:32: warning: unused parameter 'lat1' [-Wunused-parameter] CT& lat1, ^ boost/geometry/formulas/vertex_longitude.hpp:343:32: warning: unused parameter 'lat2' [-Wunused-parameter] CT& lat2, ^ boost/geometry/formulas/vertex_longitude.hpp:344:38: warning: unused parameter 'vertex_lat' [-Wunused-parameter] CT const& vertex_lat, ^ boost/geometry/formulas/vertex_longitude.hpp:345:32: warning: unused parameter 'alp1' [-Wunused-parameter] CT& alp1, ^ boost/geometry/formulas/vertex_longitude.hpp:346:44: warning: unused parameter 'azimuth_strategy' [-Wunused-parameter] Strategy const& azimuth_strategy) ^ boost/geometry/strategies/spherical/intersection.hpp:544:81: warning: unused parameter 'b2' [-Wunused-parameter] Point2 const& b1, Point2 const& b2, // in ^ boost/geometry/algorithms/detail/envelope/segment.hpp:156:61: warning: unused parameter 'lon1' [-Wunused-parameter] static inline void compute_box_corners(CalculationType& lon1, ^ boost/geometry/algorithms/detail/envelope/segment.hpp:158:61: warning: unused parameter 'lon2' [-Wunused-parameter] CalculationType& lon2, ^ boost/geometry/strategies/spherical/intersection.hpp:544:81: warning: unused parameter 'b2' [-Wunused-parameter] Point2 const& b1, Point2 const& b2, // in ^ * asio (windows 32 and 64 bits with mingw w64 + g++ 8.2.0) : /softs/win32-mingw-8.2.0/release/boost/include/boost/asio/detail/impl/win_iocp_socket_service_base.ipp: Dans la fonction membre « boost::system::error_code boost::asio::detail::win_iocp_socket_service_base::cancel(boost::asio::> /softs/win32-mingw-8.2.0/release/boost/include/boost/asio/detail/impl/win_iocp_socket_service_base.ipp:253:51: warning: transtypage entre types de fonctions incompatibles de « FARPROC » {aka « int (__attribute__((stdcall)) *)()> cancel_io_ex_t cancel_io_ex = (cancel_io_ex_t)cancel_io_ex_ptr; ^~~~~~~~~~~~~~~~ * ublas: /softs/lin64-gcc-8.2.0/debug/boost/include/boost/numeric/ublas/matrix_expression.hpp:2224:17: warning: cette instruction « if » ne protège pas… [-Wmisleading-indentation] if (it2_ != it2_end_) ^~ /softs/lin64-gcc-8.2.0/debug/boost/include/boost/numeric/ublas/matrix_expression.hpp:2227:21: note: …cette instruction, mais l'indentation de cette dernière est trompeuse car elle fait croire qu'elle est gardée par le « if » if (it2_ != it2_end_) { ^~ boost/numeric/ublas/functional.hpp:1673:57: warning: unused parameter 'size_i' [-Wunused-parameter] size_type upper_element (size_type i, size_type size_i, size_type j, size_type size_j) { ^ boost/numeric/ublas/functional.hpp:1673:88: warning: unused parameter 'size_j' [-Wunused-parameter] size_type upper_element (size_type i, size_type size_i, size_type j, size_type size_j) { ^ * interprocess (windows mingw-w64 + g++ 8.2.0 32/64 bits): In file included from boost/interprocess/errors.hpp:41, from boost/interprocess/exceptions.hpp:24, from boost/interprocess/sync/file_lock.hpp:24, from Progs/delypse-transfer.cpp:32: boost/interprocess/detail/win32_api.hpp:189:8: warning: « struct boost::interprocess::winapi::IUnknown_BIPC » a des fonctions virtuelles et un destructeur non virtuel accessible [-Wnon-virtual-dtor] struct IUnknown_BIPC ^~~~~~~~~~~~~ boost/interprocess/detail/win32_api.hpp:200:8: warning: la classe de base « struct boost::interprocess::winapi::IUnknown_BIPC » a un destructeur non virtuel accessible [-Wnon-virtual-dtor] struct IWbemClassObject_BIPC : public IUnknown_BIPC ^~~~~~~~~~~~~~~~~~~~~ boost/interprocess/detail/win32_api.hpp:200:8: warning: « struct boost::interprocess::winapi::IWbemClassObject_BIPC » a des fonctions virtuelles et un destructeur non virtuel accessible [-Wnon-virtual-dtor] boost/interprocess/detail/win32_api.hpp:306:8: warning: la classe de base « struct boost::interprocess::winapi::IUnknown_BIPC » a un destructeur non virtuel accessible [-Wnon-virtual-dtor] struct IWbemContext_BIPC : public IUnknown_BIPC ^~~~~~~~~~~~~~~~~ boost/interprocess/detail/win32_api.hpp:306:8: warning: « struct boost::interprocess::winapi::IWbemContext_BIPC » a des fonctions virtuelles et un destructeur non virtuel accessible [-Wnon-virtual-dtor] boost/interprocess/detail/win32_api.hpp:345:8: warning: la classe de base « struct boost::interprocess::winapi::IUnknown_BIPC » a un destructeur non virtuel accessible [-Wnon-virtual-dtor] struct IEnumWbemClassObject_BIPC : public IUnknown_BIPC ^~~~~~~~~~~~~~~~~~~~~~~~~ boost/interprocess/detail/win32_api.hpp:345:8: warning: « struct boost::interprocess::winapi::IEnumWbemClassObject_BIPC » a des fonctions virtuelles et un destructeur non virtuel accessible [-Wnon-virtual-dtor] boost/interprocess/detail/win32_api.hpp:369:8: warning: la classe de base « struct boost::interprocess::winapi::IUnknown_BIPC » a un destructeur non virtuel accessible [-Wnon-virtual-dtor] struct IWbemServices_BIPC : public IUnknown_BIPC ^~~~~~~~~~~~~~~~~~ boost/interprocess/detail/win32_api.hpp:369:8: warning: « struct boost::interprocess::winapi::IWbemServices_BIPC » a des fonctions virtuelles et un destructeur non virtuel accessible [-Wnon-virtual-dtor] boost/interprocess/detail/win32_api.hpp:518:8: warning: la classe de base « struct boost::interprocess::winapi::IUnknown_BIPC » a un destructeur non virtuel accessible [-Wnon-virtual-dtor] struct IWbemLocator_BIPC : public IUnknown_BIPC ^~~~~~~~~~~~~~~~~ boost/interprocess/detail/win32_api.hpp:518:8: warning: « struct boost::interprocess::winapi::IWbemLocator_BIPC » a des fonctions virtuelles et un destructeur non virtuel accessible [-Wnon-virtual-dtor] In file included from boost/interprocess/errors.hpp:41, from boost/interprocess/exceptions.hpp:24, from boost/interprocess/sync/file_lock.hpp:24, from Progs/delypse-transfer.cpp:32: boost/interprocess/detail/win32_api.hpp: Dans la fonction « bool boost::interprocess::winapi::get_system_time_of_day_information(boost::interprocess::winapi::system_timeofday_information&) »: boost/interprocess/detail/win32_api.hpp:1676:58: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> dll_func::get(dll_func::NtQuerySystemInformation); ^ boost/interprocess/detail/win32_api.hpp: Dans la fonction « bool boost::interprocess::winapi::unlink_file(const char*) »: boost/interprocess/detail/win32_api.hpp:1892:78: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> (NtSetInformationFile_t)dll_func::get(dll_func::NtSetInformationFile); ^ boost/interprocess/detail/win32_api.hpp:1894:94: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> NtQueryObject_t pNtQueryObject = (NtQueryObject_t)dll_func::get(dll_func::NtQueryObject); ^ boost/interprocess/detail/win32_api.hpp:1966:85: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> NtOpenFile_t pNtOpenFile = (NtOpenFile_t)dll_func::get(dll_func::NtOpenFile); ^ boost/interprocess/detail/win32_api.hpp:1967:73: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> NtClose_t pNtClose = (NtClose_t)dll_func::get(dll_func::NtClose); ^ boost/interprocess/detail/win32_api.hpp: Dans la fonction « bool boost::interprocess::winapi::get_file_mapping_size(void*, long long int&) »: boost/interprocess/detail/win32_api.hpp:2413:63: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> (NtQuerySection_t)dll_func::get(dll_func::NtQuerySection); ^ boost/interprocess/detail/win32_api.hpp: Dans la fonction « bool boost::interprocess::winapi::get_semaphore_info(void*, long int&, long int&) »: boost/interprocess/detail/win32_api.hpp:2426:86: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> (winapi::NtQuerySemaphore_t)dll_func::get(winapi::dll_func::NtQuerySemaphore); ^ boost/interprocess/detail/win32_api.hpp: Dans la fonction « bool boost::interprocess::winapi::query_timer_resolution(long unsigned int*, long unsigned int*, long unsigned int*) »: boost/interprocess/detail/win32_api.hpp:2437:98: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> (winapi::NtQueryTimerResolution_t)dll_func::get(winapi::dll_func::NtQueryTimerResolution); ^ boost/interprocess/detail/win32_api.hpp: Dans la fonction « bool boost::interprocess::winapi::query_performance_counter(long long int*) »: boost/interprocess/detail/win32_api.hpp:2444:57: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> dll_func::get(dll_func::QueryPerformanceCounter); ^ boost/interprocess/detail/win32_api.hpp: Dans la fonction « bool boost::interprocess::winapi::query_performance_frequency(long long int*) »: boost/interprocess/detail/win32_api.hpp:2451:59: warning: transtypage entre types de fonctions incompatibles de « boost::interprocess::winapi::farproc_t » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::interprocess:> dll_func::get(dll_func::QueryPerformanceFrequency); ^ * atomic (OSX): boost/include/boost/atomic/detail/ops_gcc_x86_dcas.hpp:269:113: warning: unused parameter 'order' [-Wunused-parameter] static BOOST_FORCEINLINE storage_type exchange(storage_type volatile& storage, storage_type v, memory_order order) BOOST_NOEXCEPT

1 1

ASIO: custom service which works with spawn/yield
by Cristian Morales Vega 02 Aug '18

02 Aug '18

Hi, I have implemented a custom service using Boost 1.67 which works mostly OK, but I have noticed it always returns success when using spawn/yield. The following simplified sample shows the problem: ------------------------------------------------ #include <boost/asio.hpp> #include <boost/asio/spawn.hpp> #include <boost/beast/core/bind_handler.hpp> #include <iostream> class Service : public boost::asio::io_context::service { public: static boost::asio::io_context::id id; typedef int implementation_type; Service(boost::asio::io_context &io_context) : boost::asio::io_context::service(io_context) {} void construct(implementation_type &) {} void destroy(implementation_type &) {} }; boost::asio::io_context::id Service::id; template <typename Service> class BasicObject : protected boost::asio::basic_io_object<Service> { public: explicit BasicObject(boost::asio::io_context &io_context) : boost::asio::basic_io_object<Service>(io_context) {} template <typename ConnectHandler> auto async_method(ConnectHandler &&handler) { BOOST_ASIO_CONNECT_HANDLER_CHECK(ConnectHandler, handler) typeCheck; boost::asio::async_completion<ConnectHandler, void(const boost::system::error_code &)> init(handler); boost::system::error_code ec = boost::asio::error::already_started; boost::asio::post( boost::beast::bind_handler(std::move(init.completion_handler), std::move(ec))); return init.result.get(); } }; int main() { boost::asio::io_context ioContext; BasicObject<Service> myObject(ioContext); #if 1 boost::asio::spawn(ioContext, [&](boost::asio::yield_context yield) { boost::system::error_code ec; myObject.async_method(yield[ec]); std::clog << ec << std::endl; }); #else myObject.async_method([](const boost::system::error_code &ec) { std::clog << ec << std::endl; }); #endif ioContext.run(); return 0; } ------------------------------------------------ The version not using spawn prints "system:114", the one using spawn prints "system:0". What am I doing wrong? Thanks.

6 18

[GIL] Boost gil and constexpr
by Eloi Du Bois 01 Aug '18

01 Aug '18

Hi, It seems that the development on boost::gil is starting again on boost 1.68, and I have an advise: I think boost::gil would strongly benefits on using constexpr in the code, it would make a lot of things statically resolved. There's a huge work to put this everywhere, but I think it would be nice. Just an idea. Thanks,

3 3

Re: [Boost-users] [boost] [release] Boost 1.68.0 Beta 1 -> warnings in filesystem, locale, thread, stacktrace, container
by Frédéric 30 Jul '18

30 Jul '18

1 0

Boost Spirit X3: populating different objects
by Matthieu Brucher 29 Jul '18

29 Jul '18

Hi all, I want to design a parser that can populate two maps while parsing. They have a slightly different values (key is a string in both cases), but I didn't see an example where this was done. Hence I'm not even sure this is possible? Would be easier, otherwise I need to add another check to see what kind of value is populated before I insert it inside my maps? Cheers, Matthieu -- Quantitative analyst, Ph.D. Blog: http://blog.audio-tk.com/ LinkedIn: http://www.linkedin.com/in/matthieubrucher

1 0

Boost Spirit X3 and spaces
by Matthieu Brucher 29 Jul '18

29 Jul '18

Hi, What is the best strategy to handle spaces with X3? The files I want to parse have sometimes spaces or tabs for separators, but I also need to scan number that have an attached suffix (so x3::double_ >> *x3::char_). If now I want to parse groups of strings, starting with a rule like const auto pin = x3::rule<class pin, std::string>() = x3::alpha >> *x3::char_; what is the best to create a vector of these? *pin or pin % ' ' and will the latter also handle tabs by default? Cheers, Matthieu -- Quantitative analyst, Ph.D. Blog: http://blog.audio-tk.com/ LinkedIn: http://www.linkedin.com/in/matthieubrucher

1 0

storing functions obtained with boost.dll as class fields
by Sean Farrow 29 Jul '18

29 Jul '18

Hi, I'm in the process of converting a project being compiled with msvc 2017 to use boost.dll. I've got a shared library loading and need to obtain and store a function in a class-level field. The function has the following typedef: typedef error_status_t (WINAPI *nvdaControllerTestIfRunningFunc)(void); I think my main issue is what shared_libary.Get<t> returns. Any help appreciated. Kind regards Sean.

1 0

Re: [Boost-users] [release] Boost 1.68.0 Beta 1 -> warnings in filesystem, locale, thread, stacktrace, container
by Frédéric 29 Jul '18

29 Jul '18

Hi, I have tested 1.68.0 on linux x86_64 with the following compilers: - g++ 8.2.0, - clang++ 5.0.2, - mingw-w64 + g++ 8.2.0 cross compiling to windows 32 bits, - mingw-w64 + g++ 8.2.0 cross compiling to windows 64 bits, - clang++ 5.0.2 cross compiliing to OSX 10.9 32 bits, - clang++ 5.0.2 cross compiliing to OSX 10.9 64 bits. I did not find any major issue. Just those warnings while building the libraries: * filesystem (g++ 8.2.0 and clang++ 5.0.2 on linux x86_64): libs/filesystem/src/operations.cpp: Dans la fonction « int {anonymous}::readdir_r_simulator(DIR*, dirent*, dirent**) »: libs/filesystem/src/operations.cpp:2126:18: warning: « int readdir_r(DIR*, dirent*, dirent**) » est obsolète [-Wdeprecated-declarations] { return ::readdir_r(dirp, entry, result); } ^~~~~~~~~ In file included from /usr/include/features.h:423, from /softs/gcc-8.2.0/include/c++/8.2.0/x86_64-pc-linux-gnu/bits/os_defines.h:39, from /softs/gcc-8.2.0/include/c++/8.2.0/x86_64-pc-linux-gnu/bits/c++config.h:508, from /softs/gcc-8.2.0/include/c++/8.2.0/cstddef:49, from ./boost/config/compiler/gcc.hpp:165, from ./boost/config.hpp:39, from ./boost/filesystem/operations.hpp:18, from libs/filesystem/src/operations.cpp:68: /usr/include/dirent.h:189:12: note: déclaré ici extern int __REDIRECT (readdir_r, ^~~~~~~~~~ * locale (many more than that one about deprecated std::auto_ptr): I wonder when auto_ptr will be removed but it would be nice to change it to unique_ptr. In file included from libs/locale/src/util/default_locale.cpp:10: ./boost/locale/util.hpp:180:28: warning: « template<class> class std::auto_ptr » est obsolète [-Wdeprecated-declarations] BOOST_LOCALE_DECL std::auto_ptr<base_converter> create_utf8_converter(); ^~~~~~~~ In file included from /softs/gcc-8.2.0/include/c++/8.2.0/bits/locale_conv.h:41, from /softs/gcc-8.2.0/include/c++/8.2.0/locale:43, from ./boost/locale/util.hpp:10, from libs/locale/src/util/default_locale.cpp:10: /softs/gcc-8.2.0/include/c++/8.2.0/bits/unique_ptr.h:53:28: note: déclaré ici template<typename> class auto_ptr; ^~~~~~~~ * thead with mingw w64 cross compiling to windows 32 bits on linux x86_64 with g++ 8.2.0: I guess this warning is due to the fact that time_t is 32 bits on windows 32 bits so this looks dangerous to me. libs/thread/src/win32/thread_primitives.cpp: Dans la fonction « boost::detail::win32::ticks_type boost::detail::win32::{anonymous}::get_tick_count_init() »: libs/thread/src/win32/thread_primitives.cpp:97:120: warning: transtypage entre types de fonctions incompatibles de « boost::winapi::FARPROC_ » {aka « int (__attribute__((stdcall)) *)() »} vers « boost::detail::win32::detail::gettickcount64_t » {aka « long long unsigned int (__attribute__((stdcall)) *)() »} [-Wcast-function-type] (boost::detail::win32::detail::gettickcount64_t)boost::winapi::get_proc_address(hKernel32, "GetTickCount64"); * stacktrace (windows 32 and 64 bits): In file included from ./boost/winapi/file_management.hpp:17, from ./boost/stacktrace/detail/safe_dump_win.ipp:20, from ./boost/stacktrace/safe_dump_to.hpp:210, from ./boost/stacktrace/frame.hpp:20, from ./boost/stacktrace/detail/frame_unwind.ipp:15, from libs/stacktrace/build/../src/basic.cpp:14: ./boost/winapi/overlapped.hpp:38:9: warning: le C++ ISO interdit les structures anonymes [-Wpedantic] }; ^ * iostreams (windows 64 bits): libs/iostreams/src/mapped_file.cpp: Dans la fonction membre « void boost::iostreams::detail::mapped_file_impl::try_map_file(boost::iostreams::detail::mapped_file_impl::param_type) »: libs/iostreams/src/mapped_file.cpp:324:29: warning: comparaison d'expressions entières de types signés différents: « boost::iostreams::stream_offset » {aka « long long int »} et « boost::iostreams::mapped_file_source::size_type » {aka « long long unsigned int »} [-Wsign-compare] (SIZE_T) (size_ != max_length ? size_ : 0), ~~~~~~^~~~~~~~~~~~~ gcc.compile.c++ bin.v2/libs/iostreams/build/gcc-8.2.0/debug/link-static/target-os-windows/threading-multi/gzip.o * container (OSX 32 and 64 bits, clang 5.0.2): many locations with this warning: In file included from libs/container/src/alloc_lib.c:24: In file included from libs/container/src/dlmalloc_ext_2_8_6.c:36: libs/container/src/dlmalloc_2_8_6.c:4085:27: warning: 'sbrk' is deprecated [-Wdeprecated-declarations] char* base = (char*)CALL_MORECORE(0); ^ libs/container/src/dlmalloc_2_8_6.c:1714:37: note: expanded from macro 'CALL_MORECORE' #define CALL_MORECORE(S) MORECORE_DEFAULT(S) ^ libs/container/src/dlmalloc_2_8_6.c:666:26: note: expanded from macro 'MORECORE_DEFAULT' #define MORECORE_DEFAULT sbrk ^ /softs/osxcross-10.9-5.0.2/bin/../SDK/MacOSX10.9.sdk/usr/include/unistd.h:580:1: note: 'sbrk' has been explicitly marked deprecated here __deprecated ^ /softs/osxcross-10.9-5.0.2/bin/../SDK/MacOSX10.9.sdk/usr/include/sys/cdefs.h:156:37: note: expanded from macro '__deprecated' #define __deprecated __attribute__((deprecated)) ^

1 0

Re: [Boost-users] building boost 1.67/1.68b1 on osx with emscripten 1.38
by danielle amethyst brake 27 Jul '18

27 Jul '18

> > > > > "how do I set the default architecture when building boost?" > > > > address-model=64 architecture=x86 > > > Indeed, using these two commands as ./b2 address-model=64 architecture=x86 changes both of those properties as expected. however, if I use them in conjunction with *toolset=emscripten*, the problem I originally asked about persists: ./b2 toolset=emscripten address-model=64 architecture=x86 Performing configuration checks - default address-model : 32-bit - default architecture : none Building the Boost C++ Libraries. - symlinks supported : yes error: No best alternative for libs/context/build/asm_sources next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc ... [more similar alternatives omitted for brevity --dab] - C++11 mutex : no - lockfree boost::atomic_flag : yes - Boost.Config Feature Check: cxx11_hdr_tuple : no - Boost.Config Feature Check: cxx11_lambdas : no - Boost.Config Feature Check: cxx11_noexcept : no - Boost.Config Feature Check: cxx11_nullptr : no - Boost.Config Feature Check: cxx11_rvalue_references : no - Boost.Config Feature Check: cxx11_template_aliases : no - Boost.Config Feature Check: cxx11_thread_local : no - Boost.Config Feature Check: cxx11_variadic_templates : no - Boost.Config Feature Check: cxx11_auto_declarations : no - Boost.Config Feature Check: cxx11_constexpr : no - Boost.Config Feature Check: cxx11_defaulted_functions : no - Boost.Config Feature Check: cxx11_final : no - Boost.Config Feature Check: cxx11_hdr_mutex : no *Error: ambiguity found when searching for best transformation* *Trying to produce type 'SEARCHED_LIB' from: * *Generators that succeeded:* * - searched-lib-generator* * - emscripten.searched-lib-generator* *First generator produced: * * - { %.no-action-icudata.SEARCHED_LIB }* *Second generator produced: * * - { %.no-action-icudata.SEARCHED_LIB }* to renew focus, the problem I am trying to solve is the last part there, ambiguity when searching for best transformation. it goes away if i disable icu, but it just yields another similar error. it was suggested that I need to provide the default architecture to solve the problem, but the way suggested to do that so far have not worked. your help is appreciated! Danielle Brake

4 4

Re: [Boost-users] Boost-users Digest, Vol 4962, Issue 4
by danielle amethyst brake 27 Jul '18

27 Jul '18

On Wed, Jul 25, 2018 at 2:38 PM <boost-users-request(a)lists.boost.org> wrote: > Send Boost-users mailing list submissions to > boost-users(a)lists.boost.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.boost.org/mailman/listinfo.cgi/boost-users > or, via email, send a message with subject or body 'help' to > boost-users-request(a)lists.boost.org > > You can reach the person managing the list at > boost-users-owner(a)lists.boost.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Boost-users digest..." > > > Today's Topics: > > 1. Re: building boost 1.67/1.68b1 on osx with emscripten 1.38 > (Oliver Kowalke) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 25 Jul 2018 20:37:18 +0200 > From: Oliver Kowalke <oliver.kowalke(a)gmail.com> > To: boost-users <boost-users(a)lists.boost.org> > Subject: Re: [Boost-users] building boost 1.67/1.68b1 on osx with > emscripten 1.38 > Message-ID: > < > CA+wfc194-XJZ9dspcJBA844+x1EPphQfRnUr_E8WBjOAyCnUCg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > default architecture : none > > you have time set the architecture > > Thanks for the advice. i just spent the last few hours flailing wildly trying to do this. Please accommodate my noob-ness here, as I have never had to set the default architecture before when building Boost. I tried setting it at the call to `b2`, with `b2 architecture=x86 ...`, and it did not effect this problem; the default architecture persists at `none` to my dismay. I have tried editing a user-config.jam file, but I just don't grok what I need to do here. at the risk of sounding like "can you do it for me?", I would like to ask "how do I set the default architecture when building boost?" danielle > danielle amethyst brake via Boost-users <boost-users(a)lists.boost.org> > schrieb am Mi., 25. Juli 2018, 20:11: > > > Hey Boost, > > I am trying to build Boost, ideally in its entirety, with emscripten. I > > am using emscripten 1.38.8, and either Boost 1.67 or the 1.68.b1, and am > on > > OSX 10.13. Both Boost versions fail. > > > >

2 1

State of latest RC
by Michael Powell 26 Jul '18

26 Jul '18

Hello, What is the state of the latest RC? I saw some reports that the build was a non-starter, then a patched RC, then no further reports after that? Or have I missed something? Thanks! Cheer, Michael W Powell

1 0

[GIL] read/write jpeg image from/to a buffer, not a file
by Frédéric 26 Jul '18

26 Jul '18

Hi, Is it possible to read/write an image as JPEG from/into a memory buffer instead of a file? I found that reference which looks promising: https://stackoverflow.com/questions/16259659/read-a-jpeg-image-from-memory-… but grep -r jpeg_tag in boost/gil gives nothing (same with image_read_settings) and read_image has no documentation and not the same signature. Anyone knows something about that? F

3 4

building boost 1.67/1.68b1 on osx with emscripten 1.38
by danielle amethyst brake 25 Jul '18

25 Jul '18

Hey Boost, I am trying to build Boost, ideally in its entirety, with emscripten. I am using emscripten 1.38.8, and either Boost 1.67 or the 1.68.b1, and am on OSX 10.13. Both Boost versions fail. I bootstrapped as normal (`./bootstrap.sh`), and then invoke b2 to build. i want C++14, so invoke as ./b2 toolset=emscripten cxxflags=-std=c++14 I get this long message with the roadblock at the end: Performing configuration checks - default address-model : 32-bit - default architecture : none Building the Boost C++ Libraries. - symlinks supported : yes error: No best alternative for libs/context/build/asm_sources next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>elf <threading>multi <toolset>qcc not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>aapcs <address-model>32 <architecture>arm <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>aapcs <address-model>64 <architecture>arm <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>o32 <address-model>32 <architecture>mips1 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>power <binary-format>xcoff <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>power <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>32 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>32 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>clang not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>darwin not matched next alternative: required properties: <abi>sysv <address-model>64 <architecture>x86 <binary-format>mach-o <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>clang-win not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>intel not matched next alternative: required properties: <abi>ms <address-model>64 <architecture>x86 <binary-format>pe <threading>multi <toolset>msvc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>clang not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>gcc not matched next alternative: required properties: <abi>x32 <address-model>64 <architecture>x86 <binary-format>elf <threading>multi <toolset>intel not matched next alternative: required properties: <abi>sysv <address-model>32_64 <architecture>x86 <binary-format>mach-o <threading>multi not matched next alternative: required properties: <abi>sysv <architecture>combined <binary-format>mach-o <threading>multi not matched - C++11 mutex : yes - lockfree boost::atomic_flag : 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 - 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 *Error: ambiguity found when searching for best transformation* *Trying to produce type 'SEARCHED_LIB' from: * *Generators that succeeded:* * - searched-lib-generator* * - emscripten.searched-lib-generator* *First generator produced: * * - { %.no-action-icudata.SEARCHED_LIB }* *Second generator produced: * * - { %.no-action-icudata.SEARCHED_LIB }* I can get past this error by disabling icu, with ./b2 toolset=emscripten cxxflags=-std=c++14 --disable-icu but i just get a similar error. *Error: ambiguity found when searching for best transformation* *Trying to produce type 'SEARCHED_LIB' from: * *Generators that succeeded:* * - searched-lib-generator* * - emscripten.searched-lib-generator* *First generator produced: * * - { %.no-action-z.SEARCHED_LIB }* *Second generator produced: * * - { %.no-action-z.SEARCHED_LIB }* of course, using c++14 doesn't affect my problem whatsoever. can anybody help me? -- Danielle Brake Assistant Professor of Mathematics University of Wisconsin Eau Claire danibrake.org she/her/hers

2 1

remove_sink for a text_file_backend backed frontend crashed in ~locale
by Yang X 25 Jul '18

25 Jul '18

I am running on boost_1_54 (don't ask why but cpprestsdk only compiles on SLES12 with that boost version). I have a mysterious SIGABORT similar to what's reported here: https://www.boost.org/doc/libs/1_66_0/libs/log/doc/html/log/rationale/why_c… However even after I put the lines below in my application it still crashes: boost::filesystem::path::imbue(std::locale("C")); boost::filesystem::path::codecvt() I've realized that in all example code except for text_ostream_backend, the "remove_sink" call was not being used for unknown reason. So do I need to call "logging::core::get()->remove_all_sinks(); or remove_sink(sink)"? when I call my destructor for my logging module? The stack trace for the SIGABORT is shown below: (gdb) bt #0 0x00007fffea552d88 in abort () from /lib64/libc.so.6 #1 0x00007fffea58f1b4 in __libc_message () from /lib64/libc.so.6 #2 0x00007fffea594706 in malloc_printerr () from /lib64/libc.so.6 #3 0x00007fffea595453 in _int_free () from /lib64/libc.so.6 #4 0x00007fffefaeca66 in __gnu_cxx::new_allocator<std::string>::deallocate (this=0x7fff240aab88, __p=0x7fffb67fe228) at ../../../../suselinux-x8664/usr/include/C++/ext/new_allocator.h:110 #5 0x00007fffefaebac2 in std::_Vector_base<std::string, std::allocator<std::string> >::_M_deallocate (this=0x7fff240aab88, __p=0x7fffb67fe228, __n=3) at ../../../../suselinux-x8664/usr/include/C++/bits/stl_vector.h:174 #6 0x00007fffefaeafae in std::_Vector_base<std::string, std::allocator<std::string> >::~_Vector_base (this=0x7fff240aab88, __in_chrg=<optimized out>) at ../../../../suselinux-x8664/usr/include/C++/bits/stl_vector.h:160 #7 0x00007fffefaeaa26 in std::vector<std::string, std::allocator<std::string> >::~vector (this=0x7fff240aab88, __in_chrg=<optimized out>) at ../../../../suselinux-x8664/usr/include/C++/bits/stl_vector.h:416 #8 0x00007ffe900b9806 in boost::date_time::date_facet<boost::gregorian::date, char, std::ostreambuf_iterator<char, std::char_traits<char> > >::~date_facet() () from /opt/mycomp/tdobject/lib/libboost_log.so.1.54.0 #9 0x00007ffe900b9943 in boost::date_time::time_facet<boost::posix_time::ptime, char, std::ostreambuf_iterator<char, std::char_traits<char> > >::~time_facet() () from /opt/mycomp/tdobject/lib/libboost_log.so.1.54.0 #10 0x00007fffea23c4b4 in std::locale::_Impl::~_Impl() () from /usr/lib64/libstdc++.so.6 #11 0x00007fffea23c674 in std::locale::~locale() () from /usr/lib64/libstdc++.so.6 #12 0x00007ffe900b078c in boost::log::v2_mt_posix::aux::light_function<std::string (unsigned int)>::impl<boost::_bi::bind_t<boost::_bi::unspecified, boost::log::v2_mt_posix::sinks::(anonymous namespace)::date_and_time_formatter, boost::_bi::list2<boost::_bi::value<std::string>, boost::arg<1> > > >::destroy_impl(boost::log::v2_mt_posix::aux::light_function<std::string (unsigned int)>::impl_base*) () from /opt/mycomp/tdobject/lib/libboost_log.so.1.54.0 #13 0x00007ffe900b163a in boost::log::v2_mt_posix::sinks::text_file_backend::~text_file_backend() () from /opt/mycomp/tdobject/lib/libboost_log.so.1.54.0 #14 0x00007fffb3667607 in boost::detail::sp_ms_deleter<boost::log::v2_mt_posix::sinks::text_file_backend>::destroy ( this=0x7fff240a5628) at /usr/local/include/boost/smart_ptr/make_shared_object.hpp:57 #15 0x00007fffb366d916 in boost::detail::sp_ms_deleter<boost::log::v2_mt_posix::sinks::text_file_backend>::operator() ( this=0x7fff240a5628) at /usr/local/include/boost/smart_ptr/make_shared_object.hpp:87 #16 0x00007fffb366d0e3 in boost::detail::sp_counted_impl_pd<boost::log::v2_mt_posix::sinks::text_file_backend*, boost::detail::sp_ms_deleter<boost::log::v2_mt_posix::sinks::text_file_backend> >::dispose (this=0x7fff240a5610) at /usr/local/include/boost/smart_ptr/detail/sp_counted_impl.hpp:153 #17 0x00007fffb36568aa in boost::detail::sp_counted_base::release (this=0x7fff240a5610) at /usr/local/include/boost/smart_ptr/detail/sp_counted_base_gcc_x86.hpp:146 #18 0x00007fffb365696d in boost::detail::shared_count::~shared_count (this=0x7fff240a2870, __in_chrg=<optimized out>) at /usr/local/include/boost/smart_ptr/detail/shared_count.hpp:371 #19 0x00007fffb365a55e in boost::shared_ptr<boost::log::v2_mt_posix::sinks::text_file_backend>::~shared_ptr (this=0x7fff240a2868, __in_chrg=<optimized out>) at /usr/local/include/boost/smart_ptr/shared_ptr.hpp:328 ---Type <return> to continue, or q <return> to quit--- #20 0x00007fffb36516f5 in AZSDKInterface::~AZSDKInterface (this=0x7fff240a2620, __in_chrg=<optimized out>) at AZSDKInterface.cpp:471 #21 0x00007fffb3651790 in AZSDKInterface::~AZSDKInterface (this=0x7fff240a2620, __in_chrg=<optimized out>) at AZSDKInterface.cpp:512 #22 0x00007fffabdfd06a in DeleteTdObjectInterface (obj=0x7fff240a2620) at TdObjectInterface.cpp:267 #23 0x00007ffff28ae250 in S3Connector::~S3Connector (this=0x7fffb67fc160, __in_chrg=<optimized out>) at ../../lib/test/testconnector.cpp:190 #24 0x00007ffff28ae2ee in S3Connector::~S3Connector (this=0x7fffb67fc160, __in_chrg=<optimized out>) at ../../lib/test/testconnector.cpp:197 #25 0x00007ffff28ba27a in testclose_int (ErrInfo_p=0x7fff6abc3880, Cfg_p=0x7fff6abc2500) at ../../lib/test/testutils.cpp:599 #26 0x00007ffff28b31b8 in testvalidatelocation (ErrInfo_p=0x7fff6abc3880, strLocation_p=0x7fff6abc3b90 "/", strLocationLen=140, IsManifestFile=0 '\000') at ../../lib/test/testinterface.cpp:392 #27 0x00007ffff589e029 in UsingClauseNameErrCheck (NameValListPtr=0x7fffb67ff1d0, DescListPtr=0x7fffb67ff810, TVMFlavor=0x7fff6abd34e9 "\002") at ../../par/res/rescommon.c:3284 #28 0x00007ffff571515b in Do_CT (T=0x7fffb67ff9d0, LINK=0x7fff6abde280) at ../../par/res/resnamtb.c:14524 #29 0x00007ffff572d561 in SCAN (Tree=0x7fff6abde408, LINK=0x7fff6abde640) at ../../par/res/resnamtb.c:24988 #30 0x00007ffff57329dc in resnamtb (Tree=0x7fffb67ff9d0, ResGlobal=0x7fff6abefcf0, AccessRight=0 '\000', In_Create_Macro=0x7fff6abe2b61 "", ViewFo=0x7fff6abf4490, ResData=..., NextIId=0x7fff6abe2d98, TVMFound=...) at ../../par/res/resnamtb.c:26902 #31 0x00007ffff5855752 in SCAN (Tree=0x7fffb67fee63, LINK=0x7fff6abe2b50) at ../../par/res/resname.c:62197 #32 0x00007ffff5834c60 in Do_Stmt (T=0x7fffb67fee48, LINK=0x7fff6abe0db0) at ../../par/res/resname.c:48525 #33 0x00007ffff585065d in SCAN (Tree=0x7fff6abf4510, LINK=0x7fff6abe2b50) at ../../par/res/resname.c:59873 #34 0x00007ffff5860056 in resname (Tree_=0x7fff6abf4510, ResGlobal_=0x7fff6abefcf0, AccessRight_=0 '\000', In_Create_Macro_=0 '\000', ViewFo_=0x7fff6abf4490, TablePtr_=0x0, ColAccrFldLists=0x7fff6abefb90, ResData_=..., ThisStmtList_=0x7fffb67fede8, ReturnExpanded=0x0, EffTIDReq_=ResIDMayExist) at ../../par/res/resname.c:66798 #35 0x00007ffff56f311f in resolve (TSeg=0x7fffb67c0000) at ../../par/res/resolve.c:6470 #36 0x00007ffff6a881a9 in pardrivr (DispParams=..., MscArg=..., MsgLoc=140734984341520, TempReqSegLoc=140733395488768, TempUnityReqSegLoc=0, TskLoc=167784288, ReqCtx=0x7fffb5500000, SesCtx=0x7fffbc8fde20, ValidateContextSegPtr=0x7fff6abfb900) at ../../par/par/pardrivr.c:19518 #37 0x00007ffff1535639 in disprreq (Global=0x7fffbcafa000, TskCtx=0x7fffbcb1a8c8, SesCtx=0x7fffbc8fde20, Keep=0x7fff6abfd8c0, TskIndex=1, DumpMeCurrent=1 '\001', PrfGrp=0x7fff6abfdd14, FromSP=0 '\000', FromIPE=0 '\000', AppCat=StandardApp, AppErrorRet=0x0, TopLevel=1 '\001') at ../../dis/dis/disdrivr.c:4721 #38 0x00007ffff1535bd7 in Process_Request (Global=0x7fffbcafa000, TskCtx=0x7fffbcb1a8c8) at ../../dis/dis/disdrivr.c:5011 #39 0x00007ffff1535cc2 in sqldrivr_thread () at ../../dis/dis/disdrivr.c:5062 #40 0x00007ffff01b3c59 in tsknewthread (threadargp=<optimized out>) at tsk/tskport.c:1129 #41 0x00007fffef1f2744 in start_thread () from /lib64/libpthread.so.0 #42 0x00007fffea606aad in clone () from /lib64/libc.so.6 (gdb) Thanks for any hints or suggestions to work around this issue. And where do you suggest I report this bug to? Best regards, Yang new boost user

1 0

Trying to track down a possible serialisation issue
by tim＠raisedbar.net 25 Jul '18

25 Jul '18

Hi, I've been working on a bit of freeware on and off (which is probably my real issue). At some point my code began to crash when returning a deserialised object to calling code and I've now got some time to try and track down what's going on. One of my theories is that a change in Boost serialisation might be responsible. Can anybody please tell me if this library and/or its wide equivalent has changed since 1.6.0 and, if so, in which versions? Many thanks in advance for any information. Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

1 0

Boost [asio]
by randy 18 Jul '18

18 Jul '18

Hello , I’ve the following c++ call that gives me an “ Invalid Argument “ error : int Asio_Send_Pck(int iSendt,int Lsocket,char * Lbuff,int Len) { session* iTempSession = reinterpret_cast<session*>(Lsocket); boost::asio::async_write(iTempSession->socket() , boost::asio::buffer(Lbuff, Len), boost::bind(&session::handle_write, iTempSession, boost::asio::placeholders::error, iTempSession->data, iSendt )); return 0; }; Please may i know where's this invalide argument ? Thank you

3 2

setup_error: test unit with name 'free_test_function' registered multiple times
by dinesh kumar 12 Jul '18

12 Jul '18

Hi Team, Greetings for the day. I apologies if this is a duplicate case which is already reported, but I am unable to find a suitable answer for this. I have installed boost(1.67.0.1) via brew, and created a simple unit test case as below. #define BOOST_TEST_DYN_LINK #define BOOST_TEST_MODULE super #include <boost/test/unit_test.hpp> using namespace boost::unit_test; std::string uri; std::string versionNum; BOOST_AUTO_TEST_CASE( free_test_function ) { BOOST_CHECK(true /* test assertion */); } *Compiled this code as below.* g++ obj/main.o -L /Library/PostgreSQL/9.6/lib -L /usr/local/lib -L /usr/local/opt/openssl/lib/ -o test_integration -lpq -lcpprest -lboost_regex-mt -lboost_system-mt -lboost_thread-mt -lssl -lcrypto -lboost_chrono-mt -lboost_log-mt -lboost_locale-mt -lboost_date_time-mt -lboost_program_options-mt -lboost_stacktrace_noop-mt -lboost_filesystem-mt -lboost_unit_test_framework-mt test integration installation is completed. *Got the error, while I execute the binary.* ./test_integration libc++abi.dylib: terminating with uncaught exception of type boost::unit_test::framework::setup_error: test unit with name 'free_test_function' registered multiple times [1] 59619 abort ./test_integration *I have tried to debug the binary, which execution is successful.* lldb -- ./pgBucket_integration (lldb) target create "./pgBucket_integration" Current executable set to './pgBucket_integration' (x86_64). (lldb) r Process 60066 launched: './pgBucket_integration' (x86_64) Running 1 test case... *** No errors detected Process 60066 exited with status = 0 (0x00000000) I would like to request you to guide me on what/where I am missing. *Below are my g++ version details.* $ g++ --version Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1 Apple LLVM version 8.1.0 (clang-802.0.42) Target: x86_64-apple-darwin16.4.0 Thread model: posix InstalledDir: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin -- Regards, Dinesh manojadinesh.blogspot.com

2 3

building on OS X with custom gcc version
by Damien Hocking 12 Jul '18

12 Jul '18

All, I’m trying to get 1.65.1 compiled on OSX 10.13.5. I have gcc 8.1 installed and I’ve added it to user-config.jam in the home directory. When I run "bootstrap.sh —with-toolset=gcc" it uses the Darwin gcc toolset, if I try —with-toolset=gcc-8.1 I get an unknown toolset error. If I use the Darwin-based gcc version of b2 and try and build with gcc 8.1 I get this series of errors: error: No best alternative for libs/context/build/asm_sources. and also linker errors from an unknown option -h on ld. I’m assuming this is because b2 built with Darwin gcc doesn’t have the right options for gcc 8. Is there a way to force b2 to be built based on gcc 8 so it gets the assembly and linker options right? Damien

4 9

[release] Boost 1.68.0 Beta 1
by Marshall Clow 10 Jul '18

10 Jul '18

Boost release 1.67.0 beta 1 is now available at: https://dl.bintray.com/boostorg/beta/1.68.0.beta1/source/ The files are identical to the RC2 that was posted on Friday. The SHA256 checksums are as follows: 961d2bdc74c1499c931b32098842abba8883b1a89ef5c8f8f0ab0aff771a3ce5 boost_1_68_0_b1_rc2.7z 0364846258648e39908ca7cebfc2d2216eef6980c32aaf8276d2cfe73ef012e3 boost_1_68_0_b1_rc2.tar.bz2 d99105685a68907a76b0479ecde77915423246236ef0db9cb846c5bfc09b41f3 boost_1_68_0_b1_rc2.tar.gz 6158e0e961bfb0d8adeb2ea70337b08504668258025f0a873fb21eee3436d22e boost_1_68_0_b1_rc2.zip For details of what's in the release, see <http://www.boost.org/users/history/version_1_68_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

Boost::MSM do_actions while in state
by IgnacioVizzo 10 Jul '18

10 Jul '18

Is there any way to do this? Using boost::msm? I know for fact that you can implement transition actions using the library, I've searched a lot around the internet and I didn't find my answer. So basically let's say I want to do this: <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_1.png> boost_msm_1.png <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_1.png> diagram1.cpp <http://boost.2283326.n4.nabble.com/file/t371323/diagram1.cpp> #include <boost/msm/back/state_machine.hpp> #include <boost/msm/front/euml/euml.hpp> #include <iostream> using namespace boost::msm::front::euml; namespace msm = boost::msm; namespace fsm { BOOST_MSM_EUML_EVENT(trigger); BOOST_MSM_EUML_ACTION(transition_action) { template <class FSM, class EVT, class SourceState, class TargetState> void operator()(EVT const &, FSM &fsm, SourceState &, TargetState &) { std::cout << "-v- transition_action -v-" << std::endl; return; } }; BOOST_MSM_EUML_ACTION(guard) { template <class FSM,class EVT,class SourceState,class TargetState> bool operator()(EVT const& evt,FSM&,SourceState& ,TargetState&) { std::cout << "[guard]" << std::endl; return true; } }; BOOST_MSM_EUML_ACTION(entry_action) { template <class Event, class FSM, class STATE> void operator()(Event const &, FSM &, STATE &) { std::cout << "==>entry_action" << std::endl; return; } }; BOOST_MSM_EUML_ACTION(exit_action) { template <class Event, class FSM, class STATE> void operator()(Event const &, FSM &, STATE &) { std::cout << "<==exit_action" << std::endl; return; } }; BOOST_MSM_EUML_STATE((entry_action,exit_action), State1); // BOOST_MSM_EUML_STATE((entry_action,exit_action), State2); // define the transition table BOOST_MSM_EUML_TRANSITION_TABLE(( State1 == State1 + trigger[guard] / transition_action // State1 == State2 + trigger[guard] / transition_action ), transition_table) // BOOST_MSM_EUML_DECLARE_STATE_MACHINE((transition_table, State1), fsm) // create a state machine "on the fly" BOOST_MSM_EUML_DECLARE_STATE_MACHINE((transition_table, init_ << State1, no_action, no_action, attributes_ << no_attributes_, configure_ << no_configure_, no_action ), my_fsm) typedef msm::back::state_machine<my_fsm> fsm_t; } //namespace fsm int main(int argc, char const *argv[]) { fsm::fsm_t example_fsm; example_fsm.start(); example_fsm.process_event(fsm::trigger); example_fsm.process_event(fsm::trigger); return 0; } // OUTPUT // ==>entry_action // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action But I want the machine to DO an action ONCE the Entry_action has completed and BEFORE the states exits. This is sort of a token or mark, like it's used in petri nets and GRAFCETS, basically. I want to add this boost_msm_2.png <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_2.png> <http://boost.2283326.n4.nabble.com/file/t371323/boost_msm_2.png> And the output for should be something like / OUTPUT // ==>entry_action // -DO ACTION- // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action // -DO ACTION- // [guard] // <==exit_action // -v- transition_action -v- // ==>entry_action Thanks! -- Sent from: http://boost.2283326.n4.nabble.com/Boost-Users-f2553780.html

2 1

[python][container] map_indexing_suite for flat_map
by MM 09 Jul '18

09 Jul '18

Hello, I've tried to adapt using myfm = boost::container::flat_map<const T*, V>; with boost::python::map_indexing_suite class_< myfm, myfm* >("myfm") .def( map_indexing_suite<myfm>{} ) ; I get a compile errors: /usr/include/boost/python/detail/invoke.hpp:75:14: error: no match for call > to ‘(const > boost::python::detail::specify_a_return_value_policy_to_wrap_functions_returning<const > T*>) (const T*)’ > ... > Caller = boost::python::detail::caller<const T* (*)(std::pair<const T*, > V>&), default_call_policies ...> I would suspect that there is some function that returns the key_type of the flat_map and takes a single argument of the value_type, but I can't find any. If there's one, I would need pick a return value policy for it. MM

1 0

Boost.Beast includes CRLF in HTTP fields
by David Demelier 08 Jul '18

08 Jul '18

Hello, It looks like HTTP response headers are saved with trailing CRLF in the message upon receiption after (async_)read. Since it usually does not add additional valuable information, would it be possible to remove them in next version of Boost.Beast? It will be more convenient as you don't need to trim them when you want to capture the field value. Regards, -- David

4 11