- Boost - lists.boost.org

[regression tests] feature request: UI integration of bjam requires clause
by Joaquin M López Muñoz 25 Oct '17

25 Oct '17

Hi, Boost regression tests as run by run.py can be explicitly disabled through two different mechanisms: 1. By marking the disabled toolsets with <mark-unusable> in status/explicit-failures-markup.xml. 2. By adding a requires clause in the corresponding Jamfile.v2 file. For instance, in Boost.PolyCollection C++11 is mandated through project : requirements [ requires cxx11_noexcept ] # used as a proxy for C++11 support ... (https://github.com/boostorg/poly_collection/blob/develop/test/Jamfile.v2 ), which results in non-C++11 toolsets being effectively disabled. The problem is that both mechanisms show very differently in the HTML report: http://www.boost.org/development/tests/develop/developer/poly_collection.ht… Toolsets disabled through markup appear grayed out wth a "n/a" legend and an (optional) link to an explanation of why the toolset doesn't work, whereas tests blocked by Jamfile's requires just show a blank column. Would it be possible to modify the regression test HTML reporting utility so that Jamfile-blocked toolsets show also as "n/a" in gray or something similar? The possibility of also adding a link to a custom explanation would be a boon, but I guess this is much harder. This would greatly increase the readability of the reports, particularly by non-savvy users who are likely to deem blank columns as just missing tests that might eventually be filled up. Many thanks, Joaquín M López Muñoz

2 2

Release Note responsibilites for maintainers
by James E. King, III 24 Oct '17

24 Oct '17

The upcoming release of 1.66.0 will be my first release in a maintainer role. How are the release notes generated and what are maintainer's responsibilities during each phase of the release cycle? Thanks, Jim

2 1

RFC.. Steering Committee Bylaws Proposal
by Rene Rivera 24 Oct '17

24 Oct '17

It has become clear to me, and some others, that the recent decisions of the Steering Committee have exposed various problems with how the Steering Committee operates. At CppCon I met with some of the Steering Committee and expressed the concerns with them. I also explained, from my experience in other organizations, how such issues are managed. The result of that is that I will be proposing the Steering Committee adopt operating Bylaws. But before formally presenting them to the Steering Committee I'd like get feedback on them <http://bit.ly/2hI22DN>[1]. The Bylaws hopefully address some key issues that I feel are at the core of the current problems: * Decisions can be made without input from interested parties. * Opaque selection of members. * No recourse by library authors to correct problems. This follows the original goals of the formation of the formation of Steering Committee of being transparent and responsive < http://bit.ly/2yoL5Ij>[2]. [1] <https://github.com/grafikrobot/other/blob/master/ bsc-bylaws-proposal/Boost%20Steering%20Committee%20Bylaws.md> [2] <https://github.com/grafikrobot/other/blob/master/ bsc-bylaws-proposal/2011-05-20%20Boost%20governance%20annotated.pdf> -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net

13 35

boost timer, warnings, backlog
by James E. King, III 24 Oct '17

24 Oct '17

I'm seeing a warning for use of "long long" in a lot of builds, originating in Boost.Timer. I like warning-free builds, so this is something I would like to see resolved. There's an issue in Boost Trac for it: https://svn.boost.org/trac10/ticket/12996 There's a pull request open since April for it (and 3 more going back a couple years): https://github.com/boostorg/timer/pull/4 Is this module still actively maintained? Thanks, Jim

5 6

[Outcome] WG21 papers of interest to Boost and Outcome
by Niall Douglas 24 Oct '17

24 Oct '17

This October's mailing has lots and lots of WG21 papers related to Outcome which were strongly influenced by the peer review here in May. Boost members who contributed to the Outcome v1 review in May should please take a bow and accept thanks for spurring so much discussion and debate regarding these potential future C++ features. Thank you. 1. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0323r3.pdf Utility class to represent expected object 2. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0650r1.pdf C++ Monadic interface 3. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0762r0.pdf Concerns about expected<T, E> from the Boost.Outcome peer review 4. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0779r0.pdf Proposing operator try() (with added native C++ macro functions!) 5. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0786r0.pdf SuccessOrFailure, ValuedOrError and ValuedOrNone types 6. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0824r0.pdf Summary of SG14 discussion on <system_error>: towards exception-less error handling Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

1 0

[timer][msvc] Universal-Windows advice needed
by Beman Dawes 23 Oct '17

23 Oct '17

Pull request https://github.com/boostorg/timer/pull/3 is a fix for Universal-Windows: "universal-windows: GetProcessTimes is not supported". Does anyone have a clue whether the P/R is correct and the best solution? Is the stated problem a temporary one that Microsoft will likely fix, and will it likely be a permanent limitation? Thanks, --Beman

1 0

[system] Header-only Boost.System by default ?
by Damien Buhl 23 Oct '17

23 Oct '17

Dear Boost, Is there any reason why Boost system couldn't be set to be header only by default ? Defining both macros allows it : - BOOST_SYSTEM_NO_DEPRECATED - BOOST_ERROR_CODE_HEADER_ONLY This ease, speeds up and reduces binary size greatly, that it's sad that non-aware Boost User needs to link to some dll/so/dylib of Boost.System per default. It has been in many releases of Boost, wouldn't it be good to set it to be the default for a next release ? Cheers, -- Damien Buhl Software Developer +33 6 77 43 10 05

10 25

[BoostBook] how to automatically test code examples?
by Hans Dembinski 19 Oct '17

19 Oct '17

Hi everyone, I am using BoostBook to prepare the documentation for the proposed histogram library https://github.com/HDembinski/histogram I have written a good deal of the documentation already, and it compiles fine with bjam (thanks to Klemens who showed me how). It says in the BoostBook documentation http://www.boost.org/doc/libs/1_65_1/doc/html/boostbook.html "The BoostBook format allows testcases to be generated by weaving together program fragments from example programs in the documentation. This capability is integrated with testsuite generation so that example programs are normal tests in BoostBook." That's awesome, I would love to use this feature, but the documentation is not explaining how to actually do that. I found the element "testsuite" which probably does what I want. I went on to scan the Boost repository for this BoostBook element, but couldn't find an example to copy from. Could someone help me out? How do I modify my BoostBook and Jam files to generate tests out of the code examples in the documentation? Best regards, Hans

6 14

[msvc] #warning preprocessor directive
by Beman Dawes 17 Oct '17

17 Oct '17

I find it very irritating that VC++ does not support #warning, and have opened a feature request: https://visualstudio.uservoice.com/forums/121579-visual-studio?query=Add%20… The last time #warning was suggested it was rejected because not enough people voted for it. So please consider upvoting it on the above link. The lack of #warning affects Boost libraries in that developers avoid otherwise useful warnings because of the hassle for using an extension not supported by VC++. --Beman

6 20

Merged #149, "Encode architecture and address model in versioned layout names"
by Peter Dimov 17 Oct '17

17 Oct '17

I've just merged https://github.com/boostorg/boost/pull/149, "Encode architecture and address model in versioned layout names", into the develop branch. Let's see how this goes. Welcome to 2005. :-)

6 10