- Boost - lists.boost.org

Spirit 3.0.0
by Joel de Guzman 18 May '15

18 May '15

Hello! C++ Now 2015. Today is the official release of Spirit X3, aka Spirit 3.0.0. X3 will be in beta, coexisting side by side with Qi, Karma, Lex and Classic. If you are a Qi user. The best place to start are the examples, especially rexpr and x3 fun. Remember to use a compiler with c++14 capabilities: clang 3.4 or greater gcc 4.9 or greater Follow this link for more: http://boost-spirit.com/home/2015/05/16/spirit-3-0-0/ Cheers! -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/

4 5

[type_traits] Time to upgrade to "version 2" ?
by John Maddock 17 May '15

17 May '15

Now that the release is out it's decision time: I'd like to merge the "Version2" branch of type_traits to develop, it passes all the tests, and I've been using it exclusively for testing and development locally for a few months now without issues. But.... it's a big change with the potential to break a lot of folks stuff if things go wrong given that this is such a core component. To recap the main advantages are: * Removed all the redundant cruft that's no longer required for old/broken compilers we don't support anymore anyway. * Very nearly dependency free (other than Config), there's just comon_type which still has dependencies elsewhere - and even that disappears for a C++11 compiler. * Much cleaner, easier to understand code, now that the horrid obfuscating macros introduced by MPL have gone. * Fewer template instantiations than before as much of the indirection / forwarding templates have been removed. * As a result code using these headers should be somewhat faster to compile - both with fewer template instantiations, and a much lighter #include load. Note that as a result of this change, a number of undocumented headers which were none the less being used in Boost have been deprecated. The headers still exist, but warn loud and clear about their deprecated status, so folks will get a lot of warnings to begin with. I know Edward Diener has submitted some PR's to fix these, but I plan to make a concerted attack on any remaining once the new version is in develop. So here's the question, how do we proceed? My thoughts are to basically go ahead and merge, but not merge to master until after the next release at the earliest to give everything a chance to bed down, and the required changes in other libraries to filter through. Or we could have some sort of mini-review either formally or informally to check things out before the merge - of course folks are most welcome to do this anyway! Let me know what you think, best, John.

9 14

[type_traits] difference in decay semantic between boost and standard library
by Anton Bikineev 17 May '15

17 May '15

Hi Boost, Is it expected semantic of boost::decay not to strip top-level constness? Thanks.

1 0

[testing] Regression unresolved issues page
by Adam Wulkiewicz 15 May '15

15 May '15

Hi, The unresolved issues page seems to be outdated (only msvc-8.0 failures can be found there): http://www.boost.org/development/tests/develop/developer/issues.html It's because from all required toolsets mentioned here: https://github.com/boostorg/boost/blob/develop/status/explicit-failures-mar… only the msvc-8.0 is currently tested. The required compilers are quite old ones. I'm not sure how we should addres this issue. I get an impression that in the past this page was used differently than it is now. I'm not sure how though. The ToC/menu is also missing. Anyway, we could: - add only some specific, more modern required toolsets to the explicit-failures-markup.xml - ignore the required toolsets entries and display the issues detected in a library for all non-disabled toolsets - remove the issues page I'd probably go with the second option and treat this page as a complement of the regression matrix. What do you think? Regards, Adam

1 0

[ELFIO] - New library proposal
by Serge Lamikhov-Center 15 May '15

15 May '15

Hello Boost community! I'd like to determine interest in possible new library submission. ELFIO is header-only C++ library that provides a simple interface for reading and generating files in ELF binary format. It is a mature library and is in use by a number of open source and commercial projects. It is a part of some Linux distributions as well as Cygwin project. Would you please have a look at the library's home page located at: http://elfio.sourceforge.net Documentation: http://elfio.sourceforge.net/elfio.pdf Library download: http://sourceforge.net/projects/elfio/files/ELFIO-sources/ELFIO-3.1/ and its source code available through: http://github.com/serge1/ELFIO Please share your opinion on making this library be a part of the Boost. Thank you and Best regards, Serge

5 6

[test] Problem with BOOST_TEST_MESSAGE
by Edward Diener 15 May '15

15 May '15

In testing out a library with Boost.Test I want to inject informational messages that will appear in the output of the test results. When I use BOOST_TEST_MESSAGE with the correct logging level my message appears in the output if there is some sort of Boost.Test error during my tests. However if my unit test does not have a Boost.Test error my BOOST_TEST_MESSAGE does not appear. Needless to say I always want my BOOST_TEST_MESSAGE messages to always appear in the output. Is there a solution to this ?

4 12

[website] Broken uBLAS link
by Renato Florentino Garcia 14 May '15

14 May '15

Hi, The link to uBLAS documentation page on http://www.boost.org/doc/libs points to http://www.boost.org/doc/libs/release/libs/numeric/ublas/doc/index.htm instead of http://www.boost.org/doc/libs/release/libs/numeric/ublas/doc/index.html There are a missing l on .html Regards, Renato Garcia

1 0

[testing] Looking for test runner owner
by Andrzej Krzemienski 14 May '15

14 May '15

Hi All, The test matrix in branch 'master' contains these two test runners: oracle-intel-S2-stlport4 <http://www.boost.org/development/tests/master/oracle-intel-S2-stlport4.html> and oracle-sparc-S2-stlport4 <http://www.boost.org/development/tests/master/oracle-sparc-S2-stlport4.html> Could the owner of these reply to me? I am trying to fix a bug on this platform in Boost.Optional, and would require some assistance. Regards, &rzej

2 1

[variant] 1.58 boost/variant/get.hpp compile errors
by Maarten de Vries 14 May '15

14 May '15

Hello list, I recently updated to boost 1.58 and one of my programs didn't compile any more. The reason was the <boost/variant/get.hpp> header. A simple test program and compiler output is attached below. Swapping the order of the includes or including <boost/type_traits/remove_cv.hpp> before <boost/variant/get.hpp> in the test program will get rid of the errors. It would appear that <boost/variant/detail/element_index.hpp> should include <boost/type_traits/remove_cv.hpp>. Kind regards, Maarten de Vries Test program: #include <boost/variant/get.hpp> > #include <boost/variant/variant.hpp> > > int main() { > return 0; > } > Compiler output g++ (GCC) 4.9.2 20150304 (prerelease): In file included from /usr/include/boost/variant/get.hpp:24:0, > from test.cpp:1: > /usr/include/boost/variant/detail/element_index.hpp:38:69: error: > ‘remove_cv’ in namespace ‘boost’ does not name a template type > variant_element_functor<boost::mpl::_1, typename > boost::remove_cv<T>::type > > ^ > /usr/include/boost/variant/detail/element_index.hpp:38:78: error: expected > template-argument before ‘<’ token > variant_element_functor<boost::mpl::_1, typename > boost::remove_cv<T>::type > > > ^ > /usr/include/boost/variant/detail/element_index.hpp:38:78: error: expected > ‘>’ before ‘<’ token > /usr/include/boost/variant/detail/element_index.hpp:38:88: error: template > argument 2 is invalid > variant_element_functor<boost::mpl::_1, typename > boost::remove_cv<T>::type > > > ^ > /usr/include/boost/variant/detail/element_index.hpp:39:9: error: expected > ‘::’ before ‘>’ token > > > ^ > /usr/include/boost/variant/detail/element_index.hpp:39:9: error: expected > identifier before ‘>’ token > /usr/include/boost/variant/detail/element_index.hpp:39:9: error: template > argument 2 is invalid > /usr/include/boost/variant/detail/element_index.hpp:40:5: error: expected > ‘::’ before ‘>’ token > > > ^ > /usr/include/boost/variant/detail/element_index.hpp:40:5: error: expected > identifier before ‘>’ token > /usr/include/boost/variant/detail/element_index.hpp:40:5: error: template > argument 2 is invalid > /usr/include/boost/variant/detail/element_index.hpp:41:1: error: expected > ‘::’ before ‘{’ token > {}; > ^ > /usr/include/boost/variant/detail/element_index.hpp:41:1: error: expected > class-name before ‘{’ token >

3 3

Community Maintainence Team - a Modest proposal
by Robert Ramey 13 May '15

13 May '15

Today at 12:45 in Bethe is the operations meeting of the Boost Community Library Maintainence team. In advance of that meeting I'd like to render my proposal on this list so I have it written down. Premise:The library maintainence team does not and will likely never have sufficient resources to maintain libraries without current maintainers. Proposal: a) The CMT will solicit volunteers to take over maintainence of specific libraries. b) The most likely source of such volunteers are those working in companies which use and depend upon the libraries in maintainence. Such companies will be expected to support the library maintainence by permitting the maintainer to undertake this effort using company time and resources. c) Since we don't have a list of which companies are using which libraries, we will send a solicitation to volunteer to every person who has posted a bug report for the library in question on the TRAC system. I believe this is the most likely source for prospective maintainers. d) Companies that support maintainence of a particular library will be permited to place their logo and link on the TRAC page for that library. So they will receive the following benefits from sponsoring the maintainece of the library. 1) They will be demonstrating their commitment to the high standard of software development that Boost supports. 2) By placing their logo and link on the track page, they will be encouraging and facilitating prospective employees who desire to work for such an organization to contact them. That is, they will have a leg up on attracting the highest quality C++ programmers. 3) They will be guarenteed timely and rigorous maintainence of the library which they depend on. 4) They will have the inside track on proposing and implementing any library enhancements that they desire. 5) They will benefit from collaboration of the boost community which provides numerous valuable benefits: Bug fixes submitted by users, suggestions for enhancements. etc. The value of all these benefits to the sponsoring company will far, far out weigh the incremental cost of the employee time. In many cases, since employees have to maintain the library anyway - the incremental cost is zero anyway. This moves the responsibility for library maintainence to those most willing and able to undertake it. The role of the CMT would be to promote, recruit, certify, and monitor library maintainence. The CMT would have the authority to move the responsability from maintainer to another. The current practice of having a single person/entity responsible for maintainence of a library would continue unchanged. Robert Ramey

4 7