August 2014 - Boost - lists.preview.boost.org

[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