October 2016 - Boost - lists.preview.boost.org

[preprocessor] PR decision for Intel C++ 17 on up on Windows
by Edward Diener 27 Oct '16

27 Oct '16

I need some guidance from Boost developers in general. A PR has been issued for Boost PP which only affects Intel C++ 17 on up in Windows. I can ascertain that only this compiler in Windows is affectd by the PR. Needless to say I do not test this personally because it costs a decent amount of money to buy a license. Intel does graciously offer free licenses for Intel C++ on Linux for Boost developers and I have used it to test the compiler under Linux. Also there are no regression tests for Intel C++ on Windows in the 'develop' or 'master' regression test matrices. While the person who issued the PR ascertains that it fixes problems for Boost libraries he uses with Intel C++ 17 on Windows the nature of the PR is drastic enough that it could easily break other libraries if the changes in the PR does not correspond to Intel C++ preprocessing in all cases. So my quandary is what to do about the PR. The PR is at https://github.com/boostorg/preprocessor/pull/9#issuecomment-256741882. It is another one of these cases, like clang targeting VC++, where a compiler implementation on Windows wants to emulate the non-standard VC++ preprocessor but can't quite get it right ( as if emulating a broken preprocessor should ever be right ). Thoughts ? Ideas ? Suggestions ?

3 4

Boost odeint 1.62 link broken
by Daniel Duffy 27 Oct '16

27 Oct '16

________________________________________ From: Boost [boost-bounces(a)lists.boost.org] on behalf of Karsten Ahnert [karsten.ahnert(a)googlemail.com] Sent: 16 May 2016 15:08 To: boost(a)lists.boost.org Subject: Re: [boost] Boost 1.61.0 has been released > The Asio link http://www.boost.org/doc/libs/1_61_0/libs/asio/ is broken > (on http://www.boost.org/doc/libs/1_61_0/) I get ERR_TOO_MANY_REDIRECTS > with Chrome. The odeint link is also broken. I get "404 Not Found File "/home/www/live.boost.org/common/code/../../doc/archives/boost_1_61_0/libs/numeric/odeint/doc/html/index.html" not found. Unable to find file." Karsten _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

2 1

[boost.process] Review
by Klemens Morgenstern 27 Oct '16

27 Oct '16

Boost.Process 0.6, as can be found here (https://github.com/klemens-morgenstern/boost-process) will be in review from October 27 to November 5. The review manager will be Antony Polukhin. Doc (http://klemens-morgenstern.github.io/process/) I really hope this library gets through the review, since boost (or C++ for that matter) really needs a process library. I would be really happy, if some of you could take the time to look into it - if you find any major issues, they might be addressed, before the actualy review. That would then increase the probability of the library getting accepted.

5 13

[release] 1.63.0 now closed for new libraries and breaking changes
by Daniel James 27 Oct '16

27 Oct '16

Hello all, The master branch is now closed for new libraries and breaking changes, and will be closing for major changes in a week (2nd Nov) and closed for the beta in two weeks (9th Nov). Also, if you're ready, you can also add your libraries' changes to the release notes at: https://github.com/boostorg/website/blob/master/feed/history/boost_1_63_0.q… thanks, Daniel

2 3

[fixed_point] First presentation from GSoC 2015 and more
by Christopher Kormanyos 25 Oct '16

25 Oct '16

Hello Boost developers, A partial implementation of fixed-point in a Boost-like style based on proposal N3352 is now available.This work is the result of developments from 2013-2016, including efforts from GSoC 2015. The source code is available at: fixed_point-masterPreliminary docs are available at: fixed_point-docWe are potentially interested in submitting this work for inclusion in Boost. We are now requesting comments and suggestions for improvements, corrections and any further test results if these become available.Some key library features include:* proper C++ header-only implementation * full numeric_limits and <cmath> functions * flexible template choice of split between resolution and range * automatic selection of underlying integral representation * portability and high efficiency for bare metal microcontrollers * interoperation with Boost.Math * seamless extension to high-precision using Boost.Multiprecision * extensive test suite Thank you for your consideration. Best regards,Christopher Kormanyos

7 22

[serialization] 2 blocking bugs
by alainm 25 Oct '16

25 Oct '16

Hi, My Boost.MPI builds are currently failing because of two blocking bugs in serialization (merge request 47 and 46). Could someone have a look please ? Thanks Alain

1 0

boost @ Meeting C++ 2016
by Jens Weller 24 Oct '16

24 Oct '16

Hello boost community, a short and final reminder, that the Meeting C++ conference is just a few weeks away! A few tickets are still available, here is the schedule: https://meetingcpp.com/index.php/schedule16.html The schedule also has the link to the student program and diversity tickets! Also there is still a few places available in the boost workshop with Boris Schäling and Michael Caisse. I plan to have a meetup for boost users in one of the breaks in the upper lounge, so that the boost communtiy is able to actually meet at Meeting C++! thanks, Jens Weller

1 0

Interest in chained relational operations
by Rahman Salim Zengin 24 Oct '16

24 Oct '16

Hi, The code in question is a simple chained comparison implementation. It works with any type If relational operators for that type is defined. https://github.com/rszengin/chain May some people find it useful?

4 4

predef: BOOST_COMP_MSVC defined for Gcc/Linux?
by Oliver Kowalke 24 Oct '16

24 Oct '16

Hi, test '#if defined(BOOST_COMP_MSVC)' evaluates to true with GCC on Linux. what I'm missing? Oliver

2 2

[interprocess] interprocess_condition blocks on notify_all if other process crashes
by Remi Chateauneu 22 Oct '16

22 Oct '16

When two processes share memory, and if one of them dies leaving a mutex in locked state, then the other process blocks on a notify using a interprocess_condition, stored in shared memory. This is described here: http://stackoverflow.com/questions/18240263/boost-interprocess-condition-bl… The reason is that this condition uses in general, a ipcdetail::spin_condition. Here is what it does in boost/interprocess/sync/interprocess_condition.hpp and boost/interprocess/sync/spin/condition.hpp : inline void spin_condition::notify(boost::uint32_t command) { //This mutex guarantees that no other thread can enter to the //do_timed_wait method logic, so that thread count will be //constant until the function writes a NOTIFY_ALL command. //It also guarantees that no other notification can be signaled //on this spin_condition before this one ends m_enter_mut.lock(); It locks an internal mutex, and if it is already locked and not unlocked by the crashed process, we are blocked. A fix is to replace lock() by: if( ! m_enter_mut.timed_lock(delay) ) throw an_exception(); A cleaner fix would be to derive a subclass from spin_condition to implement something like: bool derived_spin_condition::timed_notify(boost::uint32_t, ptime delay) What do you think ? Thanks.

2 1