- Boost - lists.boost.org

[gsoc] Change in Google Summer of Code admin
by Niall Douglas 07 Sep '17

07 Sep '17

Dear all, Google Summer of Code 2017 has ended with another successful summer of student coding with probably the highest calibre year we've ever seen. After four years as lead admin for Boost Summer of Code, my time has come to an end. I'll be making way for David Bellot, long time mentor at Boost GSoC and maintainer of Boost.uBLAS. Please join me in welcoming David as new lead admin. I'll be staying on as backup admin next summer to help David settle in. My time as Boost Summer of Code admin has certainly been eventful with lots of surprises, ups and downs. The fact these surprises did not turn into crises is due in large part to a few people in particular who went far beyond the call of duty: * Jon Kalb, who went to bat for the students repeatedly in multiple venues and finding tens of thousands of dollars when it was needed. * Boris Schäling, whom I replaced as lead admin and who acted as backup admin for some years, who also managed to arrange tens of thousands of dollars of sponsorship when it was needed most. * Bryce Adelstein Lelbach, for acting as backup admin these past few years. * Andrew Sutton, the lead GSoC admin before Boris, who gave such detailed and useful early advice and materials on how to best navigate the treacherous waters of Google Summer of Code! And finally to all the mentors who so generously volunteered their time, and to the students every single one of whom successfully finished their projects in my time as admin despite problems with sickness, deaths in close family etc. Some of those students have gone on to become mainstays of the C++ conference circuit, famous names in their own right. I'm sure they would have been so without Google Summer of Code, but I'd like to think that it helped bring them to Boost rather than them getting into C++ via elsewhere. Thank you students! Regards, Niall

5 5

master and develop branches
by James E. King, III 07 Sep '17

07 Sep '17

Could someone point me to documentation on management of the master and develop branches for committers? boostorg/uuid master ends at Jan 11. boostorg/develop has a bunch of stuff in it starting on August 3, 2017. Who is responsible for merging develop into master and when should that happen? Some of the issues are already marked resolved with a milestone of 1.66.0 but they are not in master, only develop. Should pull requests on github go directly into master? I find it confusing to have both and would prefer if there was only one possible destination for pull requests on github. If there are two, someone has to keep one of them updated and that isn't very efficient. Thanks, Jim

4 3

Libraries maintained by CMT?
by James E. King, III 07 Sep '17

07 Sep '17

Hello, I was wondering if there's a page/location that lists the libraries currently being maintained by the community maintainer team? I recently assumed responsibility for maintaining boost::uuid and I was wondering if there was a list that needs to be modified. Thanks, - Jim

4 5

[release] Boost 1.65.1
by Daniel James 07 Sep '17

07 Sep '17

Release 1.65.1 of the Boost C++ Libraries is now available. These open-source libraries work well with the C++ Standard Library, and are usable across a broad spectrum of applications. The Boost license encourages both commercial and non-commercial use. This release contains bug fixes for existing libraries. For details, including download links, see <http://www.boost.org/users/history/version_1_65_1.html> You can also download directly from: <https://dl.bintray.com/boostorg/release/1.65.1/> To install this release on your system, see <http://www.boost.org/doc/libs/release/more/getting_started/index.html> Thanks to everyone who participated in this release. Thanks, -- The Boost Release Team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

1 0

Appveyor and Travis CI for pull requests
by James E. King, III 07 Sep '17

07 Sep '17

Some of the repositories have Appveyor and Travis CI build configuration files in them. I don't see this translating into automatic builds on top of each pull request. I'd like to get the uuid library to the point where a pull request builds on Appveyor and on Travis, so that it is easier to validate the code changes are okay. Could someone let me know if this is possible and if so, how? Thanks, Jim

3 2

[pool] variadically templated object_pool.construct()
by degski 07 Sep '17

07 Sep '17

I would like to request to bring object_pool.hpp up-to-date (all the way to 2011) and include a member function with this signature: template<typename ... Args> element_type * construct( Args && ... args_ ); degski -- "*Ihre sogenannte Religion wirkt bloß wie ein Opiat reizend, betäubend, Schmerzen aus Schwäche stillend.*" - Novalis 1798

2 2

[1.65.1] Release tomorrow
by Daniel James 06 Sep '17

06 Sep '17

Hi, I'm planning on releasing tomorrow. I've written up some release notes: http://www.boost.org/users/history/in_progress.html Let me know if you want any changes to them. Daniel

2 2

[stacktrace] Not working on Cygwin
by Phil Bouchard 06 Sep '17

06 Sep '17

Hi, I tried stacktrace on Cygwin and after tweaking some local and system headers I was able to compile libboost_stacktrace_windbg.a and libboost_stacktrace_addr2line.a but when I run my application calls to boost::stacktrace::stacktrace(1, 1) doesn't output anything. It works fine under Linux using libboost_stacktrace_backtrace.a. Thanks in advance for your help, -Phil

2 2

Upcoming Boost.Fit Review (September 8th-17th)
by Matt Calabrese 05 Sep '17

05 Sep '17

Hi everyone, This coming Friday, September 8th, marks the start of review of the Fit library by Paul Fultz II. Source: https://github.com/pfultz2/Fit Docs: http://fit.readthedocs.org/ This is the second time that the library will go through the review process, with the previous time being in March of 2016. The result of the initial review can be found here: https://lists.boost.org/Archives/boost/2016/04/228770.php In this second review, those who choose to participate should be as rigorous as they'd be in any other review, but are also encouraged to voice whether or not the concerns from March of 2016 were addressed. The following is a brief description of the library from its author: ========== Fit is a header-only C++11/C++14 library that provides utilities for functions and function objects, which can solve many problems with much simpler constructs than whats traditionally been done with metaprogramming. Fit is: - Modern: Fit takes advantages of modern C++11/C++14 features. It support both constexpr initialization and constexpr evaluation of functions. It takes advantage of type deduction, varidiac templates, and perfect forwarding to provide a simple and modern interface. - Relevant: Fit provides utilities for functions and does not try to implement a functional language in C++. As such, Fit solves many problems relevant to C++ programmers, including initialization of function objects and lambdas, overloading with ordering, improved return type deduction, and much more. - Lightweight: Fit builds simple lightweight abstraction on top of function objects. It does not require subscribing to an entire framework. Just use the parts you need. Fit is divided into three components: - Function Adaptors and Decorators: These enhance functions with additional capability. - Functions: These return functions that achieve a specific purpose. - Utilities: These are general utilities that are useful when defining or using functions. ========== Requirements¶ <http://fit.readthedocs.io/en/latest/doc/src/index.html#requirements> This requires a C++11 compiler. There are no third-party dependencies. This has been tested on clang 3.5-3.8, gcc 4.6-6.2, and Visual Studio 2015. Gcc 5.1 is not supported at all, however, gcc 5.4 is supported. Contexpr support¶ <http://fit.readthedocs.io/en/latest/doc/src/index.html#contexpr-support> Both MSVC and gcc 4.6 have limited constexpr support due to many bugs in the implementation of constexpr. However, constexpr initialization of functions is supported when using the FIT_STATIC_FUNCTION <http://fit.readthedocs.io/en/latest/doc/src/FIT_STATIC_FUNCTION> and FIT_STATIC_LAMBDA_FUNCTION <http://fit.readthedocs.io/en/latest/doc/src/FIT_STATIC_LAMBDA_FUNCTION> constructs. Noexcept support¶ <http://fit.readthedocs.io/en/latest/doc/src/index.html#noexcept-support> On older compilers such as gcc 4.6 and gcc 4.7, noexcept is not used due to many bugs in the implementation. Also, most compilers don’t support deducing noexcept with member function pointers. Only newer versions of gcc(4.9 and later) support this. ========== Please take this time to become familiar with the Fit library before the review takes place and feel free to respond in this thread with any additional questions related to the library or its review. Thanks! -- -Matt Calabrese

1 0

Boost.TR1 silently removed with 1.65?
by Tim Rakowski 04 Sep '17

04 Sep '17

Hi, I noticed that boost 1.65 does not contain the tr1 folder and found that the documentation was updated accordingly: http://www.boost.org/doc/libs/1_64_0/ contains http://www.boost.org/doc/libs/1_64_0/libs/tr1/, while http://www.boost.org/doc/libs/1_65_0/ has no http://www.boost.org/doc/libs/1_65_0/libs/tr1/. But http://www.boost.org/users/history/version_1_65_0.html <http://www.boost.org/users/history/version_1_65_0.htmldoes> does not mention this. Even if it was deprecated, shouldn't this be mentioned somewhere? Googling "site:https://lists.boost.org/Archives/boost/ 1.65 tr1" didn't yield anything either :/ Regards, Tim

1 0