April 2016 - Boost - lists.boost.org

Boost 1.61.0 Release Candidate 1
by Vladimir Prus 09 May '16

09 May '16

The release candidates for the 1.61.0 release are now available at: http://boost.cowic.de/rc/boost_1_61_0_rc1.zip http://boost.cowic.de/rc/boost_1_61_0_rc1.7z http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.bz2 http://boost.cowic.de/rc/boost_1_61_0_rc1.tar.gz The SHA256 checksums are as follows: dcd11a91a412b2e8a78678b38cb2a74857e61f9bfe2577de9fd70be770100d54 boost_1_61_0_rc1.7z 476937369c7a82103b734ccae85d35a523cdb7f8462c5f2fe1217ff0c8e2a7df boost_1_61_0_rc1.tar.bz2 e60dee39ebb29d24bf8a4ef9aec34dbb8c1b9b219d4737ea4b358f38b1aab2b7 boost_1_61_0_rc1.tar.gz e5f662f44a65c5c19450b8a1c07f75c7d5f16e58667871e856ba3984ec082006 boost_1_61_0_rc1.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. The signed list of checksums is also attached, signed with the following key: https://pgp.mit.edu/pks/lookup?op=get&search=0xDA472E8659753BA4 Key fingerprint C5F0 F367 AA66 616F B839 806E DA47 2E86 5975 3BA4 Thanks! -- The release managers

14 38

Regression testing Clang/LLVM with VC14.
by degski 07 May '16

07 May '16

I have started a new thread as the other one "Testing of clang emualting the VC++ preprocessor on Windows" has become rather long and interlaced with less relevant musings. Here I would like to concentrate on the subject in the title. Sergey suggested I'd run regression tests, in the "other thread". I was hesitant at first, mostly due to the luke warm reception. Thanks to Google's simple coding of their spam filter, I actually missed the post by Niall Douglas of 4th of April. When it was referenced later and after I dug it from the archives, I became encouraged by the fact that maybe I wasn't all wrong and somebody within the community was actually thinking along similar lines as me. Following this I'd decided to take on regression testing. I chose to first simply test boost-develop against VC14, just to see how it goes. Some good, some bad. Was easy to set up (git already included with VC14, all what I needed to do was install python, which I normally have, but I'm having a new laptop). The bad, space required 44GB (advertised as 5GB). Possibly .pdb files (debugger symbols) are filling up disk-space uselessly. Next bad, the process finished with the following lines: # Done writing "C:\boost_develop\results\degski.xml". # Compressing "C:\boost_develop\results\degski.xml"... # Done writing "C:\boost_develop\results\degski.zip". # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (5 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (4 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (3 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (2 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Retrying (1 more attempts). # Uploading log archive "C:\boost_develop\results\degski.zip" to develop # <lambda> failed with message "[Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions" # Giving up. Traceback (most recent call last): File "run.py", line 71, in <module> runner(root) File "C:\boost_develop\boost_regression_src\regression.py", line 287, in __init__ self.main() File "C:\boost_develop\boost_regression_src\regression.py", line 624, in main getattr(self,action_m)() File "C:\boost_develop\boost_regression_src\regression.py", line 591, in command_regression self.command_upload_logs() File "C:\boost_develop\boost_regression_src\regression.py", line 538, in command_upload_logs lambda: File "C:\boost_develop\boost_regression_src\regression.py", line 663, in retry return f() File "C:\boost_develop\boost_regression_src\regression.py", line 546, in <lambda> self.dart_server ) File "C:\boost_develop\boost_regression_src\collect_and_upload_logs.py", line 430, in upload_logs upload_to_ftp( tag, logs_archive, ftp_proxy, debug_level, ftp_url ) File "C:\boost_develop\boost_regression_src\collect_and_upload_logs.py", line 256, in upload_to_ftp ftp = ftplib.FTP( ftp_site ) File "C:\Python27\lib\ftplib.py", line 120, in __init__ self.connect(host) File "C:\Python27\lib\ftplib.py", line 135, in connect self.sock = socket.create_connection((self.host, self.port), self.timeout) File "C:\Python27\lib\socket.py", line 575, in create_connection raise err socket.error: [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions I've re-checked this page <http://www.boost.org/development/running_regression_tests.html>again, there's no mention of "registering" or something similar. Some tests must have failed, got prompted for starting the debugger twice (is the latter normal). This was a test-run (testing the testing), with VC14U2. Assuming the above can get sorted, I would in reality like to test Clang/LLVM (with VC14U2). I would like to ask (Niall Douglas in particular, I guess) what the suggested parameters to run.py should be for this combo. Should I target clang.exe or clang-cl.exe, develop or master. What about Clang/C2? How to reduce disk-space usage? degski

5 7

boost chrono bad_cast (gcc > 4.9 on Mac)
by Min Yang Jung 01 May '16

01 May '16

Hi All, I was wondering if Boost.Chrono works with gcc > 4.9 on Mac. When system_clock::now() is called, it throws an std::bad_cast exception. The binary from the same code doesn’t have the issue if compiled with clang on Mac and gcc > 4.9 on Linux. The gcc compilers that I use are macport-installed gcc 4.9 and 5.0 (g++-mp-4.9 and g++-mp-5.0) on Mac. Any help would be appreciated. Thanks. Regards, Min Yang Jung

3 2

Designing a multi-threaded file parser
by Aaron Boxer 30 Apr '16

30 Apr '16

Hello, I hope this is not off-topic, but I am interested in hearing about boost classes that will help me design the following: 1) I am designing a multi-threaded file parser for C++11 threads. The file format I am interested in parsing is a tagged format, with some tags requiring further processing, and others not. My working model right now is to have one thread through the file, and if it hits a tag that requires further processing, to push the file offset of this tag into a queue, to be processed by a thread pool. The read thread will spend a lot of time waiting for file IO to complete. Would it be faster to us the ASIO classes to do the reading? 2) I would like to design the following thread scheduling library to help process the tags: The library would have the following features: 1. smallest unit of work for a thread is a job 2. jobs have dependencies - job FOO cannot complete until job BAR has completed 3. threads are divided into groups 4. groups can be divided into bundles (a bundle can share the same processor affinity, for example) 5. groups are assigned to domains - domains contain jobs with similar characteristics, for example slow I/O activity 6. domains contain queues of jobs 7. threads in a group assigned to a domain can execute any jobs in any of the domain's queues Does boost support this type of thread scheduling framework? Can boost help me manage dependencies between jobs? Sorry for these broad design questions - just hoping for some insight into best design here. Many Thanks, Aaron

2 5

[RFC] CallableTraits: 47 traits and metafunctions for "callable" types
by Barrett Adair 29 Apr '16

29 Apr '16

Hello all, I'm working on a project called CallableTraits [1]. Is there any interest in adding this to Boost? I think it would work well as an extension to Boost.TypeTraits. >From the introduction section: CallableTraits is a C++11/14/17 header-only library for the inspection, synthesis, and decomposition of callable types. Whether it's calling conventions, const volatile &&, or container-like manipulation of parameter lists, CallableTraits provides all the tools you need to completely rid your codebase of function type specializations. This project aims to be the "complete type manipulation facility for function types" mentioned in the last section of C++17 proposal p0172 [2]. CallableTraits currently supports GCC 4.8 and later, Clang 3.5 and later, AppleClang from XCode 6.3 and later, and MSVC 19. Much of the remaining documentation work lies in the reference sections. Many examples are provided, but many more are planned. Test coverage is good, but insufficient. Daily improvements are being made to address these issues. The headers amount to approximately 4200 lines of code, while the tests and examples tally around 6000 lines (excluding comments and blank lines). An "issues" list is maintained on GitHub [3]. Barrett [1]: http://badair.github.io/callable_traits/doc/html/index.html [2]: http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2015/p0172r0.html [3]: https://github.com/badair/callable_traits/issues

2 2

Re: [boost] New Lib "Beast", HTTP + WebSocket protocols
by Vinnie Falco 29 Apr '16

29 Apr '16

On Fri, Apr 22, 2016 at 8:13 PM, David Stone <david(a)doublewise.net> wrote: > How does this compare to www.zaphoyd.com/websocketpp We have experience with websocketpp as it is the solution we have been using in our open source peer to peer software (http://github.com/ripple/rippled) for the last five years. It is that experience that drove the development of this new library as its replacement. Since the WebSocket protocol starts with a HTTP handshake, we also developed Beast.HTTP as an added bonus - think of it as a double feature at the drive-in. Beast.WebSocket has these things going for it: * Construct a stream from a socket or ssl::stream that's already connected or accepted: boost::asio::ip::tcp::socket sock(ios); websocket::stream<boost::asio::ip::tcp::socket> ws(std::move(sock)); * Accept a WebSocket handshake request with bytes that have already been read from the socket: template<class ConstBufferSequence> void websocket::stream::accept(ConstBufferSequence const& buffers); * Accept a WebSocket HTTP request handshake that was already parsed (e.g. from Beast.HTTP): template<class Body, class Headers> void websocket::stream::accept(http::request<Body, Headers> const& request); * Wraps any object meeting these type requirements, use your own type if you want: websocket::stream<YourTypeHere> ws(...); The type requirements (sync, async, or both): http://www.boost.org/doc/libs/1_60_0/doc/html/boost_asio/reference/SyncRead… http://www.boost.org/doc/libs/1_60_0/doc/html/boost_asio/reference/SyncWrit… http://www.boost.org/doc/libs/1_60_0/doc/html/boost_asio/reference/AsyncRea… http://www.boost.org/doc/libs/1_60_0/doc/html/boost_asio/reference/AsyncWri… * Receive functions accept any object meeting the requirements of Streambuf, permitting custom memory management strategies including the use of statically sized buffers. For example games using messages of fixed length. Streambuf type requirements: http://vinniefalco.github.io/beast/beast/types/Streambuf.html * In the Asio doc, Christopher Kohlhoff alludes to alternate implementation strategies for boost::asio::streambuf using multiple discontiguous buffers of varying sizes. We fulfill this idea with an optimized stream buffer that follows the strategy he described, providing a useful building block for sending and receiving variable size data. See: https://github.com/vinniefalco/Beast/blob/master/include/beast/basic_stream… * Interfaces are designed to closely resemble Asio in every possible way. This includes support for the extensible asynchronous model - support for std::future and stackful/stackless coroutines right out of the box. The library is designed to eliminate the learning curve for those familiar with Asio: extern void handle_read(boost::system::error_code ec); websocket::stream<boost::asio::ip::tcp::socket> ws(ios); ... websocket::opcode op; beast::streambuf sb; ws.async_read(op, sb, std::bind(&handle_read, std::placeholders::_1)); * All functions are template driven so everything is transparent to the compiler, including completion handlers passed to asynchronous initiation functions and objects used as buffers. By design, Beast.WebSocket avoids doing these things: * Managing the io_service * Managing a listening socket * Managing threads or a thread pool * Requiring the use of exceptions in certain places * Imposing a particular message buffering strategy * Using std::function for asynchronous callbacks * Requiring callers to know the size of the message in advance. The last point above is especially important for applications that produce data incrementally. For example, a huge JSON reply that comes from a database query. Planned improvements for Beast.WebSocket include: * Explicit proxy support with basic authentication * Tools for parsing subprotocols and message headers * permessage compression: https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-28 Years of experience working with Asio and and WebSockets have gone into the development of this library. It tries to be a natural extension of Asio, in a manner that is as narrow and lean as possible to provide maximum flexibility and performance.

2 3

New Lib "Beast", HTTP + WebSocket protocols
by Vinnie Falco 28 Apr '16

28 Apr '16

"Beast" This is a new library that implements the HTTP and WebSocket protocols using Boost.Asio and a few other Boost tidbits. Here's a quick synopsis of what's in it: http::message: - class template modeling the HTTP message with customization points to satisfy even the most tough-minded reviewer. http::read http::write http::async_read http::async_write - Free functions to easily send and receive HTTP messages. Modeled to work exactly like boost::asio free functions. Role-agnostic, build clients or servers! websocket::stream - class template wrapping any asio sync or async stream. Implements the WebSocket protocol including the initial handshake. Examples: - websocket echo servers - HTTP servers for simple websites (no cgi) "I've heard enough, show me example code!" http://vinniefalco.github.io/beast/beast/intro/example.html Main page, with links to GitHub repository, HTML documentation and benchmarks: http://vinniefalco.github.io/ Feedback welcome, the author checks email and Issues on the GitHub repository. This project has been submitted to the Boost incubator.

2 2

CMake - one more time
by Robert Ramey 28 Apr '16

28 Apr '16

Inspired by the recent discussion regarding CMake, I've spend some more time looking at this. As a result, I've done the following. a) I experimented with using CMake in the more customary manner in my canonical project Safe Numerics - (see Boost Library Incubator). The current version does distribute CMakeLists.txt around the subdirectories of the library root. My original objections to doing this were assuaged when I realized that boost build does the same thing. That is I typically have Jamfiles in side of test, example and sometimes other directories. b) One of the features that I much like about Boost Build is the possibility of arbitrary nesting of Jamfiles. This permits one to build/test a portion of one's library (e.g. test, example) as well as the whole library. For a large library this is indispensable. In spite of what many people think, this is not easily supported with CMake. However, I have found that with some extra effort, it is possible to support this to the extent we need it. So in this project ONE CAN BUILD (actually create an IDE project or makefile that builds) ANY OF THE "SUBPROJECTS" (TEST, EXAMPLE) AS WELL AS THE LIBRARY "SUPERPROJECT" c) CMake is indispensable to me: * it creates IDE projects for "any?" platform. I use IDE alot. * everyone else uses it - so it makes it easier to promote my work to others. * it's easier to make work - still a pain though * There is lots of information, around the net about how to use CMake, how easy it is etc. Although they help when you're looking for an answer (which is all the time) - they really betray how complex, arbitrary and complex the system is. * It has an almost of idiot proof GUI version which I use a lot. I really like this. * CMake is well maintained and supported by it's promoters. d) Boost Build * either just works (great!) or doesn't. If it doesn't it's almost impossible fix without getting help * I've never run across anyone outside of boost who uses it. It makes it harder to promote my work. * It's natural to compose projects into "super projects" * it's almost impossible to integrate with and IDE. At one time, I had things setup so I could debug executables created with boost build with the Visual Studio IDE and debugger. But it was just too fragile and time consuming to keep everything in sync. * it has a lot of "automatic" behavior which can be really, really confusion. A small example: you've got multiple compilers on your system. When it discovers this, it just picks the "best" one and you don't know which one you got until the project builds (or not). I'm sure this was implemented this way to make usage of boost build "simple" but it has the opposite effect. Much better would be fail immediately with a message "multiple compilers found:... use toolset=<compiler name> to select desired one." Some Conclusions - I'm trying to not make this a rant a) The ideal, platform independent build system does not yet exist. I guessing it never will. I'm sure it won't happen in my life time - but then I'm 68 - maybe you'll get lucky. b) Both systems are much more fragile, complicated and opaque than their promoters try to make you believe. It's not that they're lying, they truely believe in their own stuff. There is much re-invention of the wheel - The each created their own (half-assed) little language for goodness sake!!! c) Neither has really resolved the issue of nested projects in a clear way. Boost Build probably does or can do this. CMake has a system of "packages" and a whole 'nuther layer about "finding" them. Assuming it can be made to work - given the amount of time I've invested in CMake, I should know how to do this by now. d) I think it's time for Boost to be a little more open about tolerating/encouraging alternative build systems. I think our documentation approach is a model. Yeah it's a hodgepodge. But the various ways of doing pretty much work and generally don't stop working and we don't have to constantly spend effort bringing things up to the latest greatest system (which we couldn't agree upon anyway). We have libraries which have been going strong 15 years - and people can still read the docs. e) We should find some way to recognize those who have made the system work as well it has. Doug Gregor (boost book), Eric Niebler, Joel Guzman (quickbook). Vladimir Prus, Rene Rivera, Steve Watanabe. I know there others but these come to mind immediately. Note that I have only addressed the issue of library development which is my main interest. I'm really not seeing this issues related to users of libraries. In particular, CMake has the whole "find" thing which I'm still not even seeing the need for. If I want to use a library, I can build the library and move it to a common place with the headers, specify the include directory and I'm on my way. I'm sure someone will step up to enlighten me on this. Robert Ramey

15 59

[1.61.0] Master branch is closed
by Vladimir Prus 27 Apr '16

27 Apr '16

Boosters, The master branch is now closed for all changes, except by permission from a release manager. Per schedule, the branch will be totally frozen on Saturday. Thanks, The Release Managers

11 51

Test report generation stalled? Re: [1.61.0] Master branch is closed
by Rene Rivera 26 Apr '16

26 Apr '16

On Tue, Apr 26, 2016 at 2:36 PM, Thomas Trummer <th.trummer(a)gmail.com> wrote: > > > On 26 Apr 2016, at 19:47, Rene Rivera <grafikrobot(a)gmail.com> wrote: > > > > Thanks for the info.. But given that we don't have *any* test results > with > > MPI passing (i.e. nothing on develop yet).. I'm afraid it's going to stay > > broken this release. > > Is the test matrix actually working? There should be more recent results > than April 21… > Grrr.. Looks like report generation stopped on the 21st :-( -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

2 3