- Boost - lists.preview.boost.org

Property Tree Maintainer
by Gary Furnish 21 Aug '17

21 Aug '17

I've emailed Sebastian Redl <sebastian.redl -at- getdesigned.at> and never got a responce, is property tree abandoned? There are a bunch of PRs (including mine at https://github.com/boostorg/property_tree/pull/29) piling up on github. I'm not exactly sure what the procedure is if it is, but maybe we could get some love for PRs from community maintainers or something? Thanks,

2 1

Boost 1.65.0 Release Candidate 5
by Daniel James 20 Aug '17

20 Aug '17

Hello everyone, The fifth release candidate for the 1.65.0 release is now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1s/RC2s/RC3s/RC4s are in that directory, too - make sure you get the right files! ] It can also be downloaded from the 'in progress' release notes on the website: http://www.boost.org/users/history/in_progress.html Changes since RC4: * Fully qualify the name of a trait to fix an error in recent versions of Visual Studio. Changes since RC3: * Fix a bug in Boost.Thread where timed waits were waiting for a very long time. Changes since RC2: * Fix a crashing bug in Boost.ASIO * Fix a compilation error when including both <boost/math_fwd.hpp> and <boost/math/common_factor_ct.hpp> * An update to Boost.Spirit to fix compilation errors on Mac OS with -std=c++17 Changes since RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 4873d8f3506fd8d76e2eadcf0ace83b258010fc268a4d974361af7abad5448f5 boost_1_65_0_rc5.7z ea26712742e2fb079c2a566a31f3266973b76e38222b9f88b387e3c8b2f9902c boost_1_65_0_rc5.tar.bz2 8a142d33ab4b4ed0de3abea3280ae3b2ce91c48c09478518c73e5dd2ba8f20aa boost_1_65_0_rc5.tar.gz f3f5c37be45eb6516c95cd147d8aa4abb9b52121fc3eccc1fc65c4af0cf48592 boost_1_65_0_rc5.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. Thanks! -- The release managers

3 3

Boost 1.65.0 Release Candidate 4
by Marshall Clow 19 Aug '17

19 Aug '17

The fourth (and hopefully final) release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1s/RC2s/RC3s are in that directory, too - make sure you get the right files! ] Changes since RC3: * Fix a bug in Boost.Thread where timed waits were waiting for a very long time. Changes since RC2: * Fix a crashing bug in Boost.ASIO * Fix a compilation error when including both <boost/math_fwd.hpp> and <boost/math/common_factor_ct.hpp> * An update to Boost.Spirit to fix compilation errors on Mac OS with -std=c++17 Changes since RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 5d255d1ff8460d52dffcf9a9b55d908ae704027a66c590ec774096effaea26c1 boost_1_65_0_rc4.7z 911602d830ea5d16483d1e565b9859d120d03f2e5176017226ef391eb9d17fc8 boost_1_65_0_rc4.tar.bz2 369e06dc787d32b0fbaae020f33d814c9e7b77263acb859776968e623035f760 boost_1_65_0_rc4.tar.gz a9c6b8346b05ea43ac4278e80036a9e956ea99fc61f0b7f55469471af2df934c boost_1_65_0_rc4.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. Thanks! -- The release managers

13 24

Improving Boost Docs
by Robert Ramey 17 Aug '17

17 Aug '17

I'm aware that at one point there was an initiative to improve boost documentation. See https://svn.boost.org/trac10/wiki/ImprovingBoostDocs It seems that the last movement here was 10 years ago. Does anyone know what the current status of this is? Does anyone still work on it? Does anyone know anything about it? I'm just curious about this. Robert Ramey

13 44

Need urgent help >> How to Handle Fragmentation in Boost's managed_shared_memory
by vijay sharma 17 Aug '17

17 Aug '17

I am using Boost::managed_shared_memory for my project. For allocate and deallocate we are using boost APIs as show in below example: shm_controller.reset(new boost::interprocess::managed_shared_memory( boost::interprocess::open_or_create, shmName, size));void * addr = shm_controller->allocate(size) ; shm_controller ->deallocate(addr); For this I have two question: 1) How can i handle fragmentation in this ? We are doing very frequent allocation and release. 2) What kind of allocation we are using in boost (slab, slub, slob) ? First question is very important for me. Please let me know if you want more info on any of these. Thanks, sharmavijay1991(a)gmail.com

3 2

Main page should link to some online compilers that include Boost
by Chambers, Matthew 17 Aug '17

17 Aug '17

Similar to https://isocpp.org/blog/2013/01/online-c-compilers but less of a blog post and more of an up-to-date list of online compilers where users can try out Boost immediately. Googling for this is tedious and it's certainly in Boost's best interest to encourage people to try it out (and make the barrier to do so as low as possible). -Matt

1 0

BOOST_STATIC_CONSTANT
by Vladimir Batov 17 Aug '17

17 Aug '17

There is something seemingly basic that puzzles me greatly. I am hoping people might clarify something I totally fail to understand. I've been using BOOST_STATIC_CONSTANT for ages (with GCC). Now I have something seemingly non-controversial: template<typename user_type> struct impl_ptr { using yes_type = boost::type_traits::yes_type; using no_type = boost::type_traits::no_type; using ptr_type = typename std::remove_const<user_type>::type*; template<typename Y> static yes_type test (Y*, typename Y::impl_ptr_type* =nullptr); static no_type test (...); BOOST_STATIC_CONSTANT(bool, value = (1 == sizeof(test(ptr_type(nullptr))))); }; When compiled with gcc-.5.4.0, both lines below pass: BOOST_TEST(true == boost::impl_ptr<Shared>::value); BOOST_TEST(true == boost::impl_ptr<Shared const>::value); The only difference between them is "const". However, when I compile with clang-4.0, the second (const) line passes. However, the first one fails! I refuse to believe it's a clang glitch. It must be me doing something really stupid. Help?!

6 14

VS2017 version 15.3
by Róbert Špir 17 Aug '17

17 Aug '17

Hi all, after upgrading my installation of vs2017 to version 15.3 (released two days ago) I'm receiving a lot of "Unknown compiler version - please run the configure tests and report the results" messages during building the project which uses boost (but everything builds and works fine). The cl.exe version in vs2017 15.3 was changed to 19.11.25506 Robert

5 7

patch for Intel compiler for new lib appeared in boost 1.65 beta
by Kurkov, Vasiliy A 17 Aug '17

17 Aug '17

Hi, I am Vasiliy Kurkov and I'm working as QA engineer in Intel Compiler QA team. I have tried to build boost libs from 1.65 beta, but I faced the following issue on Windows for new stacktrace lib: compile-c-c++ bin.v2\libs\stacktrace\build\07984f9e4da2f3b833f7520e2f16f320\windbg_cached.obj icl @"bin.v2\libs\stacktrace\build\07984f9e4da2f3b833f7520e2f16f320\windbg_cached.obj.rsp" windbg_cached.cpp .\boost/stacktrace/detail/collect_unwind.ipp(17): catastrophic error: cannot open source file "unwind.h" #include <unwind.h> ^ compilation aborted for libs\stacktrace\build\..\src\windbg_cached.cpp (code 4) Environment: Windows 2016 Server + MSVS2017 + Intel Compiler 17.0 or later I would like to suggested the following patch: --- 1/boost_1_65_0/boost/stacktrace/safe_dump_to.hpp 2017-08-16 13:37:10.003950000 +0300 +++ 2/boost_1_65_0/boost/stacktrace/safe_dump_to.hpp 2017-08-16 13:38:05.470305000 +0300 @@ -203,7 +203,7 @@ # else # include <boost/stacktrace/detail/safe_dump_posix.ipp> # endif -# if defined(BOOST_MSVC) +# if defined(BOOST_MSVC) || defined(BOOST_INTEL) # include <boost/stacktrace/detail/collect_msvc.ipp> # else # include <boost/stacktrace/detail/collect_unwind.ipp> Thank you in advance. -- Regards, Vasiliy -------------------------------------------------------------------- Intel Technology Poland sp. z o.o. ul. Slowackiego 173 | 80-298 Gdansk | Sad Rejonowy Gdansk Polnoc | VII Wydzial Gospodarczy Krajowego Rejestru Sadowego - KRS 101882 | NIP 957-07-52-316 | Kapital zakladowy 200.000 PLN. Ta wiadomosc wraz z zalacznikami jest przeznaczona dla okreslonego adresata i moze zawierac informacje poufne. W razie przypadkowego otrzymania tej wiadomosci, prosimy o powiadomienie nadawcy oraz trwale jej usuniecie; jakiekolwiek przegladanie lub rozpowszechnianie jest zabronione. This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). If you are not the intended recipient, please contact the sender and delete all copies; any review or distribution by others is strictly prohibited.

3 3

Boost 1.65.0 Release Candidate 3
by Marshall Clow 17 Aug '17

17 Aug '17

The third (and hopefully final) release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1s and RC2s are in that directory, too - make sure you get the right files! ] Changes since RC2: * Fix a crashing bug in Boost.ASIO * Fix a compilation error when including both <boost/math_fwd.hpp> <boost/math/common_factor_ct.hpp> * An update to Boost.Spirit to fix compilation errors on Mac OS with -std=c++17 Changes since RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 1d844a958656e76b140292ec1cbfe770d9916166c16e13b59d3dac1df3b7ef40 boost_1_65_0_rc3.7z 3fc2877cf5da4bbb0c91eab058d2e6764155e705e9c3e2dce2a0248936079675 boost_1_65_0_rc3.tar.bz2 e065b53d7f5326cc20d246b518facedb4407391aaf9fd4a1c90001e0c85accab boost_1_65_0_rc3.tar.gz 96b2ba69c6045060d1dfe012218457870200c2c22af60eb855bab5ffb75c13a2 boost_1_65_0_rc3.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. Thanks! -- The release managers

9 12

Where we are 1.65.0
by Marshall Clow 16 Aug '17

16 Aug '17

RC1 came out on Monday, and it had some problems. Specifically: * Some libraries didn't build with ToT clang/libc++ (Locale, Wave and Test) This is because in C++17, some deprecated library features have been removed. [bind1st, mem_fun, auto_ptr, random_shuffle, etc ] Boost.Config has support for these removals, but this was ... incomplete. [ This is on me; I did the partial job of adding these to Config's libc++ support a while back ] Normally, I would be tempted to say "Well, clang 5 is not shipping yet, and so we can put this off until 1.66.0". But both clang 5 and C++17 are imminent (they will both happen well before the 1.66 release, and so I think we should fix this now. Also, a future version of MSVC will have the same library issues. So I have committed a fix for Boost.Config that fixes the Boost.Test issues. Hartmut has fixed most of the Boost.Wave issues. Artymom has a fix for Boost.Locale. Windows/MSVC builds look good across the board. * Boost.Fiber fails to build on Mac OS with anything other than -std=c++03. There is a fix in develop for this; but there's still a bunch of tests failing. * There's a problem from the beta in Boost.Math. The regression regarding boost/math/common_factor_ct.hpp (vs > math_fwd.hpp) seems to be still there. (For details please see the > original mail and replies: > https://lists.boost.org/Archives/boost/2017/07/237452.php) > What I presume is the fix (https://github.com/boostorg/math/pull/75) was > merged into develop about 12 hours ago, some automatic CI tests still > running. * There's a problem with ScopeExit and Visual C++ 2017 With Visual C++ 2017 and /permissive-, ScopeExit is still broken, for which > there's an open PR: > https://github.com/boostorg/scope_exit/pull/3 > Looks good otherwise on MSVC 14.11, tested with /std=cpplatest and > _HAS_AUTO_PTR_ETC=1, targeting Windows 10 and XP, 32 bit and 64 bit, built > as static libraries. >

12 22

base64?
by Greger 16 Aug '17

16 Aug '17

Hi Is anyone interested in a base64 encode/decode library (for boost)? ty Greger

9 15

Re: [boost] : [math] Enable move semantics for polynomials
by Brian Wood 16 Aug '17

16 Aug '17

Lakshay Garg writes: >Hello all > >The polynomial class in boost.math does not support move sematics. I tried > to implement them and found that they immediately lead to significant >improvements in performance (benchmarking using google-benchmark). > > I would like to get the changes merged into the main repository. I > understand that boost accepts very high quality C++ code Hmm. Here's a benchmark where Boost doesn't do well: https://github.com/thekvs/cpp-serializers . Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

2 2

RC2 / VS2017 - shared libraries questions
by Raffi Enficiaud 15 Aug '17

15 Aug '17

Hi all, I am still trying RC2 (I think this is the same with RC3). I compile the RCs for VC 2017 (community 2017, v15.2) and the build generates shared libraries that link to the same VC runtime (as reported by dependency walker): Example: Boost atomic: direct link to c:\windows\system32\VCRUNTIME140.DLL for VC2017 and VC2015. Full logs of dependency walker attached. Here are the options I am passing to VC2015: toolset=msvc-14.0 --layout=versioned --build-type=complete --without-log -j 4 address-model=64 threading=multi runtime-link=shared and the options I am passing to VC2017: toolset=msvc-14.1 --layout=versioned --build-type=complete --without-log -j 4 address-model=64 threading=multi runtime-link=shared What am I doing wrong? Thanks, Raffi

4 4

[git] git config core.safecrlf setting for Windows?
by Beman Dawes 15 Aug '17

15 Aug '17

For Windows, github.com/boostorg/boost/wiki/Getting-Started suggests: git config --global core.autocrlf true But is silent about core.safecrlf. Should we be recommending a setting for core.safecrlf, and if so which one? Thanks, --Beman

3 3

[Root.Ptr] Update (C consultancy -> ISO)
by Phil Bouchard 14 Aug '17

14 Aug '17

Greetings, I just wanted to update everyone that I just made the Root.Ptr repository private: https://github.com/philippeb8/root_ptr This is because I am about to work as a consultant to fix memory leaks in C code and possibly C++98 code later on. When I am done testing Root.Ptr then I will submit it to ISO which is already pre-approved. Thank you, -Phil

7 11

Boost 1.65.0 Release Candidate 2
by Marshall Clow 14 Aug '17

14 Aug '17

The second release candidates for the 1.65.0 release are now available at: https://dl.bintray.com/boostorg/release/1.65.0/source/ [ Note: The RC1's are in that directory, too - make sure you get the right files! ] Changes from RC1: * An update to Boost.Config so that the flags BOOST_NO_CXX98_RANDOM_SHUFFLE and BOOST_NO_CXX98_BINDERS are now set appropriately for libc++. (This fixes the compilation errors for Boost.Test) * An update to Boost.Fiber to fix compilation errors * An update to Boost.Wave to fix compilation errors on Mac OS with -std=c++17 The SHA256 checksums are as follows: 786ccb478a82ef526fb8649841d2e863af90d7ea31217bb2e938d87aff06cf23 boost_1_65_0_rc2.7z 83dbc7179271825c55a59c26f30cf9de53bb8b42006d920948bad709f5372af9 boost_1_65_0_rc2.tar.bz2 493cbf33a8837b44f87e3ac8a37ec32b9a0a27b8cdb03eac6237a16027a03809 boost_1_65_0_rc2.tar.gz 40e4ccbd52322f9a8cb6e1829075c810d8aad8851f3efb2b3da7fcff6963e14d boost_1_65_0_rc2.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. Thanks! -- The release managers

6 7

[quickbook] Requiring C++11 features in quickbook
by Daniel James 14 Aug '17

14 Aug '17

Hi, I'm thinking of using some C++11 features in quickbook, will this cause anyone any issues? Based on the support tables, I'm thinking of supporting gcc 4.4, clang 3.4, Visual Studio 2013 and later compilers. I won't use anything that doesn't have wide support (such as expression SFINAE). Please let me know if this will be a problem for you. Daniel

5 8

Boost MSM Parent does not handle event
by Denis Kotov 14 Aug '17

14 Aug '17

Hello Henry, I have faced with interested behavior. When in child *FSM* I emit event it handles only by this *FSM (not proper behaviour)* But if I emit this event from the Parent *FSM* it tries to be handled by all sub-states and then by Parent *FSM (proper behavior from my point of view)* Is it possible to send event from Child State Machine to be handled first of all in all Child states and *FSM*-s and then in Parent *FSM* ? *Thanks,* *Best RegardsDenis Kotov*

1 0

[math] Enable move semantics for polynomials
by Lakshay Garg 14 Aug '17

14 Aug '17

Hello all The polynomial class in boost.math does not support move sematics. I tried to implement them and found that they immediately lead to significant improvements in performance (benchmarking using google-benchmark). I would like to get the changes merged into the main repository. I understand that boost accepts very high quality C++ code and since this will be my first time contributing to boost I am looking forward to assistance from other experienced contributors. Could someone please advise me on how to move forward and get the changes merged. Regards Lakshay

4 8

Posts not appearing on Boost Mailman
by Raffi Enficiaud 14 Aug '17

14 Aug '17

Hi Boost, I have an issue with MailMan: I never use "emails" for posting on the Boost ML, I use news.gmane.org through thunderbird. I can see my posts on news.gmane.org, but I cannot see any of my posts here for instance: https://lists.boost.org/Archives/boost/2017/07/index.php Is this normal? Thanks, Raffi

5 8

Hello World
by Naivedya Bansal 14 Aug '17

14 Aug '17

I am a new comer and would like to become a contributor at Boost. Could you please provide me with relevant links from where to start ad I am feeling entirely lost right now. Thank you, Naivedya Bansal

2 1

CUDA V9 (release candidate) breaks compilation
by Hartmut Kaiser 12 Aug '17

12 Aug '17

All, Apparently CUDA V9 has deprecated/removed the __CUDACC_VER__ macro which is used by Boost, see https://github.com/STEllAR-GROUP/hpx/issues/2815 for details. Should this be fixed before the release? Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu

1 0

Switch to CMake -- Analysis
by Thomas Heller 12 Aug '17

12 Aug '17

Hi list, After there has been a heated debated over the last three days over the switch to CMake, I'd like to share my observations... First of all, a general observation: In this discussion, there generally seems to two camps: Those who know Boost.Build and those who know CMake. Unfortunately, there doesn't seem to be any overlap between those groups, which generally made the discussions about a potential switch to CMake unfruitful, often leading to misunderstandings due to a lack of knowledge about the other tool. There is no doubt, that the group of people knowing CMake is larger and that projects using CMake far outnumber the ones using Boost.Build. A thousand flies can't be wrong, right? Is the popularity of CMake really the only benefit? Here is the thing, from my point of view: Apart from the different philosophy (Build System vs. Build System generator), in the end, you get a executable/library out of the system. From a pragmatic point of view, the only thing that changes to develop/build/test/use a library is the work flow. Leaving aside the disruptive and its effects of such. Now, on to the motivation for switching, as presented in the announcement: On 7/18/2017 9:12 AM, Jon Kalb via Boost wrote: > [...] our build system has become an impediment for many developers > and users, existing and prospective. Let's look at users first. Yes, FindBoost.cmake has its problems, but it works in 90% of the cases (from my own experience). This can, and should certainly be improved. Providing the necessary XXX-config.cmake files is what fixes this. There has been movement in that direction, with code, which could be just improved upon. This will fix those cases. The other group of library consumers, expressed the urge to build boost directly as part of their build process. That hasn't been done yet, but I am pretty certain, there are no road blocks to actually write such a CMake Module, which invokes b2 instead of the compiler directly inside of the superproject. Together with the generated XXX-config.cmake files, this use case is covered. From my recollection of the various discussions, this approach was not contentious at all, it wouldn't even require interaction with all library maintainers, and all CMake users (existing or prospective) would immediately benefit. Now on to developers. There is obviously a lot of resistance from existing developers (for various reasons, which are not really relevant for the discussion at hand). In my opinion, maintaining two build systems is a no-go. Either make a clear cut, or don't. Please don't waste resources on maintaining and supporting both. With this line of thought as the background, this will create massive disruption. Switching the whole of boost (including infrastructure, documentation etc.) to be built and tested with CMake is not easy and take a lot of time, leaving a void for both maintainers and prospective boost library authors. Now, the argument that has been brought up very often in favor for the switch is that it will attract more contributors, but will it really? I am reluctant to the idea that people don't contribute new libraries to boost just because of the build system. Despite a switch to cmake, you'd still have to conform to Boost.CMake guidelines and somehow make your library buildable and testable within and outside of the Boost Tree (there might be a straight forward solution to this). Furthermore, I often hear something like "in the presence of GitHub and CMake people don't think about submitting to boost anymore". This is exactly the point. But it has nothing to do with the "and CMake" suffix. It's is just far more easier and convenient to drop you library to GitHub, advertise it on various channels and call it a day. I hear you say: "Sure, but libraries will only be adopted if they come with CMake." That might very well be true, but what has this to do with Boost? Compare the lengthy and exhausting review process you have to go through with the click of a few buttons and hammering something onto a keyboard. And no, Robert, while the incubator was a nice idea, it doesn't compensate that either ;) All in all, I am pretty confident that a disruptive switch will hurt Boost more than it brings benefit. This already happened. To come to an end and summarize: Provide proper CMake integration, such that Boost is consumable by those (while you are at it, don't forget meson, bazel and pkg-config). While your add it, improve Boost.Build, maybe it can rise again from its ashes (why did it "fail" in the first place?). Regards, Thomas

27 78

Best Practices for Surviving the Boost Test Gauntlet?
by Vinnie Falco 11 Aug '17

11 Aug '17

Beast won the first battle, but it looks like it is losing the war: <http://www.boost.org/development/tests/develop/developer/beast.html> I've never heard of many of these platforms let alone know how to go about fixing the compile, link, and runtime errors. It seems like deallocate() is not part of some standard library's allocator_traits? Link error on operator delete from Boost.System? A lot of little thing. Is there a document or resource which explains the various peculiarities and idiosyncrasies of these platforms and toolchains that I might have a means of fixing them without actually installing them locally (which is unlikely)? Thanks

6 14