- Boost-users - lists.boost.org

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

22 Aug '18

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

1 0

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

20 Aug '18

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

1 0

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

20 Aug '18

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

2 1

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

20 Aug '18

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

3 5

[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