- Boost - lists.boost.org

[release] 1.63.0 closed for major changes
by Daniel James 02 Nov '16

02 Nov '16

Hi, The master branch is closed for major changes. In one week (9th Nov) it will be closing for the beta release. The full schedule is on the website: http://www.boost.org/development/ And if you haven't done so yet, please can you add your libraries' details to the release notes at: https://github.com/boostorg/website/blob/master/feed/history/boost_1_63_0.q… Or email them to me, if you don't like writing quickbook.

1 0

Curiousity question
by Edward Diener 01 Nov '16

01 Nov '16

I would like to ask a design question for any Boost developers or anyone on this mailing list who might care to answer. You are designing or working on a library, perhaps for Boost, perhaps for fun, and part of the design of the library has some public functionality taking a shared pointer as input. You: 1) Use boost::shared_ptr 2) Use std::shared_ptr 3) Use both boost::shared_ptr and std::shared_ptr with the same functionality 4) Use neither, you roll your own shared pointer-like functionality 5) You don't lke shared pointers and use raw pointers instead I really am curious about this. I haven't put any limitation on your library or made any presumption on who your library is for, on purpose. Thanks for anyone answering !

13 53

[process] Formal Review starts today, 27 October
by Remi Chateauneu 31 Oct '16

31 Oct '16

Hi All, "Whether you believe the library should be accepted into Boost" It could be, but as some very important features are missinge, the implementation should be prepared from now on. "Your knowledge of the problem domain" About 20 yrs C++ development Linux and Windows. This library has a strong focus on the streaming which is quite rare and interesting. However, other very important features of multi-processing are missing should be planned: At least to ensure that, in the future, they can be added without breaking existing code. Example of these desired fatures are (Taken from my own needs) * List of subprocesses of a given process. * Get its parent pid (Already discussed). * Get the entire process tree of a machine. * It is very useful to be notified when a given process dies (unotify on Linux). * On windows, we have the feature e.startup_info.dwFlags = STARTF_RUNFULLSCREEN, which gives some control on the console, which Is very good. Could we have more documentation about it, and plans to have the same feature on Linux ? Generally speaking have some control on the process terminal if there is one. * Have some knowledge about users and user groups, as strings and integer identifiers: the concept is similar on Windows and Unix. * Have some control on process priority( Unix's nice command ) Indeed, many of these features are not portable, but most of time, developers use only a common core of features, which is quite enough. Maybe take inspiration from portable libraries such as Python psutil, which exposes a common interface for all operating systems. Interoperability: * It might be worth checking portability with other operating systems. BSD ? VMS ??? * Must ensure that this lib is interoperable with boost::interprocess (Concept of permissions might be worth using ?) * Does it build on pre-C++11 compilers ? Many projects are not able to upgrade to C++11 immediately and have to stick to previous C++ standard. Some critics (Nothing is perfect): * The merit of the ">" operator for optional arguments is to be visually similar to an indirection, but in the context of C++ programming, although elegant, it is I think confusing and could be mismatched with <> templates or comparisons. Creating a process is a not-so-frequent operation and we should not be afraid to be verbose and very clear, I believe. * Syntax ‘(bp::std_out & bp::std_err) > "output.txt"’ . Can we explain the exact difference with the syntax: ‘bp::std_out > "output.txt", bp::std_err > "output.txt"’’ * More comments in the code and examples please. * Examples async_io.cpp or arg.cpp do not build with boost 1.62: include\boost\process\detail\windows\compare_handles.hpp(24): error C2039: 'BY_HANDLE_FILE_INFORMATION_': is not a member of 'boost::detail::winapi' * ‘typedef basic_environment<wchar_t> wenvironment;’ : Is It really useful ?? POSIX getenv() only uses char. * Why is the class basic_environment so big, as it is basically a simple std::map< std::string, std::string > ? (Naïve question). Anyway, many congratulations for this very interesting work, which is definitely on the right direction. Regards

2 1

[gil] Some documentation links broken
by Edward Diener 31 Oct '16

31 Oct '16

In the documentation for Gil the links to the video tutorial, as well as the Information links on the left hand side of the initial page, are broken. Does anybody know if these links still exist anywhere ?

1 0

libstdc++ debug mode
by Robert Ramey 31 Oct '16

31 Oct '16

Back on May 2 2016 I made what I thought was an innocuous change to the serialization library build. I then forgot about it. I ran my tests and normal on my OSX set up for the compilers that I use there - clang and g++ 5.1 in various modes 03, 11 etc. Things seemed fine. I uploaded the develop branch as normal. Sometime later I discovered that all the gcc tests on linux platforms were failing with a segfault. Unfortunately time had passed and I couldn't run the tests myself so I never could figure out what the breaking change was. Lately I separated time to get to the bottom of this and in installed via Parallels ubuntu v 14 on my Mac as a guest operating system. After the usual back and forth getting stuff to work I was able to reproduce the problem. Running gdb indicated that things crashed with a call to boost::io::state_saver which led me to investigate THAT library which as it turned out is also failing all it's tests on the plaform. So thought I - no problem - all I have to do is to complain to the author of that library. But this didnt' workout a) I posted message and no one responded. b) I checked trac items and there was what seemed a related item. But it seemed a little hard to understand/fix and in any case, no one addressing it. I looked into just fixing it myself, but it looked to entail delving into the bowels of libstd++. So this dissuaded me as I have my own bowels to delve into. c) So I commented out references to boost::io::state_saver an ran some tests - and damn still failed. d) So I rolled back my source to the master dated 24 April 2016 and incrementally updated and ran some tests until I found the culprit. Needless to say, this is quite a tedious procedure. The issue seems to be that I added the following to the jamfile: <toolset>gcc:<define>_STLP_DEBUG <toolset>gcc:<define>_GLIBCXX_DEBUG The second adds a lot of checking. commenting this permitted tests to pass. Lesson of all this is: a) I'm thinking we should run all tests on the deelop branch with _GLIBCXX_DEBUG defined. That is, our jam files should contain?: <toolset>gcc:<variant>debug><define>_GLIBCXX_DEBUG b) it looks like when an error in libstd++ is encounted - things just segfault. I couldn't find the corresponding source in libstd++. GDB just bailed when I made a call to state_saver. c) boost::io::state_saver should be maintained. d) It would be helpful to be able to roll back the test matrix to any previous git version. That is, the results would be put into a database or datacube and we could scroll back and forth to see track down problems in test results. Robert Ramey

3 3

Review Manager needed for stacktrace library
by Antony Polukhin 27 Oct '16

27 Oct '16

Hello, Stacktrace is a C++98 library for storing and printing backtraces. Supports major platforms, does demangling, has API for accessing individual frames, supports hashing and comparison operators. Library: https://github.com/apolukhin/stacktrace Docs: http://apolukhin.github.io/stacktrace/index.html Anyone wishing to become the Review Manager for the library? -- Best regards, Antony Polukhin

8 21

[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