- Boost - lists.preview.boost.org

[meta] Hidden libraries.
by Daniel James 04 Jul '16

04 Jul '16

I just noticed that 'detail' and 'winapi' have started turning up in the library lists because they've added metadata files. We've always hidden these libraries in the past, so I'm thinking of adding an extra field to mark them as private/hidden libraries. Probably just something like: { "key": "detail", "name": "Detail", "private": true /* the rest.... */ } Any opinions?

4 4

[release] please add fiber to master
by Oliver Kowalke 03 Jul '16

03 Jul '16

Hello admins, I'd like to ask you to add boost.fiber to the master branch so that it will become part of the next boost release (1.62). thank you in advance, Oliver

3 7

What kind of algorithms/data structures can enter in Boost
by Зайцев Александр 03 Jul '16

03 Jul '16

Hello. I am interested in developing data structures and some algorithms in Boost library. But one of the requierement for library is: "The library should be generally useful". What does it mean? I think, that i can add to the library some more data structures: suffix tree/array/automata, palindromic tree, modifications of stack/queue for getting min/max with O(1), Aho–Corasick(maybe it's algo already exist in Boost Library), maybe something else (kd-tree, for example). And algortihms: Manacker's algo for calculating palindromes number, Longest increasing subsequence, palindromic check. There are many algorithms, which i can implement to the Boost library. Also Boost.Math versus GNU MP library is very simple. In GNU MP there are many useful features. And i don't know? we need to provide these features to the Boost.Math or not. Ok, Who can explain me, what algorithms of those that i mentioned, is generally useful? What is useful for Boost, and what is useless? Thanks. -- Best regards, Zaitsev Alexander

3 4

defect macro for thread_local?
by Oliver Kowalke 02 Jul '16

02 Jul '16

Hi, does boost provide a defect macro for thread_local (like BOOST_NO_CXX11_THREAD_LOCAL)? I couldn't find something similar int the boost macro reference. The macro would be helpful together with the feature-check to exclude compilers, that do not support the keyword thread_local (as gcc-4.7. and apple's compiler), from unit-tests. Oliver

4 7

[1.61.0] building with Clang and c++11
by Richard Hadsell 02 Jul '16

02 Jul '16

I have downloaded 1.61.0 and want to build it with Clang. This is in my user-config: using clang : 3.5.0 : /netDISKS/master/netmt/LINUX_C65/app/clang/3.5.0/bin/clang++ : <compileflags>"-fPIC -gcc-toolchain /netDISKS/master/netmt/LINUX_C65/app/gcc/4.8.3 -Wno-overloaded-virtual -Wno-unused-function -Wno-unused-variable -Wno-c99-extensions -Wno-variadic-macros" <linkflags>"-fPIC -gcc-toolchain /netDISKS/master/netmt/LINUX_C65/app/gcc/4.8.3" ; When I build, I see warnings like these: ./boost/mpl/print.hpp:50:19: warning: in-class initialization of non-static data member is a C++11 extension [-Wc++11-extensions] const int m_x = 1 / (sizeof(T) - sizeof(T)); ^ ./boost/timer/timer.hpp:44:43: warning: 'long long' is a C++11 extension [-Wc++11-long-long] void clear() { wall = user = system = 0LL; } ^ ./boost/regex/v4/instances.hpp:124:34: warning: unknown warning group '-Wkeyword-macro', ignored [-Wunknown-pragmas] #pragma clang diagnostic ignored "-Wkeyword-macro" ^ When I add '-std=c++11' to the <compileflags> and <linkflags>, I get errors and warnings like these: clang-linux.compile.c.without-pth bin.v2/libs/container/build/clang-linux-3.5.0/release/instruction-set-core2/link-static/threading-multi/alloc_lib.o error: invalid argument '-std=c++11' not allowed with 'C/ObjC' "/netDISKS/master/netmt/LINUX_C65/app/clang/3.5.0/bin/clang++" -c -x c -O3 -Wno-inline -Wall -std=c++11 -fPIC -gcc-toolchain /netDISKS/master/netmt/LINUX_C65/app/gcc/4.8.3 -Wno-overloaded-virtual -Wno-unused-function -Wno-unused-variable -Wno-c99-extensions -Wno-variadic-macros -march=core2 -pthread -m64 -DBOOST_ALL_NO_LIB=1 -DBOOST_CONTAINER_STATIC_LINK=1 -DNDEBUG -I"." -c -o "bin.v2/libs/container/build/clang-linux-3.5.0/release/instruction-set-core2/link-static/threading-multi/alloc_lib.o" "libs/container/src/alloc_lib.c" libs/locale/src/shared/localization_backend.cpp:54:22: warning: 'auto_ptr' is deprecated [-Wdeprecated-declarations] std::auto_ptr<localization_backend> res(new actual_backend(backends,default_backends_)); ^ ./boost/regex/v4/instances.hpp:124:34: warning: unknown warning group '-Wkeyword-macro', ignored [-Wunknown-pragmas] #pragma clang diagnostic ignored "-Wkeyword-macro" ^ What options do I need to add or remove to build and use boost with no errors and as few warnings as possible? -- Dick Hadsell 203-992-6320 Fax: 203-992-6001 Reply-to: hadsell(a)blueskystudios.com Blue Sky Studios http://www.blueskystudios.com 1 American Lane, Greenwich, CT 06831-2560

5 6

New library? CallableTraits
by Barrett Adair 01 Jul '16

01 Jul '16

I posted about this a month ago, but I did not receive much response. Since then, I added an extended example use case, and I added a documentation section [1] that compares CallableTraits and Boost.FunctionTypes. I received some positive feedback this week in Aspen, and r/cpp also seemed to respond well [2], so I thought I'd give this another shot. Here are my questions for you: 1. Is there any interest in reviewing a future version of this for inclusion in Boost? 2. If so, does this belong in its own library, or should it be incorporated into Boost.TypeTraits or something similar? 3. What you like to see added, removed, renamed, or redesigned? I'd say CallableTraits is about 85% finished. Here's what's left: * Add INVOKE semantics to a couple of things for consistency (arity, etc) * Remove unused/undocumented code * Account for transaction_safe and C++17 noexcept * Finish/test the calling convention features * Finish/update the reference documentation * Write even more tests Cheers, Barrett [1] http://badair.github.io/callable_traits/doc/html/index.html#callable_traits… [2] https://www.reddit.com/r/cpp/comments/4ffmfs/callabletraits_never_write_ano… GitHub: https://github.com/badair/callable_traits Documentation from the top: http://badair.github.io/callable_traits/doc/html/index.html (reference section under construction)

5 11

[build] Running 1 per N tests
by Adam Wulkiewicz 30 Jun '16

30 Jun '16

Hi, At Boost.Geometry we're using CircleCI for testing. They allow to run the tests concurently on N virtual machines. I'd like to alter my script to automatically redistribute the tests evenly across all of the machines, i.e. to run 1/N of the tests on each machine. The problem is that at Boost.Geometry we have a lot of nested project directories, i.e. b2 executed for some upper directory runs the tests in the test-suite in this directory and then follows nested projects defined by build-project directives, so runs the tests recursively. So e.g. if b2 was executed on some virtual machine for the most-top-level directory all of the tests would be built anyway. Do you have an idea how this could be solved without altering the tests structure? Is it currently somehow possible (though AFAIK it isn't) or would be possible to implement options allowing to e.g.: - run b2 only for a certain directory/Jamfile, e.g. --non-recursive - ignore arbitrary Jamfile directive, e.g. --ignore-build-project - run only 1 per N tests, an option used together with -jX but running tests only for one thread, e.g. b2 -i2 -j4 running only 1 per 4 commands starting from 2nd command ? The last option would be the most convenient for me. The tests would be divided as evenly as possible. It wouldn't require to use some workarounds i.e. traversing test directories recursively and running b2 manually for them which could result in low-quality redistribution, e.g. if some directory contained many tests and other small number of tests. Regards, Adam

2 2

boost regression run.py fails with, fatal: Not a git repository
by Blower, Melanie 29 Jun '16

29 Jun '16

I'm trying to run.py on develop to report results with the Intel compiler. The script I use first downloads run.py. The git is failing partway through with this message Cloning into 'tools/quickbook'... Submodule path 'tools/quickbook': checked out 'c7cb99ac029593024f3f31a1ab2503820f1300d5' # Cleaning up "/localext3/mblower/sandbox/_try_dev/boost_root/bin" directory ... # Cleaning up "/localext3/mblower/sandbox/_try_dev/boost_root/bin.v2" directory ... # Cleaning up "/localext3/mblower/sandbox/_try_dev/results" directory ... # Getting sources (2016-06-29T12:24:07Z)... # Executing GIT command: /localext3/mblower/sandbox/_try_dev/boost_root> git submodule foreach "cd $toplevel && git submodule deinit $path" Entering 'libs/accumulators' fatal: Not a git repository (or any parent up to mount point /localext3) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). Stopping at 'libs/accumulators'; script returned non-zero status. # git_source_checkout failed with message "GIT command "git submodule foreach "cd $toplevel && git submodule deinit $path"" failed with code 256" I'm using a new server, the "master" results completed successfully last night. There's plenty of disk space. Any ideas?

2 1

[boost-git] fiber not contained?
by Oliver Kowalke 29 Jun '16

29 Jun '16

Hi, I was asked several times why boost.fiber is not contained if boost's git-repo is cloned with git clone --recursive http://github.com/boostorg/boost.git. I'm wondering because boost.fiber is already included in the regression tests (master/develop). Oliver

4 8

Attention library authors.. Library requirements testing is now active.
by Rene Rivera 29 Jun '16

29 Jun '16

As part of continued efforts to move testing to CI, to facilitate release management, and to provide more information to authors I've now implemented some testing changes: 1. Most libraries are now tested automatically if they have a usable test directory. There are still libraries that do not follow the requirements of having all their tests in just the single test directory. You can see which ones those are here < https://github.com/boostorg/boost/blob/develop/status/Jamfile.v2#L101>. Library authors should IMMEDIATELY make changes to their test/Jamfile's to follow the library requirements for testing. Before the next release I plan to blindly remove that custom list of extra test targets. 2. Most structure library requirements are now checked both in the regular full testing and in the CI testing. I've implemented a script to check for most of the library directory structure and integration requirements. The script runs as an additional CI job, currently in Travis. Here's one of those jobs < https://travis-ci.org/boostorg/boost/jobs/137506433>. At the moment it reports 17 libraries as having errors. There are also some warnings, i.e. not requirement violations but just some stuff that may be wrong. The script also runs as part of the general full testing and any problems are reported in each library's results as a single entry at the top of the tables. Here's how one of the test failures looks like < http://tinyurl.com/zbe9gal> [1] [2]. It would be great if library authors address those errors in some form ASAP. I know that for some of those reported libraries there will need to be some discussions as to how to best address the errors. Feel free to start additional threads for those as needed. [1] < http://www.boost.org/development/tests/develop/developer/output/teeks99-09f… > [2] Note there are currently some false failures in this aspect from a build system "bug". The bug is already fixed but tests will take some time to cycle to reflect the bug fix. -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

11 23