November 2019 - Boost - lists.preview.boost.org

[release] Boost 1.72.0 Beta 1
by Michael Caisse 21 Nov '19

21 Nov '19

Boost release 1.72.0 beta 1 is now available at: <https://dl.bintray.com/boostorg/beta/1.72.0.beta.1/source/> The SHA256 checksums are as follows: 5a6b5cbd27b8ca0c7741b715e022a3bf05aecbb1e73dc72dd82eef9622374bd5 boost_1_72_0_b1.7z 6c85a7aed198757f5e4be66a971ae90a25c4ce32703fecfb5bb19019bd80947c boost_1_72_0_b1.tar.bz2 be4a3fdaa84d5a8b25863651043308e02645f3fbf772b7623ee6462fb1dbad09 boost_1_72_0_b1.tar.gz 95181a5f3de0078b8fc031f63a4dc8be4d70b7d3d5cde3b266d2cd98bd4b61b0 boost_1_72_0_b1.zip For details of what's in the release, see <https://www.boost.org/users/history/version_1_72_0.html>. Please download the beta, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

1 0

[release] Boost 1.72.0 Beta 1 Release Candidate 2
by Marshall Clow 21 Nov '19

21 Nov '19

Boost release 1.72.0 beta 1 rc2 is now available at: <https://dl.bintray.com/boostorg/beta/1.72.0.beta.1.rc2/source/> The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ] The SHA256 checksums are as follows: 5a6b5cbd27b8ca0c7741b715e022a3bf05aecbb1e73dc72dd82eef9622374bd5 ./boost_1_72_0_b1_rc2.7z 6c85a7aed198757f5e4be66a971ae90a25c4ce32703fecfb5bb19019bd80947c ./boost_1_72_0_b1_rc2.tar.bz2 be4a3fdaa84d5a8b25863651043308e02645f3fbf772b7623ee6462fb1dbad09 ./boost_1_72_0_b1_rc2.tar.gz 95181a5f3de0078b8fc031f63a4dc8be4d70b7d3d5cde3b266d2cd98bd4b61b0 ./boost_1_72_0_b1_rc2.zip Changes since RC1: * Fix Boost.IOStreams to allow compilation on Mac OS w/LZMA support. Please download the beta release candidate, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

2 2

[release] Boost 1.72.0 Beta 1 Release Candidate 1
by Michael Caisse 18 Nov '19

18 Nov '19

Boost release 1.72.0 beta 1 rc1 is now available at: <https://dl.bintray.com/boostorg/beta/1.72.0.beta.1.rc1/source/> The release notes are not yet available. The updated documentation is not yet available. [ They will be available in a day or two. ] The SHA256 checksums are as follows: 3dd80fc3979c312bf892398c35778d821f6744a7fbf76c8248c85b4f3702e4d4 boost_1_72_0_b1_rc1.7z 676e476a2a1246c7c5e8f40230fa70469f29dfe8aaa5bce0a85f94692e605c68 boost_1_72_0_b1_rc1.tar.bz2 e62e5fdffe0772309c77fc9463a95350ebcabb2ce03f2c6ee177123016756044 boost_1_72_0_b1_rc1.tar.gz e3199f3f5046541570fffacd804d736e1999cfac05df6cc054ec97c8098d000d boost_1_72_0_b1_rc1.zip Please download the beta release candidate, give it a try, and report any problems you encounter. Thanks, -- The Boost Release Team

4 8

回复：Re: [release] Boost 1.72.0 Beta 1 Release Candidate 1
by ckgppl_yan＠sina.cn 18 Nov '19

18 Nov '19

I can compile this release in my macOS catalina, 10.15.1. I don't have lama installed in my OS, so I didn't have the issue below.only some warnings out. Thanks Liang----- 原始邮件 ----- 发件人：Marshall Clow via Boost <boost(a)lists.boost.org> 收件人：turkanis(a)coderage.com, Michael Caisse <mcaisse-lists(a)ciere.com> 抄送人：Marshall Clow <mclow.lists(a)gmail.com>, "boost(a)lists.boost.org List" <boost(a)lists.boost.org> 主题：Re: [boost] [release] Boost 1.72.0 Beta 1 Release Candidate 1 日期：2019年11月19日 04点38分 This appears to be https://github.com/boostorg/iostreams/issues/102, and https://github.com/boostorg/iostreams/pull/103 is a suggested fix. -- Marshall On Mon, Nov 18, 2019 at 11:56 AM Marshall Clow <mclow.lists(a)gmail.com> wrote: > On my Mac, I the version of LZMA that I have installed (via homebrew) does > not have the multi-tasking calls (_lzma_cputhreads and > _lzma_stream_encoder_mt). > It identifies itself: > > $ cat junk.cpp > #include <iostream> > #include "lzma.h" > > int main() { > std::cout << LZMA_VERSION << std::endl; > } > > $ clang++ junk.cpp && ./a.out > 50020042 > $ > > Changing libs/iostreams/src/lzma.cpp thus solves enables things to build: > > #ifndef BOOST_IOSTREAMS_LZMA_NO_MULTITHREADED > - #if LZMA_VERSION < 50020002 > + #if LZMA_VERSION <= 50020042 > #define BOOST_IOSTREAMS_LZMA_NO_MULTITHREADED > #endif > #endif > > -- Marshall > _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost

1 0

Required C++ version in meta/libraries.json
by Mateusz Loskot 18 Nov '19

18 Nov '19

Hi, How can I specify required version of the standard in the library meta info? Where is documentation of libraries.json schema? I've learned that "std":"C++17", for example, in Boost.Any states which standard adopted the library. That is not what I'm after. -- Mateusz Loskot, mateusz(a)loskot.net (Sent from mobile, may suffer from top-posting)

1 1

Jason is getting MARRIED!
by Vinnie Falco 18 Nov '19

18 Nov '19

My JSON library is going to propose to Boost soon, is there anyone who might be willing and able to function in the role of review manager? Thanks!

3 4

pulling the plug on Boost Library Incubator
by Robert Ramey 17 Nov '19

17 Nov '19

I've been maintaining the Boost Library Incubator (www.blincubator.com) for some years now. Maintaining is sort of mis-nomer since it not required any change for years now. I never, ever touch it. I was painful to get to that point though. My motivation is the continuing evolution of github which I believe has come to embody almost of the goals I've had for the inclubator. I would like a couple of tweaks to git hub - or maybe just some changes in our usage of it. For example I'd like to see us proliferate the tags #Boost and #ProposedForBoost to help us search stuff but basically I believe that it has made boost library incubator obsolete. So I'm inclined to terminate it when the domain comes up for renewal the next time. Currently it has about 200 page views / day. I don't really know how much of that a bots/rss feeds and the like. I do you a service which detects and filters out almost all the obvious bogus hits, but still one never knows. BTW - the tipping point for me is the addition of "sponsership" to github. This looks to be the realization of an idea which I've promoted for many years in one for or another. I would like to successful open source project developers and maintainers get rewarded financially rewarded for their efforts and I see that git hub promoters seem to share this view - and they're in a position to move it toward reality. When I can't sleep at night, I imagine that microsoft looked at the incubator and copied features from it into the git hub. Feels like I'm dreaming so I don't feel like I'm awake anymore. Robert Ramey

1 0

Re: [boost] Jason is getting MARRIED!
by Peter Dimov 17 Nov '19

17 Nov '19

> or even `{ "size": 3, "data": [ 1, 2 ] }`. Er, "size": 2 obviously. :-)

1 0

Fwd: Markdown to Quickbook
by Mateusz Loskot 15 Nov '19

15 Nov '19

As boost-docs may not be as popular among subscribers as the development list, I'm bumping my chances for solution... ---------- Forwarded message --------- From: Mateusz Loskot <mateusz(a)loskot.net> Date: Mon, 11 Nov 2019 at 21:25 Subject: Markdown to Quickbook To: <boost-docs(a)lists.boost.org> Hi, Is there an established known method for converting a Markdown document to Quickbook dokument? Best regards, Mateusz Loskot, mateusz(a)loskot.net (Sent from mobile, may suffer from top-posting) -- Mateusz Loskot, http://mateusz.loskot.net

3 3

Removing old branches
by Edward Diener 15 Nov '19

15 Nov '19

I received an issue about Boost PP having lots of old branches which the issuer would like removed. I notice most other Boost libraries also have lots of old branches. Is there any policy about removing these old branches from a Boost library repository ? Many of these old branches are svn-branches, but most of them do not have any value any more and, of course, do not affect the current 'develop' or 'master' branch.

5 7

[preprocessor] Testing C++ standard macro examples
by Edward Diener 14 Nov '19

14 Nov '19

I have added to the 'develop' branch of Boost PP an 'explicit' test with the alias of 'test_iso' in the 'test' subdirectory. This test, depending on the compiler toolset and C++ standard setting used, will test a compiler's ability to expand correctly the macros listed in a C++ standard document's "Macro Replacement" section for C++ standards 2003, 2001, 2014, 2017, and 2020 ( N4835 ). The test uses the __cplusplus setting and the Boost PP BOOST_PP_VARIADICS setting to determine which C++ standard's set of macros to test. This is because the __cplusplus setting alone is misleading for a number of compilers, most notably vc++ and compilers who mimic vc++, who do not set the correct __cplusplus setting for the C++ standard level being used. There are really only three sets of macros from the C++ standard documents which can potentially be tested, despite five different standards being considered. This is because the set of macros to be tested for C++11, C++14, and C++17 are exactly the same. Some compilers do allow C++20 support but do not implement the full __VA_OPT__ support yet, so these compilers will fail the C++20 macro tests with compiler errors. Among these are gcc and vc++, who both document that they do not yet support the stringizing operator with the __VA_OPT__ parameter. Clang also supports C++20 and will run the test and succeed in that mode. You can of course test any compiler at any C++ level and view the results. These tests, unlike Boost PP, do not have any workarounds for any compilers. So the tests form a really good basis for reporting macro expansion preprocessor bugs to various compiler implementations. In the 'test' subdirectory of Boost PP you should be able to run: b2 toolset=atoolset cxxstd=astandard( optional ) test_iso to get the results for any compiler. Any failed results will show the test output, where the original expression, the expanded expression, and for individual failed tests the expected expanded expression will be shown. The actual macros being used are in the appropriate C++ Standard documents or can be seen in the test program which is called cpp_standard.cpp in the same 'test' subdirectory. After the upcoming release I will push this to the 'master' branch. Please note that the test is an 'explicit' test so it is not normally run when you just run the tests for Boost PP.

1 0

fixed_string: Request for review
by Krystian Stasiowski 13 Nov '19

13 Nov '19

Hi all, My name Is Krystian Stasiowski. I'm currently attending college as a Computer Science major, am active on the C++ Language Slack, and starting to contribute to ISO C++. Vinnie offered for me to take the lead on submitting Boost.FixedString for a formal review, so here I am! Applicable links: Github: https://github.com/18 Repo: https://github.com/18/fixed_string Docs: https://18.github.io/doc/fixed_string

2 1

Late fix for Boost PP
by Edward Diener 12 Nov '19

12 Nov '19

I had added support in the Boost PP library in C20 mode ( __cplusplus > 201703L ) for the __VA_OPT__ construct and enhanced an internal function used fairly extensively in the library to use this functionality in c20 mode when __VA_OPT__ was supported. I had tested this against the compilers which I knew could operate in c20 mode, gcc and clang, and all was well. I just discovered that the vc++ compiler can also work in c20 mode in Boost PP as defined above if you pass the '/std:c++latest' and the '/Zc:__cplusplus' command line switches and that vc++, in its usual non-standard way, blows up badly when doing so using the preprocessor library because it can not handle the rather simple code that checks for __VA_OPT__ support in c20 mode. I have a simple fix for this which is to turn off the __VA_OPT__ support and __VA_OPT__ support checking in c20 mode specifically for vc++ and removes which I have pushed to 'develop'. Can I push this fix to the 'master' branch now ? The fix needs to get in the coming release or else vc++ programmers specifying both the '/std:c++latest' and the '/Zc:__cplusplus' command line switched will not be able to use Boost PP and the many libraries which use Boost PP in the upcoming release. I apologize for the seeming aggressiveness of this change, which incorporated the c20 __VA_OPT__ support internally in some much-used Boost PP functionality when c20 mode is being used, but I did not anticipate that it would blow up on me, although maybe I should have. I can also remove that internal dependency with a very simple one-line change. I realize that Boost PP stability has to be maintained, even in c20 mode for the few compilers which support that mode and apologize again that I have endangered it there.

1 1

Re: [boost] [Boost][Proposal] library for enhanced switch syntax.
by рустам абдумаликов 12 Nov '19

12 Nov '19

Phil Endecott wrote: > Specifically thinking about strings, there are numerous ways > that it could be done. Starting with > (1): the obvious sequence of if-else-if: > ... > (2): binary search using nested switches: > ... > (3) character-by-character comparison using nested switches: > ... > (4) converting to a 64-bit integer, for strings of up to 8 characters: > ... Firstly my implementation was never particularly about string in "switch" it is just one of the applications. Secondly, example 3-4 assume additional implementation( can take quite a time to do it right ), it isn't like you have it out of the box, this is exactly what my statement was about( example 1-2 don't count, they are non-scalable ). Lets rather consider something that is more complex: -- Example_1 "Parse file by extension": switch( hash_it( get_file_extention( file_name ) ) ) { case "cpp"HASH: case "cc"HASH: case "c++"HASH: case "cxx"HASH: case "C"HASH: { ... } break; case "hpp"HASH: case "hh"HASH: case "h++"HASH: case "hxx"HASH: case "H"HASH: { ... } break; } // OR // I think this way it is much readable eswitch( get_file_extention( file_name ) ) >> case_( any_from( "cpp", "cc", "c++", "cxx", "C" ) ) >> [&]{...} >> case_( any_from( "h", "hpp", "hh", "h++", "hxx", "H" ) ) >> [&]{...}; // OR // even this could be possible( but not yet implemented ) eswitch( get_file_extention( file_name ) ) >> case_( "cpp", "cc", "c++", "cxx", "C" ) >> [&]{...} >> case_( "h", "hpp", "hh", "h++", "hxx", "H" ) >> [&]{...}; -- Example_2 "Parse HTTP header with Regex": // O_o too much boilerplate if( std::regex_match( line, "^.+ 200 .+$"_r ) ){...} else if( std::regex_match( line, "^.+ 404 .+$"_r ) ){...} else if( std::regex_match( line, "^.+: .+$"_r ) ){...} else { terminate(); } // OR // I think this way your intention is clearer eswitch( line ) >> case_( "^.+ 200 .+$"_r ) >> []{...} // match for "HTTP/1.1 200 OK" case_( "^.+ 404 .+$"_r ) >> []{...} // match for "HTTP/1.1 404 Not Found" case_( "^.+: .+$"_r ) >> [&]{...} >> // match for "key: value" default_ >> []{ terminate(); }; -- Example_2 "match in range of values": // Error prone approach if( value >= 1 && value <= 10 ){ Print("Value in a range[1,10]"); } if( value >= 11 && value <= 20 ){ Print("Value in a range[11,20]"); } else { Print('?'); }; /// OR eswitch( value ) >> case_( _1.in( 1, 10 ) ) >> []{ Print("Value in a range[1,10]"); } >> case_( _1.in( 11, 20 ) ) >> []{ Print("Value in a range[11,20]"); } >> default_ >> []{ Print('?'); }; // _1 it is lazy index mapping for the params in eswitch I my opinion "eswitch" looks more readable, more intuitive, less error prone and furthermore it is extensible. P.S. Here https://github.com/rabdumalikov/proposals/blob/master/eswitch_boost_proposa… I had described why I think it is important( just in case you've missed it ).

3 4

[release] 1.72.0 closed for Beta
by Michael Caisse 11 Nov '19

11 Nov '19

The master branch is now closed for all changes except by permission for the Beta release. Also, remember to add your libraries' changes to the release notes at: <https://github.com/boostorg/website/blob/master/feed/history/boost_1_72_1.q…> Thanks, -- The Boost Release Team

4 4

[Boost][Proposal] library for enhanced switch syntax. Request for Comments
by рустам абдумаликов 11 Nov '19

11 Nov '19

Hi All, I wrote a library *eswitch* which provides enhanced functionality for* C++ switch*. Please take a look and leave your comments. *=====================* *Motivation:* *=====================* To overcome "*native switch*" limitations: - one parameter per "*native switch*" - the parameter restricted to only *integral *types( int, char, enum ... ). "*eswitch*" supports any number of parameters and almost without restriction on their *type*, as long as the *type *is comparable( i.e. has* operator==* ). *=====================Why it is important?=====================* Here is the most viewed questions on the *stackoverflow*: FEATURE VIEWS Multiple conditions in switch case <https://stackoverflow.com/questions/68578/multiple-cases-in-switch-statement> 850k Switch for string <https://stackoverflow.com/questions/650162/why-the-switch-statement-cannot-…> 693k Case match in range <https://stackoverflow.com/questions/9432226/how-do-i-select-a-range-of-valu…> 133k Over a million views indicate how many people out there are disappointed with limited functionality of "*native switch*". Building parallels with such operators as "*if*"/"*while*"... it is expected by default that "*native switch*" should have the same possibilities: - be able to work with *non-integral* types as well - be able to compose complex conditions like we do in other operators " *if*"/"*while*"... Unfortunately it is not the case up till now. There was a proposal in 2013 *Relax switch statement <http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3627.html>*, and committee agreed about importance of this topic. There also was *StringSwitch <http://llvm.org/doxygen/classllvm_1_1StringSwitch.html>* implementation by *LLVM *and *Case ranges <https://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html>* non-standard extension which is supported by *gcc*, *intel C/C++* and *clang*. Nevertheless, we still don't have common and universal solution. People want to overcome current "*native switch*" limitation either by implementing their own solution, non-standard extension or even trying to standardize it. Making proposed *eswitch <https://github.com/rabdumalikov/eswitch_v4>* functionality part of the *Boost-Library *will provide millions of developers useful, universal and agile functionality in order to finally fulfill their needs. *=====================repository:=====================* https://github.com/rabdumalikov/eswitch_v4 *=====================References:=====================/// "switch for non-integral" on stackoverflow* 1. https://stackoverflow.com/questions/650162/why-the-switch-statement-cannot-… 2. https://stackoverflow.com/questions/16388510/evaluate-a-string-with-a-switc… 3. https://stackoverflow.com/questions/5452188/switch-case-statement-in-c-with… 4. https://stackoverflow.com/questions/19273092/character-in-switch-statement-c 5. https://stackoverflow.com/questions/4165131/c-c-switch-for-non-integers 6. https://stackoverflow.com/questions/27536575/switch-case-on-char */// "Multiple conditions" on stackoverflow* 7. https://stackoverflow.com/questions/8644096/multiple-conditions-in-switch-c… 8. https://stackoverflow.com/questions/68578/multiple-cases-in-switch-statement */// "Ranges in case" on stackoverflow* 9. https://stackoverflow.com/questions/9432226/how-do-i-select-a-range-of-valu… */// "Case ranges" - non-standard extension* 10. https://gcc.gnu.org/onlinedocs/gcc/Case-Ranges.html */// LLVM "StringSwitch"* 11. http://llvm.org/doxygen/classllvm_1_1StringSwitch.html */// "Relax switch statement" proposal* 12. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3627.html */// "N3627 Relaxed switch statement" c++ committee status* 13. https://cplusplus.github.io/EWG/ewg-active.html *Best Regards.*

7 7

[Boost][Proposal] library for enhanced switch syntax. Request for Comments #2
by рустам абдумаликов 09 Nov '19

09 Nov '19

Hi All, First attempt kind of failed due to alignment:( So this is another one) So I wrote a library eswitch which provides enhanced functionality for C++ switch. Please take a look and leave your comments. Motivation: To overcome native switch limitations: 1) one parameter per switch 2) the parameter restricted to only integral types( int, char, enum ... ) Whereas "eswitch" supports any number of parameters and almost without restriction on their type, as long as the type is comparable( i.e. has operator== ). Why it is important? Because people want to overcome current switch limitation either by implementing their own solution, non-standard extension or even trying to standardize it. Making proposed eswitch functionality part of the Boost-Library will provide millions of developers useful, universal and agile functionality in order to finally fulfill their needs. Full proposal here: https://github.com/rabdumalikov/proposals/blob/master/eswitch_boost_proposa… Repository: https://github.com/rabdumalikov/eswitch_v4 Best Regards Rustam Abdumalikov

2 1

Re: [boost] fixed_string: Request for review
by Ggh 09 Nov '19

09 Nov '19

First: 1)wonderful documentation! 2) A few ideas => 2.1)find_count_of =>find number of occurences of 'argument' 2.2)get_sequence_of =>return sequence of 'begin'=>'end' 2.3)set_sequence_of => set sequence of 'begin'=>'end' with 'arg' 2.4)set_slice_of => ~= 2.3) 2.5)get_slice_of => ~= 2.2) 6)char_traits<T> here but =>> also for any type/class? Quoting Krystian Stasiowski via Boost <boost(a)lists.boost.org>: Good work! Please regard this as constructive critism, Ty G > Hi a > ,y > My name Is Krystian Stasiowski. I'm currently attending college as a > Computer Science major, am active on the C++ Language Slack, and starting > to contribute to ISO C++. Vinnie offered for me to take the lead on > submitting Boost.FixedString for a formal review, so here I am! > > Applicable links: > Github: https://github.com/18 > Repo: https://github.com/18/fixed_string > Docs: https://18.github.io/doc/fixed_string > > _______________________________________________ > Unsubscribe & other changes: > http://lists.boost.org/mailman/listinfo.cgi/boost Tell me, and I forget. Ask me, and I discover...

1 0

[container] static_string ?
by Vinnie Falco 09 Nov '19

09 Nov '19

Beast has static_string which someone has asked to be move, is there any interest in moving this to Boost.Container? See: <https://github.com/boostorg/beast/issues/1691> <https://github.com/boostorg/beast/blob/b7230f12f16fe7a9f7a1ece5be1f607c8552…> -- Regards, Vinnie Follow me on GitHub: https://github.com/vinniefalco

19 50

[Metrics] - library idea reviews
by cpijcke.wall＠laposte.net 08 Nov '19

08 Nov '19

Hi, Two years ago, I have created a library who handle metrics type (distance, speed, flow rate, ...). I have simply applied the principle of chrono library (std:: one from clang in my case) and have applied it to other types. I have decided some weeks ago to make it public on github. This project also manage inter-type conversion(speed to distance, or volume to flow rate for example). Before going much further in this project, I would like to get your though about it. Maybe some of you already have had a similar idea, maybe even in a more advanced state, or with another principle of conversion between types? Here is the project link: https://github.com/xtofpic/metrics if you are interested. In this case, don't blame me for the state of the code actually, I know it still need a huge works to do on testing and code reducing by better c++ templates. But if you can just let me know what you think of the idea? And if there is an opportunity to eventually integrate this project into boost afterwards? Best regards, Christophe Pijcke.

2 2

How to make boost write_xml not escape angle brackets?
by Ananya Maiti 07 Nov '19

07 Nov '19

Hi all, I am trying to write some data in a xml file using boost write_xml() function. My data has some angle brackets in it e.g. <![CDATA[name]]> . But when I use boost::property_tree::write_xml() to write the data node to xml file it escapes the angle brackets to < and > tags. I even tried using unicode \x3C , \x3E but still it escapes them. Is there any way to tell boost to not escape the characters in a non html safe way ? Regards, Ananyo Maiti

1 0

[1.72][Test][Math][Fiber] Recent breaking change in Boost.Test breaks fiber/math tests
by John Maddock 07 Nov '19

07 Nov '19

This change: https://github.com/boostorg/test/commit/1c4533f7654d4c049cc6a34a43a5c10cde5… To Boost test (which I'm sure has been long signaled, I just wasn't aware of it), breaks one Math lib test (develop and master), and quite a number of Fibre tests (also develop and master), the Math failure should be fixed in develop (https://github.com/boostorg/math/commit/1d04bf714e809d386088ce135e3f9ea04ca…) and will get merged to master once CI is green. Not sure if anything is in the works for Fiber. Just a wee heads-up. Best, John. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

4 8

Best Boost to use for boost::python with Python 3.7/3.8?
by Kacvinsky, Tom 06 Nov '19

06 Nov '19

Subject is the question. Any recommendations? Looking at the boost documentation for boost::python, it doesn't look like the copyright has changed since 2015, but compiling boost 1.6.9.0, for instance, points out there have been code changes.

1 0

[Test] log_level (was RE: [1.72][Test][Math][Fiber] Recent breaking change in Boost.Test breaks fiber/math tests)
by Peter Bartlett 05 Nov '19

05 Nov '19

>I think it is very counter-intuitive that messages only emerge to the normal output if there is an error or --log_level="message" > >And that > > #define BOOST_TEST_LOG_LEVEL "message" > >does not appear to have the same effect as --log_level="message" > >which is also surprising, and in my book a buglet? > >I suggest that this behaviour should be changed so that BOOST_TEST_MESSAGE >*always* produces output. > >BOOST_AUTO_TEST_CASE(test_message) >{ > BOOST_TEST_MESSAGE("\nTest BOOST_TEST_MESSAGE.\n"); } // BOOST_AUTO_TEST_CASE(test_message) > >Otherwise I am sure I will not be the only person confused. > >At the very least the documentation should highlight that ones expectation may not match what actually happens. Hi, I think it would be a bad idea to change the default value of --log_level (in your suggestion, from "error" to "message"). The default has been "error" for a long time (I don't like to count how long, because it makes me feel old!). And I'm sure that a lot of parsing tools have been built around the world assuming Boost.Test output is of a certain form. I know I've had to 'teach' various CI systems Boost.Test-speak over the years. > #define BOOST_TEST_LOG_LEVEL "message" BOOST_TEST_LOG_LEVEL is supported as an environment variable, not as a macro. Supporting it as a macro would be a bad idea for similar reasons as above - the layout and volume of the output should be for the *user* to control not the author of the tests, or otherwise the user can't rely on what the test output is going to look like from one library to the next. If you, personally, always want the log_level to be 'message', then you should set the environment variable BOOST_TEST_LOG_LEVEL permanently on your system. Hope that helps, Pete

1 0

[histogram] [1.72] merge usability patch?
by Hans Dembinski 05 Nov '19

05 Nov '19

Dear release managers, I have a patch in my develop branch for Boost.Histogram which would like to merge to the master for the 1.72 release. https://github.com/boostorg/histogram/commit/d658aff0b09f73d4f0d3b729b13518… It is a rather intrusive patch, hence my question whether I am allowed to merge this. There is no change to the public interface. The patch provides nice compile-time error messages when users make mistakes in using the histogram instead of spilling out internals details as it does now, that's why I think it would be good to have this already in the upcoming release instead of the next after. The patch passes all the tests in the CI (and new tests developed for this feature). Line coverage remains at 100 % for Boost.Histogram, therefore I am confident that applying the patch is safe. Best regards, Hans

1 0