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

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