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

[boost.locale] linguistic case discrimination in translation
by Olaf Peter 19 Aug '18

19 Aug '18

Hello Users, I like to join two translation into a single one using the word 'and' if the code path require it, e.g. translation 1 is: "{1} error" and translation 2 is: "{1} warning" if the relevant err/warn counter are both != 0 I want to combine this statement using the mentioned 'and'. I guess, an example teels more than this here: see https://wandbox.org/permlink/HbnCLQKhHAb3eqZr or even on bottom. Line 89 ... 94 looks too complicated to me even for the translator which need an own context of the intend. I've seen a lot of dating formating flags, but nothings useful for my use case. BTW; does boost.locate still using auto_ptr? I had to add the option '-Wno-deprecated' to rid the warnings... Thanks, Olaf -----------------------8<-------------------------- #include <iostream> #include <boost/locale.hpp> struct context { std::size_t error_count; std::size_t warning_count; context() : error_count{ 0 } , warning_count{ 0 } { } }; struct failure_status { context const& ctx; failure_status(context const& ctx_) : ctx{ ctx_ } { } std::ostream& operator()(std::ostream& os) const; }; static inline std::ostream& operator<<(std::ostream& os, failure_status const& status) { return status(os); } namespace detail { struct error_message { std::size_t const count; explicit error_message(std::size_t count_) : count{ count_ } { } std::ostream& operator()(std::ostream& os) const { using boost::locale::format; using boost::locale::translate; if(count) { os << format(translate( "{1} error", "{1} errors", count)) % count ; } return os; } }; std::ostream& operator<<(std::ostream& os, error_message const& err_msg) { return err_msg(os); } struct warning_message { std::size_t const count; explicit warning_message(std::size_t count_) : count{ count_ } { } std::ostream& operator()(std::ostream& os) const { using boost::locale::format; using boost::locale::translate; if(count) { os << format(translate( "{1} warning", "{1} warnings", count)) % count ; } return os; } }; std::ostream& operator<<(std::ostream& os, warning_message const& warn_msg) { return warn_msg(os); } } // namespace detail std::ostream& failure_status::operator()(std::ostream& os) const { using detail::warning_message; using detail::error_message; using boost::locale::translate; bool const any_failure = [&] { return ctx.error_count || ctx.warning_count; }(); if(any_failure) { os << error_message(ctx.error_count); if(ctx.warning_count) { os << translate(" and "); // poor translator ... } os << warning_message(ctx.warning_count); os << translate(" generated."); } return os; } int main() { context ctx; ctx.error_count = 1; ctx.warning_count = 42; std::cout << failure_status(ctx) << "\n"; } ----------------------->8--------------------------

2 2

[release][build] Errors compiling 1.68.0 with VS2015 after VS2017
by Gavin Lambert 10 Aug '18

10 Aug '18

I first used the following to compile Boost 1.68.0 for VS2017: cd boost_1_68_0 bootstrap b2 -j8 --build-dir=build toolset=msvc-14.1 variant=debug,release link=shared threading=multi runtime-link=shared address-model=32,64 stage This appears to have built successfully, although I didn't review the logs. Afterwards, I tried to build it also for VS2015: b2 -j8 --build-dir=build15 toolset=msvc-14.0 variant=debug,release link=shared threading=multi runtime-link=shared address-model=32,64 stage This build output is full of these errors, however (not specific to Boost.Math, this is just one I happened to capture): Creating library build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.lib and object build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.exp msvc.manifest.dll build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.dll 'mt' is not recognized as an internal or external command, operable program or batch file. if exist "build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.dll.manifest" ( call "build15\boost\bin.v2\standalone\msvc\msvc-14.0\msvc-setup.bat" x86 >nul mt -nologo -manifest "build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.dll.manifest" "-outputresource:build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.dll;2" ) ...failed msvc.manifest.dll build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.dll build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.lib build15\boost\bin.v2\libs\math\build\msvc-14.0\debug\threading-multi\boost_math_c99l-vc140-mt-gd-x32-1_68.pdb... Am I missing some incantation? Oddly when I run a VS2015 Developer Command Prompt it also doesn't know where to find mt.exe. A VS2017 Developer Command Prompt finds it at C:\Program Files (x86)\Windows Kits\10\bin\10.0.17134.0\x86\mt.exe. (I'm not having any apparent problems compiling projects within VS2015, but possibly I haven't given it a thorough workout since recently upgrading VS2017.) On another machine (which only has VS2015 installed), the VS2015 Developer Command Prompt finds it at C:\Program Files (x86)\Windows Kits\8.1\bin\x86\mt.exe. I do have that same path and file on my PC, but it's not being found for some reason? Adding it to my PATH before running b2 doesn't help; I assume it's overriding this. It looks like the VS2015 Developer Prompt is putting C:\Program Files (x86)\Windows Kits\10\bin\x86 into my PATH, which exists but doesn't contain any tools. I managed to "fix" the VS2015 Developer Prompt by commenting out the line in "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\Tools\vcvarsqueryregistry.bat" that looks for the Windows 10 SDK. (Thereby allowing it to find the 8.1 SDK, which contains mt.exe.) After deleting the build15 directory and adding --reconfigure to the b2 incantation above, this seems to have allowed Boost to compile as well, but I find the whole thing a bit troubling. Is there a better way to resolve this?

2 1

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

[release] Boost 1.68.0
by Marshall Clow 09 Aug '18

09 Aug '18

Release 1.68.0 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains 1 new libraryand numerous enhancements and bug fixes for existing libraries. For details, including download links, see <https://www.boost.org/users/news/version_1.68.0> You can also download directly from: <https://dl.bintray.com/boostorg/release/1.68.0/> To install this release on your system, see <https://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team

2 1

[release] Boost 1.68.0 Release Candidate 1
by Marshall Clow 08 Aug '18

08 Aug '18

The release candidates for the 1.68.0 release are now available at: <https://dl.bintray.com/boostorg/release/1.68.0/source/> The SHA256 checksums are as follows: 59804d8fad02cf3b09485f3dbc0f9097c05fc1e0123f0c133b35a6c6f601109a boost_1_68_0_rc1.7z 7f6130bc3cf65f56a618888ce9d5ea704fa10b462be126ad053e80e553d6d8b7 boost_1_68_0_rc1.tar.bz2 da3411ea45622579d419bfda66f45cd0f8c32a181d84adfa936f5688388995cf boost_1_68_0_rc1.tar.gz 3b1db0b67079266c40b98329d85916e910bbadfc3db3e860c049056788d4d5cd boost_1_68_0_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 web site will be updated today as well.

3 4

[boost.beast] Example REST api's
by Sean Farrow 07 Aug '18

07 Aug '18

Hi, Does anyone have or know of any example rest api's written with boost.beast? Any help appreciated. Kind regards Sean.

1 0

Any plans to fix C++11 nullptr issues?
by James Walker 04 Aug '18

04 Aug '18

When Clang is compiling C++11 code, there may be a warning (-Wzero-as-null-pointer-constant) when 0 or NULL is used instead of nullptr. I've seen these warnings from Smart Ptr and Tokenizer in particular, but I suppose it's all over. This is still the case in 1.68.0 beta 1.

1 0

[boost.interprocess] Construct boost::basic_string with managed_shared_memory as memory soure crash.
by Zhiming Wang 03 Aug '18

03 Aug '18

Hi, I am using boost 1.65.1 interprocess lib, and tried to construct a string that is safe to store in a managed_shared_memory. Types are defined as below: using namespace boost::interprocess; using ShmSegment_t = boost::interprocess::managed_shared_memory; using SegmentMgr_t = boost::interprocess::managed_shared_memory::segment_manager; template <typename T> using Allocator_t = boost::interprocess::allocator<T, SegmentMgr_t>; using String_t = boost::interprocess::basic_string<char, std::char_traits<char>, Allocator_t<char>>; Code in problem is as below: using namespace boost::interprocess; ShmSegment_t segment(open_or_create, "Test", 1L << 31); const std::string stdStr("std_str"); String_t ipcStr( stdStr.c_str(), segment.get_segment_manager()); *// oops, crashed! * Crash backtrace is as below: #0 0x00007ffff7ab735c in boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>::get_size (this=0x441f0ff40024) at /usr/include/boost/interprocess/mem_algo/rbtree_best_fit.hpp:593 #1 0x00007ffff7ab157a in boost::interprocess::segment_manager_base<boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0u l> >::get_size (this=0x441f0ff40024) at /usr/include/boost/interprocess/segment_manager.hpp:113 #2 0x00007ffff7ab002d in boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> >::max_size (this=0x7fffeeffbe80) at /usr/include/boost/interprocess/allocators/allocator.hpp:164 #3 0x00007ffff7aaf34d in boost::container::allocator_traits<boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_fa mily, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::priv_max_size (a=...) at /usr/include/boost/container/allocator_traits.hpp:397 #4 boost::container::allocator_traits<boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_family, boost::interproc ess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::max_size (a=...) at /usr/include/boost/container/allocator_traits.hpp:331 #5 boost::container::container_detail::basic_string_base<boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boost::interprocess::mutex_famil y, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::max_size (this=0x7fffeeffbe80) at /usr/include/boost/container/string.hpp:354 #6 0x00007ffff7aae68a in boost::container::basic_string<char, std::char_traits<char>, boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boo st::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::max_size (this=0x7fffeeffbe80) at /usr/include/boost/container/string.hpp:1080 #7 0x00007ffff7aadb7a in boost::container::basic_string<char, std::char_traits<char>, boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boo st::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::priv_reserve (this=0x7fffeeffbe80, res_arg=21, null_terminate=true) at /usr/include/boost/container/string.hpp:2777 #8 0x00007ffff7aad62a in boost::container::basic_string<char, std::char_traits<char>, boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boo st::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::reserve (this=0x7fffeeffbe80, res_arg=21) at /usr/include/boost/container/string.hpp:1141 #9 0x00007ffff7aacbdf in boost::container::basic_string<char, std::char_traits<char>, boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boo st::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::assign (this=0x7fffeeffbe80, first=0x7fff5c000d60 "std_str", last=0x7fff5c000d75 "") at /usr/include/boost/container/string.hpp:1494 #10 0x00007ffff7aac719 in boost::container::basic_string<char, std::char_traits<char>, boost::interprocess::allocator<char, boost::interprocess::segment_manager<char, boost::interprocess::rbtree_best_fit<boo st::interprocess::mutex_family, boost::interprocess::offset_ptr<void, long, unsigned long, 0ul>, 0ul>, boost::interprocess::iset_index> > >::basic_string (this=0x7fffeeffbe80, s=0x7fff5c000d60 "std_str", a=...) at /usr/include/boost/container/string.hpp:741 I tried "p m_header" within GDB at /usr/include/boost/interprocess/mem_algo/rbtree_best_fit.hpp:593, and GDB told me the memory is not accessable. What's worse is that the issue seems not happening in very code path, that's it sometimes works and sometimes fails. Any insight is appreciated. Thanks.

3 2

Re: [Boost-users] ASIO: custom service which works with spawn/yield
by Vinnie Falco 03 Aug '18

03 Aug '18

On Thu, Aug 2, 2018 at 1:02 PM, Richard Hodges <hodges.r(a)gmail.com> wrote: > I think it's worth mentioning that although your code is very well written > and laid out, the horrid internals of asio mean that only ultra-experts can > read it. It really doesn't 'flow'. > > Surely something can be done (in asio and networking TS) in terms of > providing a cleaner, more logical interface for io_object and service > developers? I have thought about this for a few years and even made efforts to provide algorithms and types to make authoring code easier, but they were not successful. I don't think a "grand unifying theory" exists. However, I also think there is a LOT of room for documentation to grow and mature, and there is opportunity for authors to develop strong, well commented examples (something I strive for in Beast). With Networking TS as part of C++20 (or later), at last there will be one correct interface for doing asynchrony. This will incentivize book publishers and library authors to focus specifically on this networking interface to provide educational resources. In my Cppcon 2018 presentation I am also dedicating a couple of slides with guidance on how to learn Asio effectively and write correct programs. Regards

1 0

Serialization and class versioning
by tim＠raisedbar.net 02 Aug '18

02 Aug '18

Hi, I have an application that uses serialization for data storage/retrieval, based on Boost 1.67.0. I've implemented class versioning as per: https://www.boost.org/doc/libs/1_67_0/libs/serialization/doc/tutorial.html#v ersioning The overall archive stores a number of sub-classes, nested within the XML. However, I get a run-time exception thrown that I can't catch when one of my sub-classes (DisplayDefinition) returns from being read in. A bit of debugging found that the problem was caused by the class version number having a value of 0, whilst the file being read had a version number of 3 for the class in question. Here's the bit of the class responsible for the archiving: class DisplayDefinition: public MessageDefinition { ... private: friend std::ostream & operator<<(std::ostream &os, const DisplayDefinition &DD); friend std::istream & operator>>(std::istream &is, const DisplayDefinition &DD); friend class boost::serialization::access; template<class Archive> void serialize(Archive & myArchive, const unsigned int version) { try { const char * cLabelTag = "Label"; myArchive & boost::serialization::make_nvp( cLabelTag, wstrLabel); const char * cAddressBytesTag = "SysExAddressBytes"; myArchive & boost::serialization::make_nvp( cAddressBytesTag, vSysExAddressBytes); const char * cActionsTag = "Actions"; myArchive & boost::serialization::make_nvp( cActionsTag, myActions); const char * cStatesTag = "StateNames"; myArchive & boost::serialization::make_nvp( cStatesTag, StateLabels); const char * cLineCountTag = "LineCount"; myArchive & boost::serialization::make_nvp( cLineCountTag, nDisplayLineCount); const char * cLineLengthTag = "LineLength"; myArchive & boost::serialization::make_nvp( cLineLengthTag, nDisplayLength); const char * cStripCountTag = "StripCount"; myArchive & boost::serialization::make_nvp( cStripCountTag, nStripCount); const char * cIsLEDLampTag = "LEDLamp"; myArchive & boost::serialization::make_nvp( cIsLEDLampTag, blnIsLEDLamp); const char * cTranslationTag = "TranslationID"; myArchive & boost::serialization::make_nvp( cTranslationTag, strTranslationID); const char * cCursorOffsetTag = "CursorOffset"; myArchive & boost::serialization::make_nvp( cCursorOffsetTag, nCursorOffset); if(version > 0) { const char * cCursorFromLeftTag = "CursorFromLeft"; myArchive & boost::serialization::make_nvp( cCursorFromLeftTag, blnCursorFromLeft); } if(version > 1) { const char * cUniCodeTag = "Unicode"; myArchive & boost::serialization::make_nvp( cUniCodeTag, blnIsUniCode); } if(version > 2) { const char * cLinkedHashTag = "LinkedTo"; myArchive & boost::serialization::make_nvp( cLinkedHashTag, strLinkedDisplayHash); } } // end try catch (...) { throw ID_LOAD_DATA_EXCEPTION; } // end catch } ... }; // end of class definition BOOST_CLASS_VERSION(DisplayDefinition, 3); I'm clueless as to why the BOOST_CLASS_VERSION macro doesn't seem to be setting the version number correctly. Can anybody advise me, please? Best wishes. Tim Burgess Raised Bar Ltd. E: <mailto:tim@raisedbar.net> tim(a)raisedbar.net M: +44 (0)7989 486976

2 3