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

Query: ADL vs MSVC2013 support
by Soul Studios 28 Jun '16

28 Jun '16

I have transplanted the advance/next/prev/distance member functions into ADL non-member functions in a current unreleased version of colony (plflib.org) My question is whether MSVC2013 support for these functions is more important to the boost community than them being ADL. There's a bug in MSVC2013 (fixed in MSVC2015, never backported to MSVC2013) that causes a compiler crash under certain template configurations - unfortunately the way that the ADL has to be implemented (I have tried several methods) causes this bug. The workaround would be to disable these functions in MSVC2013 only, as everything works fine in MSVC2010, MSVC2015, Clang 3.6-3.8 (have not tested earlier) and GCC 4.6-5.1 (have not tested earlier).

1 1

message: Build #2 is still failing.
by Robert Ramey 26 Jun '16

26 Jun '16

I'm getting these messages on aregular basis. They point to the url https://travis-ci.org/boostorg/serialization/builds/140270355 I can see the utility of this. It seems that this is due to some requirement that I'm not fulfillng in the serialization library test directory.... or something. What, if anything, should I do about this. Robert Ramey

2 1

enabling constexpr with Visual studio 2015 Update 3 (RC)
by Paul A. Bristow 24 Jun '16

24 Jun '16

I am trying to use the enhanced constexpr features and have (perhaps unwisely) downloaded the latest Visual Studio Update 3 (RC) to get as great a chance of achieving this as possible. https://blogs.msdn.microsoft.com/vcblog/2015/12/02/constexpr-in-vs2015-upda… (and later posts) I am unsure what I need to do to ensure that the compiler is enabled for use the latest features. I have added /std:c++14 to the options of the property for the project. (aside I also tried /std:C++latest but that works for some tasks but failed to compile with odd-looking errors in converter.hpp Error C2518 keyword 'typename' illegal in base class list; ignored \modular-boost\boost\numeric\conversion\detail\converter.hpp 453 // Trivial Converter : used when (cv-unqualified) T == (cv-unqualified) S // template<class Traits> struct trivial_converter_impl : public std::unary_function< BOOST_DEDUCED_TYPENAME Traits::argument_type ,BOOST_DEDUCED_TYPENAME Traits::result_type > ,public dummy_range_checker<Traits> {...} So I stopped trying that /std:c++latest option. What else should it do?) Running the modular-boost/libs/config/config_info.cpp program BOOST_NO_CXX14_CONSTEXPR [no value] BOOST_CONSTEXPR [no value] BOOST_CONSTEXPR_OR_CONST =const BOOST_STATIC_CONSTEXPR =static const These don't seem to be what I think that I would expect (constexpr and static constexpr). I want especially to use BOOST_STATIC_CONSTEXPR to get static constexpr. Do I need to also add #define BOOST_CXX14_CONSTEXPR in my program or elsewhere? (Doing this doesn't change BOOST_CONSTEXPR_OR_CONST from const to constexpr) Thanks for any suggestions. Paul --- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830

8 16

[typeof] Pull requests
by Adam Wulkiewicz 23 Jun '16

23 Jun '16

Hi, There are trivial pull requests in TypeOf waiting for merging (https://github.com/boostorg/typeof/pulls) One of them is more than 2 yo. Would it be possible to merge them? At least #3 or #4 should be merged. Regards, Adam

1 0

Additional Test Configurations
by Tom Kent 22 Jun '16

22 Jun '16

About a month ago I got three new machines dedicated to testing boost online (thanks to Boost Community/Steering Committee/Conservancy!). These three machines are currently running tests along with a couple other machines that I have. Now that things are up and running, I'm looking for some community input as to how best utilize them. Here's the current setup: teeks99-01 - Ubuntu 14.04 + Docker - gcc-4.4 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.5 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.6 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.7 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.8 (master + develop) Docker trusty + ubuntu-toolchain-r/test - gcc-4.9 (master + develop) Docker trusty + ubuntu-toolchain-r/test - gcc-5 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.0 (master + develop) Docker trusty + h-rayflood/llvm - clang-3.1 (master + develop) Docker trusty + h-rayflood/llvm - clang-3.2 (master + develop) Docker trusty + h-rayflood/llvm - clang-3.3 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.4 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.5 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.6 (master + develop) Docker trusty - clang-3.7 (master + develop) Docker trusty + llvm.org/apt teeks99-02 - Ubuntu 16.04 + Docker - gcc-4.4 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.5 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.6 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.7 (master + develop) Docker precise + ubuntu-toolchain-r/test - gcc-4.8 (master + develop) Docker trusty + ubuntu-toolchain-r/test - gcc-4.9 (master + develop) Docker trusty + ubuntu-toolchain-r/test - gcc-5 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.0 (master + develop) Docker trusty + h-rayflood/llvm - clang-3.1 (master + develop) Docker trusty + h-rayflood/llvm - clang-3.2 (master + develop) Docker trusty + h-rayflood/llvm - clang-3.3 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.4 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.5 (master + develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.6 (master + develop) Docker trusty - clang-3.7 (master + develop) Docker trusty + llvm.org/apt teeks99-03 - Ubuntu 16.04 + Docker - gcc-5 (develop) Docker trusty + ubuntu-toolchain-r/test - clang-3.7 (develop) Docker trusty + llvm.org/apt teeks99-05 - Ubuntu 14.04 (Azure VM) - gcc-4.8 (master) - clang-3.4 (master) teeks99-08 - Windows 2012 (KVM VM) - msvc-8.0 (master + develop) SP1 - msvc-9.0 (master + develop) SP1 - msvc-10.0 (master + develop) SP1 - msvc-11.0 (master + develop) Update 4 - msvc-12.0 (master + develop) Update 5 - msvc-14.0 (master + develop) Update 2 teeks99-09 - Windows 2012 (KVM VM) - msvc-8.0 (master + develop) SP1 - msvc-9.0 (master + develop) SP1 - msvc-10.0 (master + develop) SP1 - msvc-11.0 (master + develop) Update 4 - msvc-12.0 (master + develop) Update 5 - msvc-14.0 (master + develop) Update 2 I'm currently working on getting gcc-6 and clang 3.8, sorry they aren't in the list yet. I'm planning to retire the teeks99-01 shortly and converting the ancient teeks99-05 to something newer, still doing boost testing. All these configurations and the scripts that keep them cycling are on github at: https://github.com/teeks99/boost-build For each platform there are a couple configurations that I try to run frequently to give 'rapid' results as developers are committing code. The configurations for windows are set so that every few runs it will run the msvc-12.0 (develop) test, so that is never more than ~10hrs old. Similarly on linux, the gcc-5 and clang-3.7 (develp) tests get run every few hours. Just to give a feeling of the timing, Linux runs take .75-3 hrs and Windows runs take 1.5-4hrs, depending on compiler, os, hardware, etc. All these configurations have minimal compiler options set. MSVC + GCC builds have no options set, clang has `<cxxflags>-Wno-c99-extensions`. >From a lot of the discussing I've seen on the lists, it seems that there's a lot of work going into C++ 11/14/1z development. I was thinking it would be good to add some of those switches. Which ones? How many? Baseline Standard -std=c++98 (I believe this is the default for all the g++/clang++ instances above) -std=c++11/0x -std=c++14/1y -std=c++1z GNU Standard -std=gnu++98 -std=gnu++11/0x -std=gnu++14/1y -std=gnu++1z Clang Library -stdlib=libc++ -stdlib=libstdc++ Optimization -O2? Warnings -Wall -Wextra Others? I'm guessing that most of these will be of interest to at least a small subset of developers. There probably isn't a need to apply all possible combinations to all possible compilers however. (Not to mention that it would make the results matrix even more overwhelming.) Which combinations are important for you to see in the matrix? What do you think should be the 'rapid' configurations? I'm also thinking about additional compilers (in addition to gcc-6/clang-3.9 mentioned above), though these will take a bit of work on my part, so will only get implemented as I have time available. - gcc HEAD from GIT - clang HEAD from GIT - cygwin/gcc - mingw - clang on windows - Other? Thanks in advance for your input! Tom

6 12

[boost.process] 0.6 Alpha
by Klemens Morgenstern 21 Jun '16

21 Jun '16

Hi all, the boost.process 0.6 library is now in alpha, that is: it has some (compiling) examples, a documentation and tests that pass on windows as well as on linux. It basically allows you to manage a process like this: pstream pipe; child c("some_prog", "--some-arg", env["PATH"]+="C:/stuff", std_in < "data.csv", std_out > pipe, std_err > null, start_dir="./bin"); std::string data; pipe >> data; c.wait(); cout << c.exit_code() << endl; You can find the documentation here: http://klemens-morgenstern.github.io/process/ Get the source code from here: https://github.com/klemens-morgenstern/boost-process If you want to use it on windows, you currently would need to clone my boost.winapi fork also: https://github.com/klemens-morgenstern/winapi As for the scope of the library, it is meant to implement a small, portable layer to allow platform-independent process management. Thereby it's functionality is (unless I missed something) basically what is possible on posix as well as on windows. There are some platform extension, but I would not recommend to use them. It is also possible (though not yet documented) to write extensions, and if they work on both platforms I will gladly add them. It is however not the goal of the library, to be the be-all and end-all of process management; in past disscussions, different ideas where brought up, like implementing a DSEL for that or only allowing asynchronous communication. This library will never be that, since it would be much more fitting to build this on-top of it. E.g. a DSEL could be written (e.g. boost.shell) using boost.process underneath, so the library could concentrate only on the DSEL. It doesn't depend on boost.iostreams anymore, though it still uses boost.asio, boost.fusion and boost.filesystem. As for the open issues: some error handling is still lacking (but that'd be something like being unable to duplicate a handle), which would be required for proper extension, which is also why it's not documented. Also there's still an open discussion about the naming of the class and functions (child, system, spawn), so that may change also. But I consider this simple enough for a easy refactoring. If anyone has naming ideas, please tell me. One Idea was 'subprocess' but 'process::subprocess' just looks too strange to me. I hope you try it out, and give me some feedbacks. Or write angry error reports, both helps. Thanks! Klemens

8 32

Checking interest in stacktrace library
by Antony Polukhin 21 Jun '16

21 Jun '16

Hi, I've got some prototype for getting stack traces: https://github.com/apolukhin/stacktrace It's design is based on the idea that class for stacktrace must be fully noexcept, without dynamic allocations in constructors and as simple as possible. Is there interest in it? What functionality would you like to have in it? -- Best regards, Antony Polukhin

9 10

Re: [boost] proposed new library "histogram"
by Bjorn Reese 20 Jun '16

20 Jun '16

On 05/05/2016 12:21 AM, Hans Dembinski wrote: > https://github.com/HDembinski/histogram I suggest that you use non-intrusive serialization and place that in separate headers, so there is no dependency on Boost.Serialization unless you need it.

2 4

Checking interest in clang-{format, tidy} configurations
by jerry.c.t＠web.de 19 Jun '16

19 Jun '16

Hi, is there an interest for common boost clang-format and clang-tidy (only the module readability-identifier-naming) configurations to inforce consistent layout and naming style? For clang-format there are predefined styles like llvm, google etc. I think about adding a new predefined style 'boost' to clang-format. But first i would start with a separate _clang-format file. For clang-tidy there are no predefined styles thus i would simply create a _clang-tidy file. Best regards, Jerry

2 1

Feature request: variant::view
by TONGARI J 19 Jun '16

19 Jun '16

Hi, Sometimes we need to view a value as a variant and we don't want to copy the value into a variant. It'd be great if there's a variant::view that works like a variant but holds a reference to the value instead. The constructor should allow any reference to the types as in the variant, and a constructor that takes a reference to the variant, e.g. template<class T1, class T2...> class variant<T1, T2...>::view { view(T1&); view(T2&); ... view(variant&); }; And we can use apply_visitor/get on a view as on a variant. Thoughts? Thanks.

2 2