- Boost - lists.preview.boost.org

[config][type_traits] Support for final keyword in Boost?
by John Maddock 16 Aug '14

16 Aug '14

I have a couple of pull requests to add support for the final keyword in Boost.Config and an is_final trait to type traits, so my questions are: 1) Are these generally useful? 2) Do we need BOOST_NO_CXX11_FINAL_CLASS and BOOST_NO_CXX11_FINAL_OVERRIDE or will a single BOOST_NO_CXX11_FINAL do? 3) The trait appears to be unimplementable via SFINAE (anyone care to prove me wrong?) which means it's only usable on GCC and lookalikes which have an __is_final intrinsic. Should we still add this to Boost or is the answer "use GCC's native features" given that a Boost version effectively adds nothing? Thanks! John.

4 3

[docbook] Add detail namespace to Reference section
by Benedek Thaler 16 Aug '14

16 Aug '14

Hi, I have the following example code fragment: namespace boost { namespace detail { /** documentation */ class implementation {}; } // namespace detail using detail::implementation; } // namespace boost I'd like to have the class `implementation` show up in the Reference section generated by doxygen+docbook-xsl+boost build+docbook+... . Issue is, every namespace which name contains the string "detail" is excluded somehow. The direct output of doxygen has it, but not the docbook version. I couldn't find any EXCLUDE_SYMBOLS setting (it's not set in the doxyfile)or anything relevant amongst the docbook-xsl params or in the boost build scripts. Google search term "doxygen ignores detail namespace" and the like did not help. Adding documentation to the using statement and/or TYPEDEF_HIDES_STRUCT did not help. Thanks, Benedek

2 3

Should intrusive_ptr copy constructors be declared noexcept?
by James Yonan 16 Aug '14

16 Aug '14

Currently, intrusive_ptr's copy constructors are not declared noexcept. This disables the std::function small object optimization when intrusive_ptr objects are passed by value in a lambda closure. The attached patch tries to fix this by making the copy constructors conditionally noexcept, based on the noexcept status of the user-provided intrusive_ptr_add_ref function. James

1 0

[Boost][filesystem] imbue in global constructor crashes
by Peter Bindels 15 Aug '14

15 Aug '14

Hi all, When trying to use a global constructor to set the locale to utf8 for an entire project, the system failed to start due to global constructor ordering making the override happen before the std::locale object itself was initialized. Looking into the boost::filesystem code for imbue it seemed that there were a few different implementations, one of which could work. I've tried to keep the same side conditions and made this same lazy-initialization approach for all platforms, which should keep working in all the same conditions and also work for a global constructor overriding the locale. I've attached the patch. I hope that this change can be integrated into boost::filesystem or that we can have a constructive discussion on what solution we should be making. Best regards, Peter Bindels

2 1

[variant] static_visitor constructor error with boost 1.56.0 and g++ 4.5.1
by Richard Hadsell 15 Aug '14

15 Aug '14

I am trying to upgrade from Boost 1.55 to 1.56. I get this error with G++ 4.5.1: In file included from ...: .../boost/variant/static_visitor.hpp:52:24: error: 'boost::static_visitor<R>::static_visitor()' declared with non-public access cannot be defaulted in the class body .../boost/variant/static_visitor.hpp:53:25: error: 'boost::static_visitor<R>::~static_visitor()' declared with non-public access cannot be defaulted in the class body The OS is Linux Fedora 14. The compiler is gcc version 4.5.1 20100924 (Red Hat 4.5.1-4). I saw a similar problem in noncopyable.hpp, when upgrading to Boost 1.55. Andrey Semashev fixed it, and it looks like static_visitor requires the same fix. In static_visitor.hpp change line 51 from #ifndef BOOST_NO_DEFAULTED_FUNCTIONS to #if !defined(BOOST_NO_CXX11_DEFAULTED_FUNCTIONS) && !defined(BOOST_NO_CXX11_NON_PUBLIC_DEFAULTED_FUNCTIONS) I think this would be appropriate for any non-public defaulted functions, not just the ones that trip up code I happen to compile. Dick Hadsell 203-992-6320 Fax: 203-992-6001 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studioshttp://www.blueskystudios.com 1 American Lane, Greenwich, CT 06831-2560 Follow Blue Sky Studios on Facebook <http://www.facebook.com/BlueSkyStudios> and Twitter <http://twitter.com/#%21/blueskystudios>

2 1

[1.56] PDF documentation available
by John Maddock 14 Aug '14

14 Aug '14

The PDF build of Boost's documentation for 1.56 is now available from the usual address: https://sourceforge.net/projects/boost/files/boost-docs/1.56.0/ Note that it includes only the subset of Boost libraries whose documentation is quickbook/docbook based. John Maddock.

6 8

[container] 1.56.0 flat_map static assert typo ?
by feverzsj 14 Aug '14

14 Aug '14

hi, list in <boost/container/flat_map.hpp>, the ctors seems to contain a wrong static assert: flat_map() : m_flat_tree() { //Allocator type must be std::pair<CONST Key, T> BOOST_STATIC_ASSERT((container_detail::is_same<std::pair<Key, T>, typename Allocator::value_type>::value)); } missing "const" ? regards. -- View this message in context: http://boost.2283326.n4.nabble.com/boost-container-1-56-0-flat-map-static-a… Sent from the Boost - Dev mailing list archive at Nabble.com.

3 3

Boost Library Writers Workshop at CPP Con 2014
by Robert Ramey 14 Aug '14

14 Aug '14

Have you been lurking out there in cyberspace all these years? Slaving away on your fantastic new library for boost? Stuck, discouraged, concerned about getting ripped apart on the mailing list? Well, this is for you !!!! The Boost Library Writers Workshop http://rrsd.com/blincubator.com/open-content/ . Share your library and get it critiqued by you peer group - other unsung authors battling the same daemons. Best of all you can attend this workshop without being registered at the conference - to attend this workshop all you have to do is ... attend!. That's right, it's absolutely free. That's right free. And not free like in free software. Really free like "free beer". (note: there is no free beer). So if you're in the area and you want to get your library off your chest because it's weighing you down, keeping you awake, ruining your love life attend this workshop. Spaces are limited so signup now at the above web page. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/Boost-Library-Writers-Workshop-at-CPP-Co… Sent from the Boost - Dev mailing list archive at Nabble.com.

1 0

[GitHub] Transferring a new library's repo to boostorg?
by Beman Dawes 14 Aug '14

14 Aug '14

https://svn.boost.org/trac/boost/wiki/NewLibFromGit describes "Creating a new library from an existing Git repository". It seems to cover the case where the existing git repo isn't in the exact boost branch organizational structure required. The Boost Endian library is ready to be moved to boostorg on GitHub so it can be tested on develop, checked by release managers, and otherwise readied to be added to 1.57.0. It is already on GitHub and AFAIK has the usual boost branch and directory structure. GitHub has a mechanism to transfer a repo between users or organizations. This would seem the easiest and most direct approach for boost endian. Is there any reason not to give it a try, and if it works as advertized then add it to https://svn.boost.org/trac/boost/wiki/NewLibFromGit as an additional option? --Beman

3 6

Comments on generic matrix library with specific 3D operations -> news and documentation
by Fabien Picarougne 13 Aug '14

13 Aug '14

Hello Boost, After some holidays, I have finished to implement some functionalities of my matrix library (https://bitbucket.org/fpicarougne/template-matrix-library) I have also begin to write some documentation (http://www.polytech.univ-nantes.fr/wikinfo/gmt/) relatively poor at this stage but sufficient (I think) to give you a real idea of the library. Globally, functionalities are closed to Boost::QVM but implementation strategy is different and uses more C++11 techniques as variadic templates for example. I must also say that I took over the syntax of the swizzling operator from this library. I would appreciate if you could give me feedback on this code. The code has been compiled on MSVC2013 and gcc 4.8 without warning (except those that come from Boost.Preprocessor) by using these parameters (in gcc): -Wall \ -Wextra \ -pedantic \ -Wmain \ -Wundef \ -Wsign-conversion \ -Wuninitialized \ -Wshadow \ -Wunreachable-code \ -Wswitch-default \ -Wswitch-enum \ -Wcast-align \ -Wmissing-include-dirs \ -Winit-self \ -Wfloat-equal \ -Wdouble-promotion \ -Wzero-as-null-pointer-constant \ -Wunused-parameter Current namespace is temporary (and inherited from old library) and will be changed in the future. Code needs also to be separated in more header files (this work will be done soon). I have kept in the git repository the "test.cpp" file which allows me to test some functionalities (and incidentally allow you to evaluate the usage syntax). Fabien

2 1

[git] confusion setting moduler-boost to 'master'
by Edward Diener 13 Aug '14

13 Aug '14

Somehow my local modular-boost is confused. I have set the top-level to 'master' and each of the sub-modules to 'master'. Yet git still shows it wants to commit each of the submodules at the library level as all are marked dirty. So I try: git reset --hard master git submodule foreach --recursive git reset --hard master But still the end result is that git has marked each submodule as 'dirty' and needing to commit. Anybody have any ideas how I straighten out this mess ?

3 4

build of 1.56.0 has no tools/build/v2
by Roger Martin 12 Aug '14

12 Aug '14

Hi, The build has changed or the docs http://www.boost.org/doc/libs/1_56_0/more/getting_started/unix-variants.htm… are correct and tools/build/v2 is missing There is a bootstrap.sh in tools/build and I used it successfully And then built the libs I needed so I'm guessing the docs on getting started aged slightly. I didn't need tools/build/v2/user-config.jam this time but do see the bootstrap build of bjam produces a ./build.tool/share/boost-build/example/user-config.jam For new users maybe a little cleanup on getting started would be helpful

1 0

[git][regression] Regression is not a submodule
by Adam Wulkiewicz 12 Aug '14

12 Aug '14

Hi, I noticed that Regression isn't setup properly as a submodule of modular boost unlike other tools. It isn't present on a list displayed with: git submodule status nor in .gitmodules $ grep 'tools' .gitmodules path = tools/build path = tools/bcp path = tools/inspect path = tools/boostbook path = tools/quickbook path = tools/litre path = tools/auto_index path = tools/boostdep There is a module Regression: https://github.com/boostorg/regression/tree/develop and there is also a non-submodule directory in boostorg: https://github.com/boostorg/boost/tree/develop/tools/regression Unlike the former, the latter seems to be actively developed. I assume that the code should be contributed to the boostorg directly? Is there a reason for this? Regards, Adam

2 1

[interprocess] atomic_write32 on GCC/x86/x68_64 lacks memory barrier
by Lars Hagström 12 Aug '14

12 Aug '14

Hi! In a piece of legacy code I've had a few uses of the atomic operations inside Boost.Interprocess (yes, I know they're internal, but I had no other choice at the time, so sue me :-). I've been debugging a thread synchronization issue which ended up in me actually looking for a problem inside interprocess, and I believe that I found the error. The atomic_write32 function, when running gcc on intel platforms does not have a memory barrier, which causes my threads to not see changes that they should see. A little bit of googling gave me the following link http://boost.2283326.n4.nabble.com/interprocess-atomic-write32-td4173289.ht…, which discusses exactly this issue. I've now fixed my code to use Boost.Atomic instead of relying on boost interprocess internals, so I'm good, but I worry that the issue might affect boost.interprocess as well. So I propose that atomic_write32 should be implemented using atomic_cas32. Or indeed that Boost.Atomic should be used instead, which is more work, obviously. Thoughts? /Lars

5 20

[1.56] Sorry but no PDF doc build (build script has been broken)
by John Maddock 11 Aug '14

11 Aug '14

Sorry folks, but as things stand there will be no PDF build of the docs for 1.56 as the build script appears to be hopelessly broken :-( Each time I fix one Boost.Build error it just leads to another, and frankly at present I have neither time nor inclination to keep tracking these down. If anyone wants to experience some pain then trying to invoke bjam in /doc/pdf/ will give you an idea of some of the issues. Regards, John.

6 7

Re: [boost] [multi_index]: Migration of code to VS12 does not compile anymore
by Brian Wood 11 Aug '14

11 Aug '14

Johannes Brunen writes: >Hello, > > > I'm porting some code fromVS10 to the VS12 compiler on windows. I have a >problem compiling code like the following: Clang didn't like the code either: clang++ -c -I ../boost-1_56_0_b1/ mi.cc mi.cc:21:35: error: use 'template' keyword to treat 'nth_index' as a dependent template name typedef typename container_t::template nth_index<0>::type sequence_index_t; ^ 1 error generated. -- Brian Ebenezer Enterprises - So far G-d has helped us. http://webEbenezer.net

1 0

[multi_index]: Migration of code to VS12 does not compile anymore
by Johannes Brunen 11 Aug '14

11 Aug '14

Hello, I'm porting some code fromVS10 to the VS12 compiler on windows. I have a problem compiling code like the following: //Test.cpp #include <boost/multi_index_container.hpp> #include <boost/multi_index/random_access_index.hpp> #include <boost/multi_index/hashed_index.hpp> #include <boost/multi_index/identity.hpp> template<typename T> class test { public: typedef typename boost::multi_index_container < T*, boost::multi_index::indexed_by < boost::multi_index::random_access<>, boost::multi_index::hashed_non_unique < boost::multi_index::identity<T*> > > > container_t; typedef typename container_t::nth_index<0>::type sequence_index_t; }; This does not compile and gives the following error message: 1> Test.cpp 1>D:\test\Test.cpp(18): error C2059: syntax error : '<' 1> D:\test\Test.cpp(19) : see reference to class template instantiation 'test<T>' being compiled 1>D:\test\Test.cpp(18): error C2238: unexpected token(s) preceding ';' I'm unable to find the reason for this error. Is it a compiler error, or is something wrong with my declaration? Regards, Johannes

2 1

Missing <boost/detail/endian.hpp>
by Edward Diener 11 Aug '14

11 Aug '14

I am not seeing a <boost/detail/endian.hpp> after pulling the latest 'master' and pulling all the submodules. What have I done wrong ?

2 1

Showstopper for Boost 1.56?
by Niall Douglas 10 Aug '14

10 Aug '14

Is anyone else seeing this warnings spew on Boost 1.56 beta when compiled with clang 3.4? https://ci.nedprod.com/view/Boost.AFIO/job/Boost.AFIO%20Build%20POSIX_ Linux64_clang%203.4/11/consoleFull GCC 4.8 produces no such spew. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

10 39

Boost 1.56.0 has been released
by Marshall Clow 09 Aug '14

09 Aug '14

Release 1.56.0 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 one new library and numerous enhancements and bug fixes for existing libraries. === Modularization === Boost version control has migrated to a system using git submodules. This shouldn't make too much of a difference to users, although the directory structure is now a bit different. Parts of some libraries have been moved into different modules, and several new modules have been extracted from existing code. All header paths should remain the same. The new modules are: • Assert: Customizable assert macros. Maintained by Peter Dimov. • Core: Core utilities used by other libraries, with minimal dependencies. Maintained by Peter Dimov, Glen Fernandes and Andrey Semashev. • Lexical_Cast: General literal text conversions, such as an int represented a string, or vice-versa, from Kevlin Henney. • Throw_Exception: A common infrastructure for throwing exceptions from Boost libraries, from Emil Dotchevski. • Winapi: Windows API declarations without <windows.h>, for internal Boost use. === New Libraries === • Align: Memory alignment functions, allocators, and adaptors, from Glen Fernandes. • Type_Index: Runtime/Compile time copyable type info, from Antony Polukhin. For details, including download links, see http://www.boost.org/users/news/version_1.56.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.56.0/ To install this release on your system, see http://www.boost.org/doc/libs/release/more/getting_started/index.html Thanks, --The Boost release team Vladimir Prus Rene Rivera Marshall Clow Eric Niebler Daniel James Beman Dawes

8 7

[config] Macro for initializer-list literals?
by Peter Dimov 09 Aug '14

09 Aug '14

We have BOOST_NO_CXX11_HDR_INITIALIZER_LIST, which tells us whether we can #include <initializer_list> and use std::initializer_list; we also have BOOST_NO_CXX11_UNIFIED_INITIALIZATION_SYNTAX, which tells us whether we can use X{ 1, 2 }, or X x{ 1, 2}. But we don't have a macro that tells us whether this: struct X { int a, b; }; void f( X x ) { } int main() { f( { 1, 2 } ); } is supported. This is a problem for http://www.boost.org/development/tests/develop/developer/output/Sandia-inte… because the test is guarded by BOOST_NO_CXX11_UNIFIED_INITIALIZATION_SYNTAX: https://github.com/boostorg/smart_ptr/blob/develop/test/allocate_shared_arr… and this macro is not set for Intel 13.1 in C++0x mode. Presumably the compiler allows braced initialization, but not braced literals.

1 0

[1.56.0] Release candidates available
by Marshall Clow 08 Aug '14

08 Aug '14

Release candidate files for 1.65.0 are available at http://boost.cowic.de/rc/ 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. This helps ensure the candidates build OK before we push them out to SourceForge. The files (and associated md5s) are: MD5 (boost_1_56_0_rc1.7z) = 0ac22b92b24209286d48e4c41925cd9f MD5 (boost_1_56_0_rc1.tar.bz2) = 5b5bfa99244b1ac5737323decceb19c2 MD5 (boost_1_56_0_rc1.tar.gz) = 2047cdd4e09cda34e7f10fec0f821175 MD5 (boost_1_56_0_rc1.zip) = 0c544f6acc85550b15cdc9221f2ac0c9 Thanks! -- The release managers

13 23

A quieter clang build
by Marshall Clow 08 Aug '14

08 Aug '14

I added the following lines to my user-config.jam: using clang-darwin : noC99W : "/usr/bin/clang++" : <cxxflags>"-Wno-c99-extensions -Wno-variadic-macros" ; and then built the 1.56.0 release with "toolset=clang-darwin-NoC99W", and lo! there were a *sane* amount of warnings. Just a quick tip for people drowning under the warnings. — Marshall P.S. I’m leaving for vacation this afternoon, but would like to pick this back up when I return.

1 0

Regression testing unobservable behavior?
by Beman Dawes 08 Aug '14

08 Aug '14

Certain library function errors are difficult to regression test because it is not obvious how to observe their behavior in a test framework. Examples include: 1) Selection of correct overload or template specialization when the only difference in effect is a performance enhancement. 2) Verification that BOOST_ASSERT fires when a precondition is violated. 3) Verification that I/O and other operating system API errors are handled correctly. 4) More generally, something occurs in a function under test that is hard to observe but needs to be verified. How do other boost developers address these regression testing needs? It seems to me all of the examples can be solved by creating some form of back channel (or channels) to pass information between caller and callee functions. All require getting additional information from a function after it is called. (3) also requires passing additional information to a function when it is called. An ideal solution requires: * Works in the existing Boost regression test framework. So much the better if it works in other test frameworks. * Does not violate the ODR or depend on undefined behavior. * Does not alter the interface of the function under test. * Does not generate any code except when the function is actually being tested. * Does not require that each test case be run as a separate program. * Works even if the function under test is noexcept. * Is lightweight, utterly reliable, and has few if any dependencies beyond those already present. --Beman

3 5

Error Handling issue in NonCopyable Interface
by John Pallino 08 Aug '14

08 Aug '14

Hello, I am having error handling issues that is in regards to the NonCopyable Interface library. Here is the source code: #include <boost/noncopyable.hpp> #include <iostream> class A : public boost::noncopyable { public: A() { std::cout << "In A \n" << std::endl; } class AnError {}; void Func() { if () //error condition throw AnError(); } }; int main() { try { A object1; A object2(object1); object1 = object2; } catch (A::AnError) { //tell user about error. } return 0; } } So far, I have tried on the forums in CPlusPlus.com and MSDN, but no responses. Since that Boost.org has created and authored the NonCopyable.hpp library, I would like to get some assistance. Can anybody give me some solutions on how to suppress any compilation errors? Thanks in advance. Email me back at the Cc: if you have any answers or comments with detailed information and examples. John P.

2 1