- Boost - lists.preview.boost.org

[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

boost serialization and new archive types
by Robert Ramey 13 May '15

13 May '15

I'm here at C++Now and some have approached me about some enhancements to the serialization library. Specifically there is interest in moving the implementation of XML serialization to the latest C++11 of boost. I've gone them one better - While they're at it, how about including JSON and YAML as well? I would be happy to meet with anyone and everyone interested in this while here at the conference. I'm commited to all the operations meetings 12:45 so that time would be out - I'm flexible. Robert Ramey

2 1

Windows XP support survey
by Niall Douglas 13 May '15

13 May '15

The Boost SC suggested I ask about Microsoft Windows XP support in Boost libraries here, so I'd appreciate if library maintainers could state: 1. If they still support Microsoft Windows XP i.e. actively do not use APIs not supported by XP. And if SP3 is the only service pack supported, or if any XP is okay. 2. Whether they regularly test their libraries on a Windows XP machine to ensure their libraries work there. 3. Their personal opinion about when would be best to drop mandatory Microsoft Windows XP support. Individual library maintainers can of course choose to keep supporting it. As we all know, Microsoft Windows XP is no longer supported by Microsoft as of April 2014, however a widely available registry tweak reenables support and updates until 2019. However Visual Studio 2012 cannot run on XP, nor by default can produce binaries which execute on XP, so testing and developing for XP compatibility is going to become increasingly difficult. It may become wise to announce a date that XP support guarantees will be dropped, and any users needing XP support must remain on an older Boost version and/or make use of Boost modularity to mux their own Boost distro. One big reason for thinking about this is that the first C++ 11 mandatory Boost libraries are just around the corner, and they of course need VS2013 or even VS2015 and so therefore cannot promise Windows XP support. There are also a number of post-XP APIs the assumption of which would make some library authors very pleased. For example, I would assume any Boost.Thread v5 would use the Vista only condvar APIs as one can then skip emulating condvars with win32 semaphores which would be an enormous saving of code complexity. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

14 41

Re: [boost] Interest in a container which can hold multiple data types?
by James Armstrong 12 May '15

12 May '15

You're correct in that a vector<boost::any> can achieve the same thing, and that would probably be the better way to implement this internally. I guess the proposal would be to provide the container interface to give some data modification functions and iterators which iterate over only a given type and such. That way there would be a standardized container with methods to deal with the data in a type specific way. -- James Armstrong

5 17

Re: [boost] [boost.org website] Incorrect links on Boost website
by Marek Kurdej 12 May '15

12 May '15

> > From: Daniel James <dnljms(a)gmail.com> > To: boost(a)lists.boost.org > Cc: > Date: Sun, 10 May 2015 20:04:10 +0100 > Subject: Re: [boost] [boost.org website] Incorrect links on Boost website > On 10 May 2015 at 16:10, Michael Levine <shmuel.levine(a)gmail.com> wrote: > > I was browsing through the Boost website this morning and the links on > the > > right sidebar caught my attention. It appears that there is a duplicate > > entry for "coding guidelines for constant integral expressions", under > > Development / Requirements and Guidelines. The first of these links > points > > to the correct page. The second links to a page regarding library > > metadata. I'm not sure who, exactly, to contact for this, so I figured > this > > list would be the most appropriate means to have this addressed. > It's fixed now. Hi, Along these lines, I have spotted a curious detail on 3 Boost mailing lists. The logos (C++ Boost / Boost C++ libraries) point to web pages that are not affiliated in any way to boost. The concerned lists are: - http://lists.boost.org/boost-docs/ points to www [dot] boost [dot] com - http://lists.boost.org/boost-testing/ points to www [dot] boost [dot] com - http://lists.boost.org/geometry/ points to www [dot] osl [dot] iu [dot] edu There are maybe more wrong links that I haven't caught. Can it be fixed, please?. Regards, Marek Kurdej

2 1

A summary of testing with sanitizers
by Ben Pope 12 May '15

12 May '15

Hello all. Now that I've finally managed to get the sanitizers all working properly (correctly linking against the sanitized runtimes) I'd like to present a summary of its output (which I hope doesn't wrap). I would like to point out that the sanitizers may not be able to completely determine whether the code is correct or not, perhaps merely that they do not understand it (inline asm, etc.), and it also looks like some of the errors are in libc++, not Boost. If the code is determined to be correct, I could add entries to the blacklist to make sure the sanitizers ignore the output, but I would prefer not to. Perhaps a better approach would be to mark up the code so that all users of sanitizers benefit, rather than just the test matrix. Suggestions on how to reduce this output (I hope to publish summaries on a regular basis) in the best possible way are welcomed. I've ordered the output by the number of test failures that result from a particular complaint as determined by the command below: cat bjam.log | grep SUMMARY | sort | uniq -c | sort -n -r Count Warning 89 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/detail/shared_count.hpp:449:49 in boost::detail::shared_count::shared_count(boost::detail::shared_count const&) 70 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/shared_ptr.hpp:392:63 in boost::shared_ptr<boost::detail::thread_data_base>::shared_ptr(boost::shared_ptr<boost::detail::thread_data_base> const&) 69 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/detail/sp_counted_base_clang.hpp:31:5 in boost::detail::atomic_increment(int _Atomic*) 44 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/shared_ptr.hpp:392:57 in boost::shared_ptr<boost::detail::thread_data_base>::shared_ptr(boost::shared_ptr<boost::detail::thread_data_base> const&) 44 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/detail/shared_count.hpp:449:43 in boost::detail::shared_count::shared_count(boost::detail::shared_count const&) 33 SUMMARY: ThreadSanitizer: data race on vptr (ctor/dtor vs virtual call) /home/ben/development/boost/test/build/boost_root/status/../libs/thread/src/pthread/thread.cpp:168:21 in boost::(anonymous namespace)::thread_proxy(void*) 22 SUMMARY: ThreadSanitizer: data race (/home/ben/development/llvm/trunk/build/release/projects/compiler-rt/lib/tsan/libcxx_tsan/lib/libc++.so.1+0x43962) in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::assign(char const*, unsigned long) 21 SUMMARY: ThreadSanitizer: data race (/home/ben/development/llvm/trunk/build/release/projects/compiler-rt/lib/tsan/libcxx_tsan/lib/libc++.so.1+0x43991) in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::assign(char const*, unsigned long) 21 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/test/utils/basic_cstring/basic_cstring.hpp:384:13 in boost::unit_test::basic_cstring<char const>::operator=(boost::unit_test::basic_cstring<char const> const&) 21 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/test/utils/basic_cstring/basic_cstring.hpp:383:13 in boost::unit_test::basic_cstring<char const>::operator=(boost::unit_test::basic_cstring<char const> const&) 21 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/test/impl/unit_test_log.ipp:118:41 in boost::unit_test::(anonymous namespace)::unit_test_log_impl::set_checkpoint(boost::unit_test::basic_cstring<char const>, unsigned long, boost::unit_test::basic_cstring<char const>) 18 SUMMARY: ThreadSanitizer: data race /usr/local/bin/../include/c++/v1/ios:499:12 in std::__1::ios_base::width() const 15 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:331:10 in boost::multiprecision::backends::detail::gmp_float_imp<50u>::~gmp_float_imp() 12 SUMMARY: ThreadSanitizer: heap-use-after-free /home/ben/development/boost/test/build/boost_root/status/../boost/chrono/time_point.hpp:196:20 in boost::chrono::time_point<boost::chrono::steady_clock, boost::chrono::duration<long, boost::ratio<1l, 1000000000l> > >::time_since_epoch() const 11 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/detail/invoke.hpp:134:14 in _ZN5boost6detail6invokeIPFvNS_7promiseIRiEEEJS4_EEEDTclclsr5boostE7forwardIT_Efp_Espclsr5boostE7forwardIT0_Efp0_EEEOS7_DpOS8_ 11 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/shared_ptr.hpp:392:63 in boost::shared_ptr<boost::detail::shared_state<int&> >::shared_ptr(boost::shared_ptr<boost::detail::shared_state<int&> > const&) 10 SUMMARY: MemorySanitizer: use-of-uninitialized-value /usr/local/bin/../include/c++/v1/string:640:63 in std::__1::char_traits<char>::length(char const*) 10 SUMMARY: AddressSanitizer: 4 byte(s) leaked in 1 allocation(s). 8 SUMMARY: AddressSanitizer: 552 byte(s) leaked in 23 allocation(s). 7 SUMMARY: ThreadSanitizer: data race /usr/local/bin/../include/c++/v1/ios:742:54 in std::__1::basic_ios<char, std::__1::char_traits<char> >::fill() const 6 SUMMARY: ThreadSanitizer: data race /usr/local/bin/../include/c++/v1/ios:437:12 in std::__1::ios_base::flags() const 6 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/detail/invoke.hpp:134:14 in _ZN5boost6detail6invokeIPFvNS_7promiseIiEEEJS3_EEEDTclclsr5boostE7forwardIT_Efp_Espclsr5boostE7forwardIT0_Efp0_EEEOS6_DpOS7_ 6 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/shared_ptr.hpp:392:63 in boost::shared_ptr<boost::detail::shared_state<int> >::shared_ptr(boost::shared_ptr<boost::detail::shared_state<int> > const&) 5 SUMMARY: ThreadSanitizer: data race /usr/local/bin/../include/c++/v1/map:1006:47 in std::__1::map<void const*, boost::detail::tss_data_node, std::__1::less<void const*>, std::__1::allocator<std::__1::pair<void const* const, boost::detail::tss_data_node> > >::empty() const 5 SUMMARY: ThreadSanitizer: data race /usr/local/bin/../include/c++/v1/ios:506:22 in std::__1::ios_base::width(long) 5 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/src/pthread/thread.cpp:85:78 in boost::detail::(anonymous namespace)::tls_destructor(void*) 5 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/serialization/test/test_shared_ptr.cpp:123:5 in void save_and_load<boost::shared_ptr<A> >(boost::shared_ptr<A>&) 5 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/serialization/test/test_shared_ptr_132.cpp:117:5 in void save_and_load<boost_132::shared_ptr<A> >(boost_132::shared_ptr<A> const&) 5 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/serialization/src/basic_iarchive.cpp:443:16 in boost::archive::detail::basic_iarchive_impl::load_pointer(boost::archive::detail::basic_iarchive&, void*&, boost::archive::detail::basic_pointer_iserializer const*, boost::archive::detail::basic_pointer_iserializer const* (*)(boost::serialization::extended_type_info const&)) 5 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/numeric/odeint/stepper/bulirsch_stoer.hpp:202:13 in boost::numeric::odeint::controlled_step_result boost::numeric::odeint::bulirsch_stoer<std::__1::vector<double, std::__1::allocator<double> >, double, std::__1::vector<double, std::__1::allocator<double> >, double, boost::numeric::odeint::range_algebra, boost::numeric::odeint::default_operations, boost::numeric::odeint::initially_resizer>::try_step<void (*)(std::__1::vector<double, std::__1::allocator<double> > const&, std::__1::vector<double, std::__1::allocator<double> >&, double), std::__1::vector<double, std::__1::allocator<double> >, std::__1::vector<double, std::__1::allocator<double> >, std::__1::vector<double, std::__1::allocator<double> > >(void (*)(std::__1::vector<double, std::__1::allocator<double> > const&, std::__1::vector<double, std::__1::allocator<double> >&, double), std::__1::vector<double, std::__1::allocator<double> > co 5 SUMMARY: AddressSanitizer: heap-use-after-free /home/ben/development/llvm/trunk/llvm/projects/compiler-rt/lib/asan/asan_interceptors.cc:403:3 in __asan_memcpy 5 SUMMARY: AddressSanitizer: 936 byte(s) leaked in 6 allocation(s). 5 SUMMARY: AddressSanitizer: 768 byte(s) leaked in 4 allocation(s). 5 SUMMARY: AddressSanitizer: 64 byte(s) leaked in 2 allocation(s). 5 SUMMARY: AddressSanitizer: 576 byte(s) leaked in 4 allocation(s). 5 SUMMARY: AddressSanitizer: 552 byte(s) leaked in 2 allocation(s). 5 SUMMARY: AddressSanitizer: 480 byte(s) leaked in 8 allocation(s). 5 SUMMARY: AddressSanitizer: 368 byte(s) leaked in 4 allocation(s). 5 SUMMARY: AddressSanitizer: 32 byte(s) leaked in 4 allocation(s). 5 SUMMARY: AddressSanitizer: 240 byte(s) leaked in 4 allocation(s). 5 SUMMARY: AddressSanitizer: 1 byte(s) leaked in 1 allocation(s). 4 SUMMARY: ThreadSanitizer: thread leak /home/ben/development/boost/test/build/boost_root/status/../libs/thread/src/pthread/thread.cpp:250:25 in boost::thread::start_thread_noexcept() 4 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/pthread/pthread_mutex_scoped_lock.hpp:24:23 in boost::pthread::pthread_mutex_scoped_lock::pthread_mutex_scoped_lock(pthread_mutex_t*) 4 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/pthread/pthread_mutex_scoped_lock.hpp:24:17 in boost::pthread::pthread_mutex_scoped_lock::pthread_mutex_scoped_lock(pthread_mutex_t*) 4 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/pthread/once_atomic.hpp:128:25 in void boost::call_once<void (&)()>(boost::once_flag&, void (&)()) 4 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/detail/thread.hpp:116:17 in boost::detail::thread_data<void (*)()>::run() 4 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/atomic/detail/atomic_template.hpp:134:22 in boost::atomics::detail::base_atomic<unsigned int, int>::compare_exchange_strong(unsigned int&, unsigned int, boost::memory_order, boost::memory_order) volatile 4 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/serialization/test/test_shared_ptr_multi_base.cpp:185:5 in void shared_weak<boost::shared_ptr<Sub>, boost::weak_ptr<Base3> >(boost::shared_ptr<Sub>&, boost::weak_ptr<Base3>&) 4 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/type_index/stl_type_index.hpp:141:40 in boost::typeindex::stl_type_index::pretty_name() const 3 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/detail/invoke.hpp:134:14 in _ZN5boost6detail6invokeIPFvNS_7promiseIvEEEJS3_EEEDTclclsr5boostE7forwardIT_Efp_Espclsr5boostE7forwardIT0_Efp0_EEEOS6_DpOS7_ 3 SUMMARY: MemorySanitizer: use-of-uninitialized-value /usr/local/bin/../include/c++/v1/string:3767:13 in bool std::__1::operator==<std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) 3 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/spirit/home/qi/numeric/detail/real_impl.hpp:295:22 in bool boost::spirit::qi::detail::real_impl<double, boost::spirit::qi::real_policies<double> >::parse<char const*, double>(char const*&, char const* const&, double&, boost::spirit::qi::real_policies<double> const&) 3 SUMMARY: MemorySanitizer: use-of-uninitialized-value /build/buildd/glibc-2.21/misc/tsearch.c:356 in tdelete 2 SUMMARY: ThreadSanitizer: data race (/home/ben/development/llvm/trunk/build/release/projects/compiler-rt/lib/tsan/libcxx_tsan/lib/libc++.so.1+0x381e2) in std::__1::__shared_weak_count::__release_shared() 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/try_join_until_pass.cpp:55:12 in G::operator()() 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/try_join_until_pass.cpp:54:5 in G::operator()() 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/detach_pass.cpp:70:5 in main 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/detach_pass.cpp:69:5 in main 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/constr/move_pass.cpp:58:55 in G::operator()(int, double) 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/asio/test/strand.cpp:91:3 in sleep_increment(boost::asio::io_service*, int*) 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/future.hpp:3377:50 in boost::packaged_task<double (int, char)>::packaged_task(boost::packaged_task<double (int, char)>&&) 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/future.hpp:3377:11 in boost::packaged_task<double (int, char)>::packaged_task(boost::packaged_task<double (int, char)>&&) 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/detail/invoke.hpp:134:14 in _ZN5boost6detail6invokeIPFvNS_13packaged_taskIFdicEEEEJS4_EEEDTclclsr5boostE7forwardIT_Efp_Espclsr5boostE7forwardIT0_Efp0_EEEOS7_DpOS8_ 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/shared_ptr.hpp:392:63 in boost::shared_ptr<boost::detail::shared_state<void> >::shared_ptr(boost::shared_ptr<boost::detail::shared_state<void> > const&) 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/shared_ptr.hpp:334:35 in boost::shared_ptr<boost::detail::task_base_shared_state<double (int, char)> >::shared_ptr() 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/detail/shared_count.hpp:114:21 in boost::detail::shared_count::shared_count() 2 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/log/utility/once_block.hpp:91:24 in boost::log::v2_mt_posix::aux::once_block_sentry::executed() const 2 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:159:10 in boost::multiprecision::backends::detail::gmp_float_imp<50u>::operator=(long) 2 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/geometry/strategies/cartesian/point_in_box.hpp:36:34 in bool boost::geometry::strategy::within::within_range::apply<double, double>(double const&, double const&, double const&) 2 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/container/vector.hpp:2774:7 in boost::container::container_detail::vec_iterator<boost::container::stable_vector_detail::node_base<void*>**, false> boost::container::vector<boost::container::stable_vector_detail::node_base<void*>*, boost::container::allocator<boost::container::stable_vector_detail::node_base<void*>*, 2u, 0u> >::priv_forward_range_insert<boost::container::container_detail::insert_value_initialized_n_proxy<boost::container::allocator<boost::container::stable_vector_detail::node_base<void*>*, 2u, 0u>, boost::container::stable_vector_detail::node_base<void*>**> >(boost::container::stable_vector_detail::node_base<void*>** const&, unsigned long, boost::container::container_detail::insert_value_initialized_n_proxy<boost::container::allocator<boost::container::stable_vector_detail::node_base<void*>*, 2u, 0u>, boost::container::stable_vector_detail::node_base<void*>**>) 2 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/container/vector.hpp:2604:11 in void boost::container::vector<MyInt, boost::container::allocator<MyInt, 2u, 6u> >::priv_push_back<MyInt>(MyInt&&) 2 SUMMARY: MemorySanitizer: use-of-uninitialized-value /build/buildd/glibc-2.21/misc/tsearch.c:320 in tfind 2 SUMMARY: AddressSanitizer: stack-buffer-overflow /home/ben/development/boost/test/build/boost_root/status/../libs/spirit/classic/test/traverse_tests.cpp:379:44 in void post_order_trace_test<boost::spirit::classic::sequence<boost::spirit::classic::chlit<char>, boost::spirit::classic::chlit<char> > >(boost::spirit::classic::sequence<boost::spirit::classic::chlit<char>, boost::spirit::classic::chlit<char> > const&, char const**, unsigned long) 2 SUMMARY: AddressSanitizer: stack-buffer-overflow /home/ben/development/boost/test/build/boost_root/status/../libs/local_function/test/return_derivative_seq.cpp:17:9 in derivative(boost::function<int (int)>&, int)::boost_local_function_auxXfunctorX17X::operator()(int) 2 SUMMARY: AddressSanitizer: 576 byte(s) leaked in 12 allocation(s). 2 SUMMARY: AddressSanitizer: 288 byte(s) leaked in 6 allocation(s). 2 SUMMARY: AddressSanitizer: 16 byte(s) leaked in 1 allocation(s). 2 SUMMARY: AddressSanitizer: 14496 byte(s) leaked in 404 allocation(s). 2 SUMMARY: AddressSanitizer: 120 byte(s) leaked in 5 allocation(s). 1 SUMMARY: ThreadSanitizer: data race /usr/local/bin/../include/c++/v1/ios:488:22 in std::__1::ios_base::precision(long) 1 SUMMARY: ThreadSanitizer: data race /usr/local/bin/../include/c++/v1/ios:444:20 in std::__1::ios_base::flags(unsigned int) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/./util.inl:106:16 in (anonymous namespace)::execution_monitor::wait() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/try_join_for_pass.cpp:55:12 in G::operator()() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/try_join_for_pass.cpp:54:5 in G::operator()() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/join_pass.cpp:56:12 in G::operator()() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/thread/test/threads/thread/members/join_pass.cpp:39:5 in G::G() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/spirit/classic/test/owi_mt_tests.cpp:93:23 in test_task<boost::spirit::classic::impl::object_with_id<tag1, unsigned long> >::increase_test_size(unsigned long) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/log/test/run/util_once_block.cpp:64:25 in once_block_flag_thread(boost::barrier&) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/log/test/run/util_once_block.cpp:112:25 in once_block_thread(boost::barrier&) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/interprocess/test/condition_test_template.hpp:83:17 in void boost::interprocess::test::condition_test_thread<boost::interprocess::interprocess_condition_any, boost::interprocess::ipcdetail::spin_mutex>(boost::interprocess::test::condition_test_data<boost::interprocess::interprocess_condition_any, boost::interprocess::ipcdetail::spin_mutex>*) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/interprocess/test/condition_test_template.hpp:321:15 in void boost::interprocess::test::do_test_condition_queue_notify_one<boost::interprocess::interprocess_condition_any, boost::interprocess::ipcdetail::spin_mutex>() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/interprocess/test/condition_test_template.hpp:282:10 in boost::interprocess::test::condition_func<boost::interprocess::interprocess_condition_any, boost::interprocess::ipcdetail::spin_mutex>::operator()() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/interprocess/test/condition_test_template.hpp:277:10 in boost::interprocess::test::condition_func<boost::interprocess::interprocess_condition_any, boost::interprocess::ipcdetail::spin_mutex>::operator()() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/atomic/test/ordering.cpp:200:40 in total_store_order_test<(boost::memory_order)0, (boost::memory_order)0>::thread2fn() 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../libs/atomic/test/atomicity.cpp:131:28 in racy_add(unsigned int volatile&, unsigned long) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/pthread/mutex.hpp:62:17 in boost::posix::pthread_mutex_lock(pthread_mutex_t*) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/future.hpp:2481:88 in boost::promise<void>::promise(boost::promise<void>&&) 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/thread/detail/invoke.hpp:134:14 in _ZN5boost6detail6invokeIPFvvEJEEEDTclclsr5boostE7forwardIT_Efp_Espclsr5boostE7forwardIT0_Efp0_EEEOS4_DpOS5_ 1 SUMMARY: ThreadSanitizer: data race /home/ben/development/boost/test/build/boost_root/status/../boost/smart_ptr/shared_ptr.hpp:663:16 in boost::shared_ptr<boost::detail::shared_state<void> >::get() const 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /usr/local/bin/../include/c++/v1/bitset:757:46 in std::__1::bitset<8ul>::bitset<char, std::__1::char_traits<char>, std::__1::allocator<char> >(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::size_type, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::size_type, char, char) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /usr/local/bin/../include/c++/v1/algorithm:1193:13 in bool std::__1::equal<boost::archive::iterators::mb_from_wchar<wchar_t const*>, char const*, std::__1::__equal_to<wchar_t, char> >(boost::archive::iterators::mb_from_wchar<wchar_t const*>, boost::archive::iterators::mb_from_wchar<wchar_t const*>, char const*, std::__1::__equal_to<wchar_t, char>) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_rational_io_mpz.test/clang-linux-3.7~msan~c14_libc++/release/test_rational_io_mpz+0x76708) in boost::multiprecision::number<boost::multiprecision::backends::gmp_rational, (boost::multiprecision::expression_template_option)1> generate_random<boost::multiprecision::number<boost::multiprecision::backends::gmp_rational, (boost::multiprecision::expression_template_option)1> >() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_miller_rabin.test/clang-linux-3.7~msan~c14_libc++/release/test_miller_rabin+0x75bbf) in void test<boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> >() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_int_io_mpz.test/clang-linux-3.7~msan~c14_libc++/release/test_int_io_mpz+0x7ca20) in boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> generate_random<boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> >() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_generic_conv.test/clang-linux-3.7~msan~c14_libc++/release/test_generic_conv+0x99138) in void boost::multiprecision::detail::generic_interconvert<boost::multiprecision::backends::gmp_int, boost::multiprecision::backends::cpp_int_backend<0u, 0u, (boost::multiprecision::cpp_integer_type)1, (boost::multiprecision::cpp_int_check_type)0, std::__1::allocator<unsigned long long> > >(boost::multiprecision::backends::gmp_int&, boost::multiprecision::backends::cpp_int_backend<0u, 0u, (boost::multiprecision::cpp_integer_type)1, (boost::multiprecision::cpp_int_check_type)0, std::__1::allocator<unsigned long long> > const&, mpl_::int_<0> const&, mpl_::int_<0> const&) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_float_io_mpf.test/clang-linux-3.7~msan~c14_libc++/release/test_float_io_mpf+0x916e9) in void test<boost::multiprecision::number<boost::multiprecision::backends::gmp_float<50u>, (boost::multiprecision::expression_template_option)1> >() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_cpp_int_3.test/clang-linux-3.7~msan~c14_libc++/release/test_cpp_int_3+0x89656) in boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> generate_random<boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> >(unsigned int) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_cpp_int_2.test/clang-linux-3.7~msan~c14_libc++/release/test_cpp_int_2+0x89246) in boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> generate_random<boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> >(unsigned int) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value (/home/ben/development/boost/test/build/results/boost/bin.v2/libs/multiprecision/test/test_cpp_int_1.test/clang-linux-3.7~msan~c14_libc++/release/test_cpp_int_1+0x95d16) in boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> generate_random<boost::multiprecision::number<boost::multiprecision::backends::gmp_int, (boost::multiprecision::expression_template_option)1> >(unsigned int) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/serialization/src/basic_xml_grammar.ipp:200:5 in boost::archive::basic_xml_grammar<char>::my_parse(std::__1::basic_istream<char, std::__1::char_traits<char> >&, boost::spirit::classic::rule<boost::spirit::classic::scanner<std::__1::__wrap_iter<char*>, boost::spirit::classic::scanner_policies<boost::spirit::classic::iteration_policy, boost::spirit::classic::match_policy, boost::spirit::classic::action_policy> >, boost::spirit::classic::nil_t, boost::spirit::classic::nil_t> const&, char) const 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/graph/test/typestr.hpp:33:29 in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > typestr<boost::undirected_graph<VertexBundle, EdgeBundle, GraphBundle> >() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/container/test/alloc_full_test.cpp:126:10 in boost::container::test::test_allocation_shrink() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/container/test/alloc_basic_test.cpp:24:7 in basic_test() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/container/bench/bench_alloc.cpp:63:13 in void allocation_timing_test<char_holder<8u> >(unsigned int, unsigned int) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../libs/config/test/limits_test.cpp:97:8 in void print_hex_val<long double>(long double, char const*) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/test/impl/test_tools.ipp:298:9 in boost::test_tools::tt_detail::report_assertion(boost::test_tools::assertion_result const&, boost::unit_test::lazy_ostream const&, boost::unit_test::basic_cstring<char const>, unsigned long, boost::test_tools::tt_detail::tool_level, boost::test_tools::tt_detail::check_type, unsigned long, ...) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/spirit/home/qi/numeric/detail/real_impl.hpp:295:22 in bool boost::spirit::qi::detail::real_impl<double, boost::spirit::qi::ureal_policies<double> >::parse<char const*, double>(char const*&, char const* const&, double&, boost::spirit::qi::ureal_policies<double> const&) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/spirit/home/qi/numeric/detail/real_impl.hpp:295:22 in bool boost::spirit::qi::detail::real_impl<double, boost::spirit::qi::strict_real_policies<double> >::parse<char const*, double>(char const*&, char const* const&, double&, boost::spirit::qi::strict_real_policies<double> const&) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/spirit/home/qi/numeric/detail/real_impl.hpp:295:22 in bool boost::spirit::qi::detail::real_impl<double, boost::spirit::qi::real_policies<double> >::parse<std::__1::__wrap_iter<char*>, double>(std::__1::__wrap_iter<char*>&, std::__1::__wrap_iter<char*> const&, double&, boost::spirit::qi::real_policies<double> const&) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/numeric/odeint/stepper/bulirsch_stoer.hpp:202:13 in boost::numeric::odeint::controlled_step_result boost::numeric::odeint::bulirsch_stoer<boost::array<double, 3ul>, double, boost::array<double, 3ul>, double, boost::numeric::odeint::array_algebra, boost::numeric::odeint::default_operations, boost::numeric::odeint::initially_resizer>::try_step<lorenz, boost::array<double, 3ul>, boost::array<double, 3ul>, boost::array<double, 3ul> >(lorenz, boost::array<double, 3ul> const&, boost::array<double, 3ul> const&, double&, boost::array<double, 3ul>&, double&) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/numeric/odeint/iterator/impl/adaptive_iterator_impl.hpp:105:17 in boost::numeric::odeint::adaptive_iterator_impl<boost::numeric::odeint::adaptive_iterator<boost::numeric::odeint::dummy_controlled_stepper, empty_system, boost::array<double, 1ul>, boost::numeric::odeint::controlled_stepper_tag>, boost::numeric::odeint::dummy_controlled_stepper, empty_system, boost::array<double, 1ul>, boost::numeric::odeint::detail::ode_state_iterator_tag, boost::numeric::odeint::controlled_stepper_tag>::increment() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:368:7 in boost::multiprecision::backends::detail::gmp_float_imp<0u>::data() const 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:331:10 in boost::multiprecision::backends::detail::gmp_float_imp<25u>::~gmp_float_imp() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:331:10 in boost::multiprecision::backends::detail::gmp_float_imp<100u>::~gmp_float_imp() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:234:7 in boost::multiprecision::backends::detail::gmp_float_imp<0u>::str(long, unsigned int) const 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:1932:7 in boost::multiprecision::backends::gmp_rational::str(long, unsigned int) const 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:1827:10 in boost::multiprecision::backends::gmp_rational::operator=(unsigned long) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:152:10 in boost::multiprecision::backends::detail::gmp_float_imp<50u>::operator=(unsigned long) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:152:10 in boost::multiprecision::backends::detail::gmp_float_imp<2000u>::operator=(unsigned long) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:152:10 in boost::multiprecision::backends::detail::gmp_float_imp<0u>::operator=(unsigned long) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:1226:7 in boost::multiprecision::backends::gmp_int::str(long, unsigned int) const 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:1100:10 in boost::multiprecision::backends::gmp_int::operator=(long) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/multiprecision/gmp.hpp:1093:10 in boost::multiprecision::backends::gmp_int::operator=(unsigned long) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/graph/boykov_kolmogorov_max_flow.hpp:471:22 in boost::detail::bk_max_flow<boost::adjacency_list<boost::vecS, boost::vecS, boost::directedS, Node<boost::detail::edge_desc_impl<boost::directed_tag, unsigned long> >, Link<boost::detail::edge_desc_impl<boost::directed_tag, unsigned long> >, boost::no_property, boost::listS>, boost::adj_list_edge_property_map<boost::directed_tag, long, long&, unsigned long, Link<boost::detail::edge_desc_impl<boost::directed_tag, unsigned long> >, long Link<boost::detail::edge_desc_impl<boost::directed_tag, unsigned long> >::*>, boost::adj_list_edge_property_map<boost::directed_tag, long, long&, unsigned long, Link<boost::detail::edge_desc_impl<boost::directed_tag, unsigned long> >, long Link<boost::detail::edge_desc_impl<boost::directed_tag, unsigned long> >::*>, boost::adj_list_edge_property_map<boost::directed_tag, boost::detail::edge_desc_impl<boost::directed_ 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/gil/color_base_algorithm.hpp:237:60 in bool boost::gil::detail::element_recursion<2>::static_equal<boost::gil::bit_aligned_pixel_reference<unsigned char, boost::mpl::vector3_c<int, 1, 2, 1>, boost::gil::layout<boost::mpl::vector3<boost::gil::red_t, boost::gil::green_t, boost::gil::blue_t>, boost::mpl::vector3_c<int, 2, 1, 0> >, true>, boost::gil::bit_aligned_pixel_reference<unsigned char, boost::mpl::vector3_c<int, 1, 2, 1>, boost::gil::layout<boost::mpl::vector3<boost::gil::red_t, boost::gil::green_t, boost::gil::blue_t>, boost::mpl::range_c<int, 0, 3> >, true> >(boost::gil::bit_aligned_pixel_reference<unsigned char, boost::mpl::vector3_c<int, 1, 2, 1>, boost::gil::layout<boost::mpl::vector3<boost::gil::red_t, boost::gil::green_t, boost::gil::blue_t>, boost::mpl::vector3_c<int, 2, 1, 0> >, true> const&, boost::gil::bit_aligned_pixel_reference<unsigned char, boost::mpl::vector3_c<int, 1, 2, 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/context/execution_context.hpp:115:17 in boost::context::execution_context::activation_record::resume(bool) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/container/vector.hpp:457:10 in boost::container::container_detail::vector_alloc_holder<boost::container::allocator<int, 2u, 0u>, boost::move_detail::integral_constant<unsigned int, 2u> >::~vector_alloc_holder() 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/container/vector.hpp:2774:7 in boost::container::container_detail::vec_iterator<int*, false> boost::container::vector<int, boost::container::allocator<int, 2u, 0u> >::priv_forward_range_insert<boost::container::container_detail::insert_move_proxy<boost::container::allocator<int, 2u, 0u>, int*> >(int* const&, unsigned long, boost::container::container_detail::insert_move_proxy<boost::container::allocator<int, 2u, 0u>, int*>) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/container/vector.hpp:2774:7 in boost::container::container_detail::vec_iterator<boost::container::container_detail::pair<int, int>*, false> boost::container::vector<boost::container::container_detail::pair<int, int>, boost::container::allocator<boost::container::container_detail::pair<int, int>, 2u, 0u> >::priv_forward_range_insert<boost::container::container_detail::insert_move_proxy<boost::container::allocator<boost::container::container_detail::pair<int, int>, 2u, 0u>, boost::container::container_detail::pair<int, int>*> >(boost::container::container_detail::pair<int, int>* const&, unsigned long, boost::container::container_detail::insert_move_proxy<boost::container::allocator<boost::container::container_detail::pair<int, int>, 2u, 0u>, boost::container::container_detail::pair<int, int>*>) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/container/vector.hpp:2675:10 in boost::container::vector<MyInt, boost::container::allocator<MyInt, 2u, 0u> >::priv_shrink_to_fit(boost::move_detail::integral_constant<unsigned int, 2u>) 1 SUMMARY: MemorySanitizer: use-of-uninitialized-value /home/ben/development/boost/test/build/boost_root/status/../boost/container/vector.hpp:2604:11 in void boost::container::vector<int, boost::container::allocator<int, 2u, 0u> >::priv_push_back<int>(int&&) 1 SUMMARY: AddressSanitizer: stack-buffer-overflow /home/ben/development/boost/test/build/boost_root/status/../libs/local_function/test/return_derivative.cpp:22:9 in derivative(boost::function<int (int)>&, int)::boost_local_function_auxXfunctorX22X::operator()(int) 1 SUMMARY: AddressSanitizer: stack-buffer-overflow /home/ben/development/boost/test/build/boost_root/status/../boost/intrusive/detail/size_holder.hpp:35:14 in boost::intrusive::detail::size_holder<true, unsigned long, void>::get_size() const 1 SUMMARY: AddressSanitizer: global-buffer-overflow /home/ben/development/boost/test/build/boost_root/status/../boost/numeric/odeint/iterator/impl/times_iterator_impl.hpp:86:42 in boost::numeric::odeint::times_iterator_impl<boost::numeric::odeint::times_time_iterator<boost::numeric::odeint::dummy_stepper, empty_system, boost::array<double, 1ul>, double*, boost::numeric::odeint::stepper_tag>, boost::numeric::odeint::dummy_stepper, empty_system, boost::array<double, 1ul>, double*, boost::numeric::odeint::detail::ode_state_time_iterator_tag, boost::numeric::odeint::stepper_tag>::times_iterator_impl(boost::numeric::odeint::dummy_stepper, empty_system, boost::array<double, 1ul>&, double*, double*, double) 1 SUMMARY: AddressSanitizer: global-buffer-overflow /home/ben/development/boost/test/build/boost_root/status/../boost/numeric/odeint/iterator/impl/times_iterator_impl.hpp:86:42 in boost::numeric::odeint::times_iterator_impl<boost::numeric::odeint::times_iterator<boost::numeric::odeint::dummy_stepper, empty_system, boost::array<double, 1ul>, double*, boost::numeric::odeint::stepper_tag>, boost::numeric::odeint::dummy_stepper, empty_system, boost::array<double, 1ul>, double*, boost::numeric::odeint::detail::ode_state_iterator_tag, boost::numeric::odeint::stepper_tag>::times_iterator_impl(boost::numeric::odeint::dummy_stepper, empty_system, boost::array<double, 1ul>&, double*, double*, double) 1 SUMMARY: AddressSanitizer: container-overflow /usr/local/bin/../include/c++/v1/string:1664:39 in std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__is_long() const 1 SUMMARY: AddressSanitizer: container-overflow /home/ben/development/llvm/trunk/llvm/projects/compiler-rt/lib/asan/../sanitizer_common/sanitizer_common_interceptors.inc:188:3 in __interceptor_strcmp 1 SUMMARY: AddressSanitizer: 96 byte(s) leaked in 6 allocation(s). 1 SUMMARY: AddressSanitizer: 8 byte(s) leaked in 1 allocation(s). 1 SUMMARY: AddressSanitizer: 816 byte(s) leaked in 1 allocation(s). 1 SUMMARY: AddressSanitizer: 797943 byte(s) leaked in 357 allocation(s). 1 SUMMARY: AddressSanitizer: 796079 byte(s) leaked in 351 allocation(s). 1 SUMMARY: AddressSanitizer: 72000000 byte(s) leaked in 3000000 allocation(s). 1 SUMMARY: AddressSanitizer: 65536 byte(s) leaked in 1 allocation(s). 1 SUMMARY: AddressSanitizer: 56 byte(s) leaked in 4 allocation(s). 1 SUMMARY: AddressSanitizer: 324 byte(s) leaked in 3 allocation(s). 1 SUMMARY: AddressSanitizer: 24 byte(s) leaked in 2 allocation(s). 1 SUMMARY: AddressSanitizer: 20 byte(s) leaked in 2 allocation(s). 1 SUMMARY: AddressSanitizer: 1984 byte(s) leaked in 11 allocation(s). 1 SUMMARY: AddressSanitizer: 171 byte(s) leaked in 9 allocation(s). 1 SUMMARY: AddressSanitizer: 14256 byte(s) leaked in 99 allocation(s). 1 SUMMARY: AddressSanitizer: 12345 byte(s) leaked in 1 allocation(s). 1 SUMMARY: AddressSanitizer: 114688 byte(s) leaked in 7 allocation(s). 1 SUMMARY: AddressSanitizer: 104 byte(s) leaked in 2 allocation(s). I'm happy to expand on any line that is less than useful. For the sake of sanity, I think I will also add this to the command line -Wno-unused-local-typedef, as the log contains 462603 matches, often times the warnings push more interesting things off beyond the 64Kb limit. Ben

6 12

Re: [boost] Multiple-pattern string search algorithms
by meghana madhyastha 12 May '15

12 May '15

Hi, The Rabin Karp algorithm performs better than KMP and Boyer Moore during multiple pattern searching. The interface that I have suggested is given below. Please let me know your opinions and if there is a better approach than the one I am suggesting. Any feedback/criticism/guidance will be appreciated and helpful. An overview of the Rabin Karp Algorithm: The Rabin Karp algorithm assigns hash values to the text. The pattern is made to 'slide' along the text to be searched. The hash value of the text is computed and is compared to the hash value of the pattern. A brute force search of each element in the pattern with the current window of text is performed if and only if the hash value of the text matches the hash value of the pattern (and this hash value can be calculated in O(1) time). There can be two interfaces that can be implemented for this a procedural and an object oriented interface (similar to the interfaces for the Boyer Moore Algorithm). There should be two iterator types. One to iterate through the text called 'textIter' and another to iterate through the set of patterns (multiple patterns can be stored as part of a set) called 'setIter'. In the object oriented interface, the hash value of the pattern can be precomputed in the constructor. The text can be searched to match the pattern using the () operator (similar to the implementation of Boyer Moore). In the procedural interface, the search as well as hash computation of the pattern string all happens in the single function 'rabin_karp_search'. template <typename patIter> class rabin_karp { public: rabin_karp ( patIter first, patIter last ); ~rabin_karp (); template <typename textIter> template <typename setIter> textIter operator () ( textIter text_first, textIter text_last, setIter set_first, setIter set_last); }; template <typename patIter, typename textIter> textIter rabin_karp_search ( textIter text_first, textIter text_last, setIter set_first, setIter set_last ); Thanks and Regards, Meghana

1 0

[website] online docs not available?
by Andrzej Krzemienski 12 May '15

12 May '15

Hi Everyone, It looks that the online documentation is not available. the link http://www.boost.org/doc/libs/1_58_0/ displays a blank page. Can you see the docs? Regards, &rzej

3 2

[regression][testing][config] Regression results not displayed.
by Adam Wulkiewicz 11 May '15

11 May '15

Hi, Since 2015/04/26 the tests started to dissapear from Geometry summary pages for develop branch. And now the pages aren't even displayed properly, I see only: Error extracting file: No matching files were found. for: http://www.boost.org/development/tests/develop/developer/geometry.html http://www.boost.org/development/tests/develop/developer/geometry-extension… and on: http://www.boost.org/development/tests/develop/developer/geometry-index.html there are only 2 tests. Furthermore "geometry" and "geometry-extensions" can't be found in the menu. I can see the results for Geometry in the paskages sent to the server. I can also see them in the sanitizer reports sent by Ben. So I'm guessing that the error must be on a later stage of processing, probably in the Regression. Just before the time I saw the issue the first time I added new tests to "geometry-extensions", though it seems wierd that it could affect "geometry" and "geometry-index": https://github.com/boostorg/geometry/commit/9bc8baaa3b3fffc96fbb0abd10a8cb0… https://github.com/boostorg/geometry/commit/07c8b24b89e9fec75c6b7efc7e94032… Geometry is probably the library with the most complex tests structure. We use nested directories and build-project directive in Jamfiles. May this be a part of the problem? AFAIR at that time there were also some changes in the Regression, and the last time something like this happened Config was changed. Could some changes in those modules cause the issue I'm writing about? What may be the reason of such behavior and most importantly do you know how to fix it? Regards, Adam

2 6

What variants should be build on Windows by default?
by Olaf van der Spek 11 May '15

11 May '15

Hi, What library variants should be build on Windows by default? Currently it builds: --build-type=<type> Build the specified pre-defined set of variations of the libraries. Note, that which variants get built depends on what each library supports. -- minimal -- (default) Builds a minimal set of variants. On Windows, these are static multithreaded libraries in debug and release modes, using shared runtime. On Linux, these are static and shared multithreaded libraries in release mode. Personally I use a static-release runtime often (for simple deployments). What variants do others use and what should be build by default? Greetings, -- Olaf

4 3

[array] Support for multidimensional arrays?
by Peter Dimov 10 May '15

10 May '15

Currently, creating a multidimensional boost/std::array is a bit unwieldy: array<array<array<int, 5>, 4>, 3> a; // int a[3][4][5] a[2][3][4] = 5; As a first step, we should consider enabling the element type T of array<T, N> to be an array type. array<int[4][5], 3> a; // int a[3][4][5] a[2][3][4] = 5; This almost works already, except for the array interface functions specified and implemented in terms of, say, std::equal or std::fill. It is an open question whether these standard algorithms should not be fixed themselves to work on array types, as swap_ranges has been, but for now, we can implement the array functions in a way that works. Opinions on that part? If we agree that this is a good idea, the next logical step would be to eliminate the special handling of the first extent and simply allow array<int[3][4][5]> a; // int a[3][4][5] a[2][3][4] = 5;

4 4

[boost.org website] Incorrect links on Boost website
by Michael Levine 10 May '15

10 May '15

I was browsing through the Boost website this morning and the links on the right sidebar caught my attention. It appears that there is a duplicate entry for "coding guidelines for constant integral expressions", under Development / Requirements and Guidelines. The first of these links points to the correct page. The second links to a page regarding library metadata. I'm not sure who, exactly, to contact for this, so I figured this list would be the most appropriate means to have this addressed. Best regards, Shmuel

2 1

[algorithm] Removal of preference to std implementation
by Rob Conde 10 May '15

10 May '15

Marshall/Others-in-the-know, In boost algorithm change set 4dac507b773cf4a82727703ddffa2b36c42ab814, the code which uses std version of algorithms when available was removed. I'm curious about the motivation for this change. I can guess at a few potential reasons, but I figure you can just share the real reason. This change potentially explains a performance regression in my code so I'm just trying to understand the motivation before I make any code changes. Thanks! Rob Conde

1 0

[testing] Add a tester with hidden visibility
by Andrey Semashev 09 May '15

09 May '15

Hi, Is it possible to add a tester that enables hidden visibility (- fvisibility=hidden -fvisibility-inlines-hidden) when building and testing Boost? I believe, a single tester on Linux+GCC would be enough to discover most issues related to symbol visibility. The reason I'm asking is that I believe Boost should support building with hidden visibility by default. This mode allows more optimizations and does not export unintended symbols from libraries. I've set hidden visibility for Boost.Log (in develop) and, as I understand, Robert is doing a similar change in Boost.Serialization. However, when building 1.58 with hidden visibility for my project I found out that not all libraries work well with that setting. What do you think about it?

4 20

Re: [boost] Windows XP support survey
by Thomas Trummer 07 May '15

07 May '15

The sad reality in a lot of industries is that we still have to support Windows XP for the foreseeable future. Though, I understand the desire to drop support for it. Believe me, everyone would be more than happy to just require Windows 7 as default and be done with it. However, it is hard to convince costumers to make the switch when there is only risk and no tangible benefit attached to it. In addition to this we do have the problem that we control complex (and expensive) hardware that consists of components that don’t have drivers for Windows 7 because the manufacturer discontinued them. For these people the end of support from Microsoft isn’t really an argument since the computers are not connected to the Internet and continue to work fine, not to mention that you can still buy extended support from Microsoft. The huge outcry from the C++ community when Microsoft wanted to drop support for XP in Visual Studio should be a clear indicator that a lot of people livelihoods still depend on it. Unfortunately since then the install base hasn’t really shrunken too much. So even Visual C++ 2015 will continue to support it. So, as long as a Visual C++ version supported by Boost can build for Windows XP and there isn’t a significant cost attached to it, Boost should also continue to support Windows XP.

3 2

Re: [boost] Windows XP support survey
by Andrzej Horoszczak - Billon 07 May '15

07 May '15

1 0

Re: [boost] Interest in a container which can hold multiple data types?
by James Armstrong 07 May '15

07 May '15

Sorry about the README file, I pretty much just uploaded what I had to github so people can grab the source. Admittedly, things there are lacking. I'll work on filling out the readme with some instructions hopefully today. The main difference between this and a container of boost:any is that the container of boost::any still is a container of one data type, just being that one data type is a very flexible one. This container natively supports insertion of different data types. So, you could do, int my_int = 5; double my_double0 = 9342.132; double my_double1 = 987.654; std::string my_string("This is a string."); std::vector<double> my_vec; my_vector.push_back(123.456); omni my_container; my_container.push_back(my_int); my_container.push_back(my_double); my_container.push_back(my_string); my_container.push_back(my_vector); and the container happily stores the data. You can then access the data through iterators //access all doubles for (auto itr = my_container.begin<double>(); itr != my_containert.end<double>(); ++itr) { std::cout << *itr << std::endl; } or through specifying the data type and index //get the 0th element string std::cout << my_container.at<string>(0) << std::endl; -- James Armstrong

9 27

[lambda] Addressing pull requests
by Edward Diener 07 May '15

07 May '15

The maintainer for lambda in the libs/maintainer.txt list is Jaako Jarvi, who is the original author. But I see others who have made changes to the library. So I am wondering if anyone is still actively maintaining the library. There are a number of pull requests for lambda, related to updating the code for type_traits Version2, by John Maddock and myself. Is someone handling these ?

5 6

Re: [boost] Arguing about names in Boost libraries
by Vicente J. Botet Escriba 06 May '15

06 May '15

Le 25/04/11 15:21, Edward Diener a écrit : > What is wrong with the people commenting on libraries for Boost who > are so concerned about the names being used ? We are talking only > about C++ identifiers and yet there are now endless discussions where > people disagree on names or argue that some name is not what they want > or that they like some other name, with a list of names that they find > adequate. > > This is irrelevant. There is something mentally wrong about all those > peoples spending endless amounts of time around this issue. I notice > this does not happen nowadays for just one library but for ever single > library, or proposed library, which is mentioned on this mailing list. > > Is this the way all of you people actually work in your daily jobs, or > on your own projects, spending hours and days arguing with others > about C++ identifiers for every little thing ? Are you not aware of > the absurdity of your endless remarks ? > > Grow up ! Surely there are better things to do than carry on endlessly > about some name, that is should be x or y or z or some other inane > preferable list. > > It's time for somebody to say this, so I will do it. A C++ identifier > name, as long as it is vaguely about what the functionality entails, > is perfectly adequate. It does not have to satisfy everyone in the > universe. Period ! > Hi, I'm really surprised to read such a post on this forum. Vicente

4 4

C++11 compilers and fenv
by Damian Vicino 06 May '15

06 May '15

Hi, I’m implementing the safe_float library (on c++11) proposed for the GSOC . I was planning to access FENV for detecting unsafe operations on the native floating point types and include some custom pre-post conditions for testing other floating types safety conditions. Conditions come from policies passed as template parameter to give users the possibility of chose their own set of safety conditions to be enforced. An example of the conditions that can be asked is enforcing overflows to infinite does not happen. An overflow to infinite can be detected by the FE overflow flag or because the addition of two finites numbers result in an infinite one. I just found today that clang++ does not support the pragma to use FENV yet. warning: pragma STDC FENV_ACCESS ON is not supported Googling a little I found out that neither does gcc. How are c++11 boost libraries dealing with these compiler issues? I got some options in mind: — Implement everything using custom detections, this will work in every compiler, but it will run slower for everyone too. — Finding a compiler with the support, implementing the library using the FENV, and assuming compilers will support it when the library is finished and reviewed. — Detect somehow the FENV pragma was not processed and have 2 implementations. No idea how to detect something like this. Had someone dealt with similar problem already? Is there a common approach? Best regards, Damian Vicino

4 5

[ boost ] [ Trie ]
by Cosmin Boaca 06 May '15

06 May '15

Hello, I am interested in working at the Boost.Trie project which was started during GSoC 2013 and I am searching for someone who can give me some advice about what should I change / add to the current implementation, because I'm not too experienced in developing library code. However, I do not want do this during GSoC because I won't be available during the summer. I want to contribute during my spare time. If anyone thinks that can help me with this, please reply to this email. Thank you, Cosmin

8 90

BenPope x86_64 Ubuntu issue at link time
by Vicente J. Botet Escriba 06 May '15

06 May '15

Hi, I'm getting this link error /usr/bin/ld: error: /home/ben/development/boost/test/build/results/boost/bin.v2/libs/thread/test/thread__constr__FArgs_p_lib.test/clang-linux-3.7~asan~c14_libc++/debug/threading-multi/threads/thread/constr/FArgs_pass.o: multiple definition of 'operator delete(void*)' /usr/bin/ld: /home/ben/development/llvm/trunk/install/release/bin/../lib/clang/3.7.0/lib/linux/libclang_rt.asan_cxx-x86_64.a(asan_new_delete.cc.o): previous definition here at http://www.boost.org/development/tests/develop/developer/output/BenPope%20x… I define it as follows #if defined _GLIBCXX_THROW void* operator new(std::size_t s) _GLIBCXX_THROW (std::bad_alloc) #elif defined BOOST_MSVC void* operator new(std::size_t s) #else void* operator new(std::size_t s) throw (std::bad_alloc) #endif { std::cout << __FILE__ << ":" << __LINE__ << std::endl; if (throw_one == 0) throw std::bad_alloc(); --throw_one; return std::malloc(s); } Is this a compiler issue, or is my definition of the operator new incorrect? Vicente

2 2

[move] unique_ptr converting constructor
by Peter Dimov 06 May '15

06 May '15

While looking at https://svn.boost.org/trac/boost/ticket/11259 I found that after implementing a converting shared_ptr constructor that takes a boost::movelib::unique_ptr, the straightforward code in the ticket still fails (with g++ in C++03 mode): namespace mystd { using boost::shared_ptr; using boost::make_shared; using boost::movelib::unique_ptr; using boost::movelib::make_unique; } mystd::unique_ptr<int> load_thing() { return mystd::make_unique<int>(1); } mystd::shared_ptr<int> get_thing() { return load_thing(); } So, out of curiosity, I looked at how unique_ptr itself implements its converting constructor. It turns out that it, too, doesn't work. mystd::unique_ptr<int const> get_thing_2() { return load_thing(); } Furthermore, the two possible ways to make the shared_ptr code work: mystd::shared_ptr<int> get_thing() { mystd::shared_ptr<int> r( load_thing() ); return r; } mystd::shared_ptr<int> get_thing() { mystd::unique_ptr<int> r( load_thing() ); return boost::move( r ); } fail for the unique_ptr<int const> case.

4 8

Re: [boost] Interest in a container which can hold multiple data types?
by Brian Wood 06 May '15

06 May '15

Joaquin M Lopez Munoz writes: > I wrote something on this some time ago, maybe worth having a look at: > > http://bannalia.blogspot.com/2014/05/fast-polymorphic-collections.html <http://bannalia.blogspot.com/2014/05/fast-polymorphic-collections.html> > http://bannalia.blogspot.com/2014/05/fast-polymorphic-collections-with.html <http://bannalia.blogspot.com/2014/05/fast-polymorphic-collections-with.html> I look forward to someone implementing these things. Any progress? -- Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

2 1

Fwd: Boost.Python build error in 1.58 RC1, 2 and 3 (OK in Beta 1)
by Marshall Clow 06 May '15

06 May '15

---------- Forwarded message ---------- From: <mark.incley(a)synx.com> Date: Wed, Apr 8, 2015 at 1:29 AM Subject: Boost.Python build error in 1.58 RC1, 2 and 3 (OK in Beta 1) To: mclow.lists(a)gmail.com Hi Marshall, Please excuse the direct mail, but my mailing list posting wasn't picked up on by anyone. I believe I've found a problem in Boost.Python that causes build errors if the user has Python 3.0 or later on their system. This change appears to have been introduced after 1.58 Beta 1. Using: bjam address-model=32 runtime-link=shared toolset=msvc-12.0 --stagedir=./stage/x86 C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\xtgmath.h(206) : warning C4273: 'round' : inconsistent dll linkage C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\INCLUDE\math.h(516) : see previous definition of 'round' libs\python\src\exec.cpp(91) : error C2664: 'FILE *_Py_fopen(PyObject *,const char *)' : cannot convert argument 1 from 'char *' to 'PyObject *' Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast call "C:\Users\MARK~1.INC\AppData\Local\Temp\b2_msvc_12.0_vcvarsall_x86.cmd" >nul cl /Zm800 -nologo @"bin.v2\libs\python\build\msvc-12.0\debug\link-static\threading-multi\exec.obj.rsp" ...failed compile-c-c++ bin.v2\libs\python\build\msvc-12.0\debug\link-static\threading-multi\exec.obj… The problem appears to be this Boost.Python code that was changed some time after 1.58 Beta 1 and appears in 1.58 RC1 within boost\libs\python\src\exec.cpp at around line 91: 1.58 beta 1: FILE *fs = fopen(f, "r"); 1.58 RCs: FILE *fs = _Py_fopen(f, "r"); ← f is a char *, hence the error shown above. It expects a PyObject * as the first parameter. This code occurs within a test for #if PY_VERSION_HEX >= 0x03000000 which may explain why no-one else has reported it – I have Python 3.3.0 on my HDD. Cheers, Mark. _____________________________________ Sent from http://boost.2283326.n4.nabble.com

13 31

Interest in a container which can hold multiple data types?
by James Armstrong 06 May '15

06 May '15

Hello forum, I was wanting to gauge interest in a container I developed which can natively handle multiple data types (as opposed to using a container of boost::any). I have the templated source hosted on my github account at https://github.com/armstrhu/omni There is some documentation on the current functions under omni/doc/html/index.html. main.cpp has some example codes on inserting, retrieving, and manipulating the data within the container. The one caveat to using the container is that the function destroy<T>() must be called for all data types inserted into the container, I currently have an assert in the destructor which will hit if destroy<T>() is not called for a data type. Also, this requires using a modified version of boost/core/typeinfo.hpp, so you will need to replace the original with the one I provide. The changes simply keep the boost functionality even when C++ typeinfo is available. I am trying to guage interest in this, and if there is interest, get some feedback on additional functionality to include. The iterators I have now work, but they are inefficient and that will be fixed eventually. Currently, I'm calling the container an omni, but don't really like that name and am looking for suggestions for something better :) Thanks -- James Armstrong

5 5

[Voronoi] Weighted Voronoi diagram
by Sybren A. Stüvel 06 May '15

06 May '15

Dear Boost mailing list, Currently I'm working on a Voronoi-based crowd simulation system. We model crowd agents as line segments, and feed them to the Boost Voronoi library. It would be very nice if we could give different line segments different weights. Does the Boost Voronoi library support different weights for its inputs? If not (which I'm afraid is the case, as it isn't mentioned in the documentation), how difficult would it be to add support for this? Kind regards, -- Sybren A. Stüvel http://stuvelfoto.nl/ http://stuvel.eu/

1 0

[threads] Unexpected behaviour of Thread loal storage
by Fu ji 06 May '15

06 May '15

Hello, I would like to ask if there is everything ok with my way of thinking. I have 3 solutions (projects) in MS Visual Studio. Let say: SolutionA (static lib) SolutionB (linked with Solution A) SolutionC (linked with Solution A) In Header file of solutionA I have delaration of TLS from boost static boost::thread_specific_ptr<int> TLS; And now in SolutionB I set tls (TLS.reset(uVariable)) - uVariable is integer 2 Call function from SolutionC and call TLS.get() but there is different value than 2. But when i return from function to SolutionB and call TLS.get there is everything ok (return 2). It's ok ? Why in solutionC there is no visibilty of value set in solutionB ? It's the same thread (with the same threadId). Best regards

2 18

[tuple] Changes living in develop
by Marcel Raad 06 May '15

06 May '15

Hi, there are three commits from last year in develop that haven't been merged to master yet. Could someone merge them please? 8bdf2a9 Make tuple constructor explicit 4fb2618 Add metadata file. b4f0590 Ported documentation to boostbook I always have to apply 8bdf2a9 manually to new Boost releases.

1 0

Re: [boost] [Boost-testing] Attempt to redeclare already registered project id '/check/predef'
by Tom Kent 06 May '15

06 May '15

On Tue, May 5, 2015 at 2:43 AM, Dmitry Moskalchuk <dm(a)crystax.net> wrote: > > Hello, > > Running tests of 'develop' branch, I've bumped with error today: > > error: at /home/cislave/.crystax/ci-boost/regression/android-19-x86-develop/test/develop/regression/x86/test/boost_bb/src/build/project.jam:1069 > error: Attempt to redeclare already registered project id '/check/predef'. > error: Original project: > error: Name: ../check/predef > error: Module: ../check/predef > error: Main id: /check/predef > error: File: ../check/predef.jam > error: Location: ../check/predef > error: New project: > error: Module: ../../predef/check/predef > error: File: ../../predef/check/predef.jam > error: Location: ../check/predef > > > It happens only when run regression tests for 'develop' branch ('master' > is OK). Is this known problem? > I'm getting the same error (which is stopping the regression run) on all my develop testers (windows and linux). Tom

2 1

[Master project] GitHub issues disabled
by Louis Dionne 06 May '15

06 May '15

Hi, The title pretty much says it all. Is there a reason for disabling GitHub issues on the master project? Also, I'd like to know when will the master project be tagged with the 1.58.0 release. Thanks, Louis

18 35

Re: [boost] Interest in a container which can hold multiple data types?
by James Armstrong 05 May '15

05 May '15

On 5/5/2015 7:49 PM, Joaquin M Lopez Munoz wrote: > TONGARI J <tongari95 <at> gmail.com> writes: > >> If the data sequence shows some affinity, I guess an ordered >> tuple_vector-based sequence can provide some performance benefit in >> traversal (with some crafted for_each method). >> >> That is, a sequence of [AAABBB] may be traversed faster than [ABABAB] for >> such a container, and I believe in the later case such that the types are >> uniformly distributed, vector<variant> will perform better. > I wrote something on this some time ago, maybe worth having a look at: > > http://bannalia.blogspot.com/2014/05/fast-polymorphic-collections.html > http://bannalia.blogspot.com/2014/05/fast-polymorphic-collections-with.html > Nice analysis. If we can identify different use cases, we may be able to come up with several implementations of heterogeneous containers which balance efficiency and flexibility. I think it would be an interesting project to work on and surely useful if the containers all the a similar 'feel' -- James Armstrong

1 0

[filesystem] copy_file compilation error
by Rob Conde 05 May '15

05 May '15

In boost 1.55 the following code compiled file on visual studio 2013 and g++ 4.4.7: #include "boost/filesystem/operations.hpp" void myFunc() { using namespace boost::filesystem; copy_option opt(copy_option::overwrite_if_exists); copy_file(path("p1"),path("p2"),opt); } in boost 1.58 I get the following error on g++ 4.4.7 (Visual Studio 2013 continues to work): test.cpp: In function 'void myFunc()': test.cpp:9: error: no matching function for call to 'copy_file(boost::filesystem::path, boost::filesystem::path, boost::filesystem::copy_option&)' boost/filesystem/operations.hpp:494: note: candidates are: void boost::filesystem::copy_file(const boost::filesystem::path&, const boost::filesystem::path&, boost::filesystem::copy_option::enum_type) boost/filesystem/operations.hpp:500: note: void boost::filesystem::copy_file(const boost::filesystem::path&, const boost::filesystem::path&) boost/filesystem/operations.hpp:505: note: void boost::filesystem::copy_file(const boost::filesystem::path&, const boost::filesystem::path&, boost::filesystem::copy_option::enum_type, boost::system::error_code&) boost/filesystem/operations.hpp:511: note: void boost::filesystem::copy_file(const boost::filesystem::path&, const boost::filesystem::path&, boost::system::error_code&) is this a bug in filesystem on gcc, a bug in gcc, a non-standard behavior in visual studio 2013, or an intended change? Rob Conde

2 2

Re: [boost] Description of pre-requisites for building Boost 1.58.0?
by Marko Asplund 05 May '15

05 May '15

On 2015-04-24 22:17:55 Ben Pope wrote: > This doesn't really answer the question, but as a practical note, you > can do: > sudo apt-get build-dep libboost* > Which will install the build dependencies for the version of Boost in > your repository, rather than the version you're trying to build, but it > should get you where you want to be most of the time. FYI, I submitted a documentation pull request for adding a short section about pre-requisite software installation: https://github.com/boostorg/boost/pull/78 marko

1 0

Another variant type (was: [peer review queue tardiness] [was Cleaning out the Boost review queue] Review Queue member requirements)
by Nevin Liber 05 May '15

05 May '15

On 2 April 2015 at 08:13, Niall Douglas <s_sourceforge(a)nedprod.com> wrote: > I > was recently working with eggs.variant for example, and that is Boost > quality written to Boost guidelines and yet I understand there is > zero interest in it entering Boost, despite it being superior to > Boost.Variant in almost every way. I don't remember anyone asking if they'd like to see this in Boost. Could you point to a thread? Even though you claim it is superior in almost every way, if I'm reading it correctly it has one fundamental difference in that it models "at-most-one-of" vs. Boost.Variant which models "exactly-one-of". And yes, I would like to see it in Boost, because as variant gets proposed for the standard, it would be better to have a lot more user experience to help us decide that fundamental question. That certainly fits the current mission in that "We aim to establish 'existing practice' and provide reference implementations so that Boost libraries are suitable for eventual standardization." -- Nevin ":-)" Liber <mailto:nevin@eviloverlord.com> (847) 691-1404

14 43

Interested in contributing
by suryansh tiwari 05 May '15

05 May '15

Hey I'm new, but I'd like to contribute to your organisation, can someone please guide me along? I have done some good amount of competetive programming in c++ and I am completely new to open source.

3 4

Re: [boost] Interest in a container which can hold multiple data types?
by James Armstrong 05 May '15

05 May '15

So, as it is currently implemented, it doesn't actually make use of boost::any or boost::variants. I used a deque<void*> to store addresses of the data, and deque<boost::core::typeinfo> to store the data types. Therefore, iterating through the container to get the data for datatype T simply involves iterating through the deque<boost::core::typeinfo> until a type match is found, then casting the void* to a T* for the corresponding index. There are definitely different ways to take the idea, and maybe there is use for multiple types of heterogeneous containers. The way this container is setup has the advantage (depending on your viewpoint) that you do not have to explicit declare what data types the container will store up front. This could be useful in some context where, for instance, you are pulling information from a database where you don't quite know up front whether certain fields will be numeric or character data until you've queried the db. This container can allow you to pop in whatever data-type the result is, without having to explicitly list out every possibility up front. -- James Armstrong

3 2

[predef] Boost build errors using predef-check
by Edward Diener 04 May '15

04 May '15

In my jam file I have: import ../../predef/check/predef : check require : predef-check predef-require ; and in the requirments section of various Boost Build built-in rules I have: [ predef-check "BOOST_COMP_GNUC >= 4.3" : <cxxflags>-std=c++0x ] When I try to process my jamfile I get numerous warnings along the line of: > C:/Programming/VersionControl/modular-boost/libs/vmd/test\../../predef/check/pre > def.jam:61: in predef-check > warning: object is empty > Jamfile.v2:51: in modules.load > C:/Programming/VersionControl/modular-boost/tools/build/src/build\project.jam:32 > 5: in load-jamfile > C:/Programming/VersionControl/modular-boost/tools/build/src/build\project.jam:64 > : in load > C:/Programming/VersionControl/modular-boost/tools/build/src/build\project.jam:14 > 5: in project.find > C:/Programming/VersionControl/modular-boost/tools/build/src\build-system.jam:535 > : in load > C:\Programming\VersionControl\modular-boost\tools\build\src/kernel\modules.jam:2 > 89: in import > C:\Programming\VersionControl\modular-boost\tools\build\src/kernel/bootstrap.jam > :139: in boost-build > C:\Programming\VersionControl\modular-boost\boost-build.jam:17: in module scope > C:/Programming/VersionControl/modular-boost/libs/vmd/test\../../predef/check/pre > def.jam:61: in predef-check > warning: object is empty > Jamfile.v2:52: in modules.load followed eventually by: > C:\Programming\VersionControl\modular-boost\boost-build.jam:17: in module scope > Performing configuration checks > > - 32-bit : yes (cached) > - arm : no (cached) > - mips1 : no (cached) > - power : no (cached) > - sparc : no (cached) > - x86 : yes (cached) > - symlinks supported : yes > C:/Programming/VersionControl/modular-boost/tools/build/src/kernel\modules.jam:1 > 07: in modules.call-in > *** argument error > * rule ../../predef/check/predef.predef_check_action ( targets + : sources + : p > rops * ) > * called with: ( <p..\..\..\bin.v2\check\predef\gcc-mingw-4.9.2\debug\address-mo > del-32\architecture-x86>8bab483dffdbedc6438ba8af0f25a37e.txt : : <abi>ms <actio > n>@../../predef/check/predef%../../predef/check/predef.predef_check_action <addr > ess-model>32 <architecture>x86 <asynch-exceptions>off <auto-index-internal>off < > auto-index-no-duplicates>off <auto-index-section-names>on <auto-index-verbose>of > f <auto-index>off <binary-format>pe <debug-store>object <debug-symbols>on <doxyg > en.doxproc.index>no <doxygen.processor>xsltproc <embed-manifest>on <exception-ha > ndling>on <extern-c-nothrow>off <format>html <hardcode-dll-paths>true <host-os>w > indows <inlining>off <install-dependencies>off <link>shared <log-api>generic <mi > dl-robust>yes <midl-stubless-proxy>yes <optimization>off <os>NT <pch>on <predef- > expression>BOOST_COMP_GNUC >= 4.3 <preserve-test-targets>on <profiling>off <pyth > on-debugging>off <python.interpreter>C:/Utilities/Python278_32\python <python>2. > 7 <rtti>on <runtime-debugging>on <runtime-link>shared <stdlib>native <strip>off > <suppress-import-lib>false <symlink-location>project-relative <target-os>windows > <testing.execute>on <threadapi>win32 <threading>single <toolset-gcc:flavor>ming > w <toolset-gcc:version>4.9.2 <toolset>gcc <user-interface>console <variant>debug > <warnings-as-errors>off <warnings>on <windows-api>desktop : : : : : : : > : : : : : : : : ) > * missing argument sources > C:/Programming/VersionControl/modular-boost/libs/vmd/test\../../predef/check/pre > def.jam:99:see definition of rule '../../predef/check/predef.predef_check_action > ' being called > C:/Programming/VersionControl/modular-boost/tools/build/src/util\indirect.jam:98 > : in indirect.call > C:/Programming/VersionControl/modular-boost/tools/build/src/build\virtual-target > .jam:798: in class(a)action.actualize > C:/Programming/VersionControl/modular-boost/tools/build/src/build\virtual-target > .jam:311: in actualize-action etc. Any ideas of what is wrong ? Without the use of predef-check everything is OK. I have the latest 'develop' for predef and Boost build. I am trying to set gcc in c++11 mode for gcc 4.3 on up in my VMD tests.

3 5

[predef] Using predef-require with OR conditions
by Edward Diener 04 May '15

04 May '15

In a jamfile I would like to use predef-require in OR situatuations so that if any particular predef-definition is true my unit testing rule occurs, else it does not occur: import ../libs/predef/check/predef : require : predef-require ; run some_test.cpp : : : BOOST_COMP_SOME_COMPILER >= n.n.n || other_predef_definiion ; The typical use case for this is to have a unit test for particular version(s) of a compiler or for all other versions of other compilers. Is this possible ?

2 4

[afio] Trouble with examples
by Brian Ravnsgaard Riis 03 May '15

03 May '15

Hi, The first two examples for the AFIO library do not work as written. The "Hello World" example is missing a file_flag::Create[OnlyIfNotExist] flag on the "example_file.txt" op. Otherwise it never creates the file and the rest of the example becomes garbage. The "less toy" example has a bug in the parsing of the input files. It loops, incrementing argc instead of n, as it should. Even after that I cannot get the program to work, and I am unsure exactly what is wrong. The output file for the concatenated inputs is created and "truncated" to the correct size, but no data ever gets written to this file. If I use large files I have seen std::invalid_argument exceptions and even segfaults. I *think* the problem may be related to the buffers; I have tried using a simple std::vector<char> for the file_buffer_type, but this makes no difference. I have not looked at any other examples yet; I think I should get these two working correctly first... Regards, Brian

2 2

Guidance on contributing to BOOST
by Rohith R 03 May '15

03 May '15

Hey All I am Rohith R, a budding developer from BITS Pilani University in India. Having used a lot of libraries from the STL and BOOST of C++ for my work as an application programmer and some data science projects, i wanted to contribute to BOOST by writing some code for it. I also have experience in writing low-level code for Operating Systems and I have written some basic drivers for raspberry pi as well. I want some guidance on this as to where should i start from and on what area should I focus my library on. This is a small implementation of vector i made just for fun. https://github.com/MadaraUchiha-314/Data-Structures-Library/blob/master/Vec… Any kind of help would be appreciated. Thanks A Lot Rohith R

2 1

[function_types] Pull request for library in 'develop'
by Edward Diener 02 May '15

02 May '15

Is there a maintainer for the function_types library ? Tobias Schwinger is listed as the maintainer but I do not believe he has been active in Boost for a long time. I have a pull request for the library. Can someone who has administrative rights for the library please look at it ?

1 0

Re: [boost] Official JSON Package
by Michael Ainsworth 01 May '15

01 May '15

> Is there an official Boost package for reading and writing JSON data? >> >> Not on Boost, I would suggest you the RapidJSON. >> Do not use boost PropertyTree since you will face incompatibilities mainly >> with arrays. Given that JSON is a de-facto standard (along the lines of INI files and the like) would an official addition as a boost library be considered?

8 8

Official JSON Package
by Michael Ainsworth 01 May '15

01 May '15

Is there an official Boost package for reading and writing JSON data? I know of JSON Spirit, but this is not (to my knowledge) official. I also know the Boost.PropertyTree works, but doesnot have full support. Michael

3 2

[date_time] default constructor for period?
by Scott Bailey 01 May '15

01 May '15

I would like to use this: std::deque<boost::posix_time::time_period> But std::deque depends on (as does some of my other code) it's type having a default constructor. I'm surprised it does not already exists. An implementation that seems to work for me is trivial, although I'm not sure it will work for everyone? My changes to 'boost/date_time_time_period.hpp' follow. I have guarded them with DATE_TIME_NO_DEFAULT_CONSTRUCTOR and simply set begin to point_type() and end to begin_ -1; Is this a change worth an eventual release? Thanks, SB --- a/period.hpp 2015-04-29 15:13:28.040930833 -0700 +++ b/period.hpp 2015-04-29 15:15:01.201392793 -0700 @@ -57,6 +57,9 @@ typedef point_rep point_type; typedef duration_rep duration_type; +#if !defined(DATE_TIME_NO_DEFAULT_CONSTRUCTOR) + period(); +#endif // DATE_TIME_NO_DEFAULT_CONSTRUCTOR period(point_rep first_point, point_rep end_point); period(point_rep first_point, duration_rep len); point_rep begin() const; @@ -82,6 +85,16 @@ point_rep last_; }; +#if !defined(DATE_TIME_NO_DEFAULT_CONSTRUCTOR) + //! default constructor + template<class point_rep, class duration_rep> + inline + period<point_rep,duration_rep>::period() : + begin_(point_type()), + last_(begin_ - duration_rep::unit()) + {} +#endif // DATE_TIME_NO_DEFAULT_CONSTRUCTOR + //! create a period from begin to last eg: [begin,end) /*! If end <= begin then the period will be invalid */ -- Scott Bailey

3 5

[property_tree] Co-Maintainer Needed
by Sebastian Redl 01 May '15

01 May '15

H List, It pains me to say that I can't find sufficient time to maintain PropertyTree the way I should. Bugfixes are delayed, regressions appear, and the long-needed documentation improvement is going nowhere. I made a commitment last C++Now to add C++11 support and document the way I did it in order to help other Boost developers, and failed to do so. New features, like proper encoding support or type-preserving JSON parsing simply aren't happening. It's clear that I can't do it alone. So I am looking for help, someone else who cares about the library and can help me with bugfixes and future development. This could be an individual, a group of people, or the community maintenance team, but I definitely need someone if PropertyTree is supposed to continue as a useful part of Boost. Anyone interested or know somebody who would be interested, please let me know. Sebastian

2 1

Re: [boost] Official JSON Package
by John Venarchick 01 May '15

01 May '15

> > ---------- Forwarded message ---------- > From: Michael Ainsworth <michael(a)michaelainsworth.id.au> > To: "boost(a)lists.boost.org" <boost(a)lists.boost.org> > Cc: > Date: Fri, 1 May 2015 08:53:02 +1000 > Subject: [boost] Official JSON Package > Is there an official Boost package for reading and writing JSON data? > > I know of JSON Spirit, but this is not (to my knowledge) official. I also > know the Boost.PropertyTree works, but doesnot have full support. > > Michael About two years ago when there was talk of a GSOC 2013 project for JSON, I posted that I had been working on changes to ptree so that you could have a ptree<string, boost::any> and be able to round trip successfully. At the time no one seemed interested. I think I should be able to recreate what I had done to make it work for you if your use case is DOM centric like Bjorn Reese's post indicates is one of the draw backs of using ptree. -John Venarchick

1 0

[ANN] "Die Boost C++ Bibliotheken", 2nd edition available (German edition)
by Boris Schäling 01 May '15

01 May '15

Just a quick announcement: The 2nd edition of my book "Die Boost C++ Bibliotheken" (German edition) is available. - It introduces 72 Boost libraries. - It contains more than 430 examples. - The print version has 600 pages. - There is also a Kindle, Epub and PDF version. - It's also online: <http://dieboostcppbibliotheken.de/> There is hardly any difference between the German and the English language edition. The German language edition is a bit more up-to-date after the English language edition has been published in September last year. But there is no need to read the book again in case you read the English language edition already. For those who don't know German: The English language edition remains available online at <http://theboostcpplibraries.com/>. Boris

1 0

[CrystaX.NET][multi_index][release] Segfaults with Clang 3.5 on Android
by Joaquin M Lopez Munoz 01 May '15

01 May '15

Hi, Android CrystaX.NET-* testers are segfaulting on some (~65%) of the Boost.MultiIndex tests after successful build. For instance: http://tinyurl.com/jwnfryy The curious thing is that this is Clang 3.5 only, only for some tests and the same tests across the different Android variants. I'd like to help fixing whatever it's required (if anything) in the lib so as to make this work, but the existing info does not provide any clue. Maybe the regression tester maintainer can shed some more light here? Thank you, Joaquín M López Muñoz Telefónica

2 4

[1.58.0] Release candidates available
by Marshall Clow 01 May '15

01 May '15

Release candidate files for 1.58.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_58_0_rc1.7z) = 609ea035fd3b9f1da110f640c9b8d1e6 MD5 (boost_1_58_0_rc1.tar.bz2) = 7edf680e2532a0370bce64e8e847d661 MD5 (boost_1_58_0_rc1.tar.gz) = 0e435db6a5963e58ffa8d7df49ab5846 MD5 (boost_1_58_0_rc1.zip) = a8d1761306a2ea020e92de53a5cae82d Thanks! -- The release managers P.S. Release notes are here: http://www.boost.org/users/history/version_1_58_0.html

21 53

[1.58.0] Adding Oracle Solaris Studio 12.4 to the list of tested compilers
by Aparna Kumta 01 May '15

01 May '15

One of our primary goals has been to get Oracle Solaris Studio C++ compiler listed on the boost website. With this mind, we have been testing the Boost Nightly regression tests for few months now. For the past month have been submitting the results on http://www.boost.org/development/tests/develop/developer/summary.html (look for the SunOS tab). Could the Oracle Solaris Studio C++ compiler be added to the boost website under 'COMPILERS TESTED' section at http://www.boost.org/users/history/version_1_58_0.html ? Thanks, Aparna

4 6

[githelp] Moving from push to pull requests
by Fletcher, John P 30 Apr '15

30 Apr '15

I have been working for some time on boost phoenix using git push origin develop to push my changes. I have now been asked to change to use pull requests and I am not clear about how to get into the new setup. My current setup on my local computer has phoenix as a subproject in a complete boost clone with branches develop, master and several other branches. I have not created any branches on the remote repository. What I want is to have a repository where I can work and then send pull requests for things to go to the main develop. I have two ideas about how this could be done. (1) create a separate repository outside the modular structure and put a copy of phoenix there. I have created an empty structure called phoenix_changes both on my local computer and under my user name on github. I am puzzled as to how to get the correct content into it. This could come from my local copy or from the main repository. (2) Should I instead create a new branch in both my local and the remote copies of boost/phoenix? If so how do I do that? Can I branch from the current develop as the starting point? In either case I want to be able to send pull requests to the other developers. It would be helpful to have an example of the commands needed. Please ask me for more information if this is not clear. Thank you for the [githelp] resource. John

6 7

[Boost] Windows 10 Building/Testing
by Kyle Ketterer 30 Apr '15

30 Apr '15

Hey all, I was just curious if any devs/users have tried to compile/build on any of the Windows 10 preview releases and if there is a plan to support moving forward. I have been using Boost in various projects for 4-5 years and I am actually interested in getting involved in this project somehow. What is the most appropriate way to become involved? I really appreciate the skill level here and if anything would love the learning experience (learning from the best). Thanks

1 0

[gsoc15] This year's GSoC students
by Niall Douglas 29 Apr '15

29 Apr '15

Dear Boost, It is our pleasure to announce this year's winning GSoC students and projects: 1. Damian Vicino Topic: Safe Float (boost::safe_numerics<float>) Mentor: Robert Ramey 2. Rajaditya Mukherjee Topic: Boost uBLAS EigenSolver Mentor: David Bellot 3. Anurag Ghosh Topic: Boost Document Library Mentor: Antony Polukhin 4. Nikhar Agrawal Topic: Boost.Fixed-Point Mentor: Paul A. Bristow 5. Benedek Thaler Topic: Enhanced vector and deque containers Mentor: Thorsten Ottosen 6. Louis Dionne Topic: Improved compile-time associative data structures for Hana Mentor: Joel Falcou 7. Jakub Szuppe Topic: Improving Boost.Compute Mentor: Kyle Lutz Congratulations to these students for passing an exceptionally tough contest this year, and our thanks to the above mentors for making themselves available. Finally, thank you Google for another year of funding and to those open source orgs who released duplicate students to us, we appreciate it! Niall and Boris --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

5 4

Updated library_status for easier use..
by Rene Rivera 29 Apr '15

29 Apr '15

Following up on the reorganization of the regression tools.. I'm happy to say that part of the changes I pushed last night include a cleaned up and easier to use library_status tool. Key changes, from the older version and the one Robert forked, are: * Processing the jam log (i.e. process_jam_log) is integrated into it. * Running b2 to build/run tests is also integrated into it (optionally). Which means that there's no external support script(s) needed and that it's fully cross-platform single executable. Documentation is updated at < https://rawgit.com/boostorg/regression/develop/index.html> on how to build it and on using it at < https://rawgit.com/boostorg/regression/develop/library_status/doc/library_s… >. Obviously improvements from others welcome (as PRs). HTH -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

3 2

[trac] Internal error
by Edward Diener 28 Apr '15

28 Apr '15

I logged into Boost trac and received: " Trac detected an internal error: OperationalError: database is locked There was an internal error in Trac. It is recommended that you notify your local Trac administrator with the information needed to reproduce the issue. To that end, you could a ticket. The action that triggered the error was: GET: /login"

1 0

[regex] Change format of data in file
by Fu ji 28 Apr '15

28 Apr '15

Hello all, I have file output.txt, in file we can find something like: 01/01/2015 15:00:00 2222.2222 2222.2222 2222.2222 2222.2222 04/04/2015 15:00:00 2222.2222 and i would like to change format from DD/MM/RRRR HH:MM:SS to RRRR-MM-DD HH:MM:SS.000 using boost regex. But I have no clue how should I type pattern and replace them with another. Anyone have knowledge about boost regex and could help me ? Best regards

2 2

[date_time] Ordering non-overlapping time period
by Arindam Mukherjee 28 Apr '15

28 Apr '15

The documentation for time_period suggests that for two periods tp1 and tp2, tp1 < tp2 if tp1.end() < tp2.begin() i.e. !tp1.intersects(tp2). http://www.boost.org/doc/libs/1_58_0/doc/html/date_time/posix_time.html#dat… But I can see that the following works: time_period tp1(second_clock:local_time(), hours(2)); time_period tp2(second_clock:local_time() + hours(1), hours(2)); assert(tp1.intersects(tp2)); assert(tp1 < tp2); The behavior seems legit - tp1.begin() < tp2.begin()/ The documentation says nothing about overlapping periods. Arindam

1 1

[test] floating point comparison
by Emil Dotchevski 28 Apr '15

28 Apr '15

Hello, Can someone please tell me exactly what do I need to include and which namespace to use to get exact same behavior as: #include <boost/test/floating_point_comparison.hpp> bool check( float a, float b, float tolerance ) { using namespace boost::test_tools; return check_is_close(a,b,fraction_tolerance(tolerance)); } (The above used to work with older Boost versions but no longer.) Thanks, Emil

5 8

[boost, config, context, log, 1.58] address-model and architecture detection
by Vladimir Prus 28 Apr '15

28 Apr '15

Hi, for some time on develop, top-level Jamroot used to deduce address-model and architecture from compiler. The only issue was that both properties would be added to targets paths when not necessary. Fix for that has been just committed, for develop: https://github.com/boostorg/boost/commit/945e3c0bbdd31ce8c297e0aff5340f0adb… and I performed these operations on master: - Merged all of Boost.Build changes: https://github.com/boostorg/build/commit/2e764707e03d25b6928501c25a717e195c… - Cherry-picked one Boost.Context change: https://github.com/boostorg/context/commit/9b392c68b59021aa4801dcb245bc64ad… - Cherry-picked one Boost.Log change: https://github.com/boostorg/log/commit/27a822a6b82f8bf34cbc681ac6583412bdf2… - Cherry-picked two root project changes and updated pointers to Context and Log: https://github.com/boostorg/boost/commit/e3bc35f7891e72ad74e57dc216db899d16… https://github.com/boostorg/boost/commit/beb53b6b9574f95309384bfc5afffb40d4… https://github.com/boostorg/boost/commit/b69a072401695c9978085158af4c1ea84c… With that, "./b2 -n" in up-to-date checkout of superproject works fine on Linux. Also, "./b2 -n --with-context --with-system" works fine, no address-model elements in path. Putting explicit address-model=64 does not change path. Putting explicit address-model=32 does add this element to path, as expected. Note that: - I did not merge any other Boost.Context or Boost.Log changes. - Nothing was required for Boost.Config, since it was merged earlier. I'd appreciate if people test current state of master branch, and report any concerns. Thanks, -- Vladimir Prus CodeSourcery / Mentor Embedded http://vladimirprus.com

16 44

[afio] Compilation error in applications, including tests
by Brian Ravnsgaard Riis 27 Apr '15

27 Apr '15

Hi, I wanted to try out the proposed AFIO library, but I'm having trouble with compilation. I followed the instructions for inserting it into the boost checkout, by symlinking libs/afio to the AFIO checkout. Boost compilation happens correctly, including the AFIO library, however I get include failures on BindLib when I try to compile a test program. I then tried running the test suite, as per instructions: $ ./b2 libs/afio/test [snip] gcc.compile.c++.pch bin.v2/libs/afio/test/gcc-4.9.1/debug/threading-multi/test_functions.hpp.gch In file included from ./boost/afio/spinlock/include/boost/spinlock/concurrent_unordered_map.hpp:35:0, from ./boost/afio/config.hpp:341, from ./boost/afio/afio.hpp:41, from libs/afio/test/test_functions.hpp:17: ./boost/afio/spinlock/include/boost/spinlock/spinlock.hpp:81:36: fatal error: bindlib/include/import.h: No such file or directory #include "bindlib/include/import.h" ^ compilation terminated. ... And more of the same ilk. Am I missing some obvious configuration or something? The boost version is at tag boost-1.58.0 and AFIO is at tag v1.31_Boost_v1.58. The BindLib submodule does contain include/import.h. Regards, Brian

2 2

[Property Tree] No documentation for <boost/property_tree/ptree.hpp>
by Nevin Liber 27 Apr '15

27 Apr '15

At < http://www.boost.org/doc/libs/1_58_0/doc/html/property_tree/reference.html#…> The entry for "Header <boost/property_tree/ptree.hpp>" is blank. It looks like a 1.58 bug. Kind regards, Nevin :-) -- Nevin ":-)" Liber <mailto:nevin@eviloverlord.com> (847) 691-1404

1 0

1.58.1 bugfix release necessary?
by Oliver Kowalke 27 Apr '15

27 Apr '15

Unfortunately boost.context fails to compile for gcc-4.8.x and option -std=c++11. Because of a dependency to boost.context, boost.asio and boost.coroutine do not compile too. I've pushed a pull-request to boost.config - the patch adds C++14 test macro BOOST_NO_CXX14_INTEGER_SEQUENCE ( https://github.com/boostorg/config/pull/57) Oliver

14 20

Review request for DLL
by Antony Polukhin 27 Apr '15

27 Apr '15

Hi, Me and Vladimir Prus (review manager) have agreed to start the review of the the DLL library on the June 29. We also agreed that a two weeks review period is required. So the review must go till July 12. Ronald, please adjust the review schedule if there's no objections. -- Best regards, Antony Polukhin

1 0

[vmd] Getting regression tests
by Edward Diener 27 Apr '15

27 Apr '15

I created a pull request for boostorg/boost so that VMD is added to the regression tests. It has been sitting there for a long time now. Can someone at the Boost superproject level please address this pull request ? I want to have VMD added as a library in the next Boost release.

1 0

Boost 1.58.0 has been released
by Marshall Clow 26 Apr '15

26 Apr '15

Release 1.58.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 two new libraries and numerous enhancements and bug fixes for existing libraries. New Libraries * Endian: Types and conversion functions for correct byte ordering and more regardless of processor endianness. * Sort: Includes spreadsort, a general-case hybrid radix sort that is faster than O(n*log(n)) For details, including download links, see http://www.boost.org/users/news/version_1.58.0 You can also download directly from SourceForge: http://sourceforge.net/projects/boost/files/boost/1.58.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

13 17

[interprocess] condition variables and spurious wakeups
by eg 26 Apr '15

26 Apr '15

Hi, I was hoping to get some clarification on whether the boost::interprocess library implementation of condition variables is susceptible to spurious wake ups. Most other library implementations (pthreads, boost::thread, std::thread) seem to be and are documented as such. I couldn't find any mention in the interprocess documentation nor find anything definitive in my google searching. Thanks in advance, Ed

2 1

Latest dependency report
by Peter Dimov 25 Apr '15

25 Apr '15

... generated from the develop branch: http://www.pdimov.com/tmp/report-develop-c3bb6eb/module-overview.html http://www.pdimov.com/tmp/report-develop-c3bb6eb/module-levels.html http://www.pdimov.com/tmp/report-develop-c3bb6eb/module-weights.html

2 2

[boost_document_library] [GSoC'15] How to Start? Any standards to follow?
by Abhinav Tripathi 25 Apr '15

25 Apr '15

Hello, I have finally set up my development environment on Ubuntu 14.10 x64... I am now able to compile any program consisting of Both OpenOffice and Boost code. I have made succesfully small examples with multiple files with both boost and OpenOffice sdk code and compiled them. . I am now ready to start writing code for the document library. What i could think of till now is : 1. Make the project on github and keep it synced 2. Separate classes in different headers with proper namespaces . What i am looking for : 1. Any suggestions on how to start! (More specifically) 2. Are there and standards that need to be followed for developing any library for boost (like using or not using some syntaxes &/or libraires) 3. Any suggestions as to what practices i should use, like which syntaxes/libraries to prefer. . Also, i see that all the boost libraries are independent (i.e., only dependence is within boost itself) [as far as i know]. While what i will be writing will depend on OpenOffice sdk. So, what are its chances to be accepted as an "actual boost library"? . Regards, Abhinav

4 5

tokenizer for overlapping delimiters?
by Jorge Cardoso Leitão 25 Apr '15

25 Apr '15

Dear boost devs, I'm writing here because I've been coding a tokenizer that I believe, given its generality, could be an addition to Boost. I'm asking for a judgement on whether the idea has room in boost or not. The interface I'm proposing is a function of two arguments, a string (call it text) and a set of strings (call it key-terms), that returns a vector<string> (call it result) which fulfils 4 constraints: 1. a string in the result can only be either a key-term or a string between two key-terms; 2. the concatenation of the result is always the original text; 3. a key-term containing other key-terms has priority over the latter; 4. a key-term overlapping other has priority based on its position in the text A tokenizer that divides a string by delimiters is a subset of this interface whose key-terms are the delimiters. This is considered in Boost.Tokenizer, where the key-terms are *non-overlapping. *The critical addition here is the ability to deal with *overlapping key-terms*. A common use case of overlapping key-terms is when you have key-terms that you want to consider as single tokens but they overlap with common delimiters. A practical example: tokenize a string (with words separated by spaces) and guarantee that both `"United States of America"` and `"United States of Brazil"` are interpreted as single tokens. The non-triviality appears because such feat requires storing which key-terms are using a previous sub-string, and how to reverse in case the match fails. (e.g. "United States of " is common to both terms above, but once the first letter appears, either one or both can be discarded as potential matches). Some examples in pseudo-code (see how they fulfil constraints 1-4) tokenize("the end", {}) --> {"the end"} tokenize("the end", {" "}) --> {"the", " ", "end"} tokenize("foo-bar", {"foo", "foo-bar"}) --> {"foo-bar"} tokenize("the end", {"the e", " ", "end"}) --> {"the e", "nd"} tokenize("foo-tars ds", {"foo", "foo-bar", "-tar"}) --> {"foo", "-tar", "s ds"} As a proof of concept, I've implemented such interface and respective test cases, which you can find in https://github.com/jorgecarleitao/tokenize. Any change is possible to accommodate to boost standards: this can be generalized to arbitrary sequences, to arbitrary types, and to use iterators, documented, better tested etc. But before anything else, I would like to ask for an opinion on whether this is sufficiently general and useful to be considered to boost. Thank you for your time, Best regards, Jorge

2 2

Description of pre-requisites for building Boost 1.58.0?
by Marko Asplund 25 Apr '15

25 Apr '15

Hi, While trying to build Boost on Ubuntu 14.04.2 LTS I noticed that the build failed because some library dependencies were missing on my system. I was unable to find documentation about library dependencies and other pre-requisites for building Boost. Are these documented somewhere? Some build related info can be found here, but I couldn't find info about required libraries: http://www.boost.org/doc/libs/1_58_0/more/getting_started/unix-variants.html I was able to build Boost after installing libpython-dev, libbz2-dev packages. This was with default Boost configuration, so other libraries may be required for custom configurations. marko

2 1

[CMT] List of libraries being maintained
by Edward Diener 24 Apr '15

24 Apr '15

Is there a list of libraries being maintained by the community maintenance team ?

3 2

[config] Configuring for C++14 and later library features.
by John Maddock 24 Apr '15

24 Apr '15

Folks, I have an open PR for adding BOOST_NO_CXX14_INTEGER_SEQUENCE (https://github.com/boostorg/config/pull/58) Unfortunately, the correct way to check for std::integer_sequence is to include <utility> and then check for __cpp_lib_integer_sequence. The problem is that we went to some lengths to remove dependencies on <utility> in https://github.com/boostorg/config/pull/40. Further, if we get requests for more such feature-detection macros, we would end up including the whole std lib (see http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2013/n3745#recs.cpp14) This doesn't look acceptable to me, but what to do? The only solution I can see is to simply not support these features in Boost.Config, but rather rely on users needing these features checking the std detection macros directly. Which will work up until someone implements a feature without defining the appropriate macro :( Thoughts? Thanks, John.

7 10

Re: [boost] [thread] Windows compilation broke with 8853a4c
by Jürgen Hunold 24 Apr '15

24 Apr '15

Hi Vicente, On Mittwoch, 22. April 2015 22:50:05 Vicente J. Botet Escriba wrote: > I have rolled back the changes. Please let me know if it works now on > develop. Yes, everything is working again. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

1 0

Git tag for 1.58
by Brian Ravnsgaard Riis 24 Apr '15

24 Apr '15

Hi, 1.58 is still not tagged in the git repo. Does anyone know the sha1 of the relevant commit...? Regards, Brian

1 0

[config] gcc,msvc,mingw visibility
by Robert Ramey 24 Apr '15

24 Apr '15

I've been enabling limited gcc visibility so that it works similarly to msvc *_DECL attributes and will export from the DLL/DSO only those symbols which need to be exported. I've had a lot of difficulty with this. I followed the instructions http://www.boost.org/doc/libs/1_58_0/libs/config/doc/html/boost_config/boos… which more or less boil down to using BOOST_SYMBOL_EXPORT when functions are exported, BOOST_SYMBOL_IMPORT when functions are imported, and BOOST_SYMBOL_VISIBLE on class declarations. I set my Jamfile.v2 in the library build to enable gcc visibility=hidden and let her rip. After the more or less normal back and forth it seemed that the library built and work on all platforms/compilers. .... EXCEPT Mingw. Hmmmm - this shouldn't be too tough, just look at how the other libraries did it. Turns out that it seems that no boost libraries actually enable gcc visibility in their builds - at least as far as I can tell. (I didn't dig into the depths of jam tools files). After a fair amount of research I concluded that for windows platforms - regardless of whether they are built with minnow (gcc) or mdvc, one needs to define BOOST_SYMBOL_VISIBLE as BOOST_SYMBOL_IMPORT or BOOST_SYMBOL_IMPORT which of course makes things more complicated. So here is what I came up with. My questions are: a) did I do this right? b) is there a simpler way c) if the answer to the above is no - can the documentation be updated? Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/config-gcc-msvc-mingw-visibility-tp46747… Sent from the Boost - Dev mailing list archive at Nabble.com.

3 3

[boost.serialization] Problem when serializing a wide char on version 1.58.0
by Marco Oman 23 Apr '15

23 Apr '15

Hi to all, I am having a problem with boost serialization on version 1.58.0 The code at the end of the post is nearly the same found at the beginning of the page libs/serialization/doc/index.html (the 'Very simple case'). The only relevant difference is the use of the wide char version of archive (and fstream) and an additional 'name' text field in the sample structure. This text contains a cyrillic character (the capitol 'D') The problem I am having with this code is that it throws an exception when using version 1.58.0, while everything is OK if I compile/link against version 1.57.0 The problem seems to be related with character conversion: the library seems to convert non ascii chars to local default codepage, instead of UTF-8. So everything looks fine as long as I use characters convertable to my codepage. I gave a look at the differencies between the two versions, but they are definitely beyond my reach... Tests done on windows with MSVC2013 and MSVC2008 Marco #include <fstream> // include headers that implement a archive in simple text format #include <boost/archive/text_woarchive.hpp> #include <boost/archive/text_wiarchive.hpp> ///////////////////////////////////////////////////////////// // gps coordinate // // illustrates serialization for a simple type // class gps_position { private: friend class boost::serialization::access; // When the class Archive corresponds to an output archive, the // & operator is defined similar to <<. Likewise, when the class Archive // is a type of input archive the & operator is defined similar to >>. template<class Archive> void serialize(Archive & ar, const unsigned int version) { ar & degrees; ar & minutes; ar & name; ar & seconds; } int degrees; int minutes; std::wstring name ; float seconds; public: gps_position(){}; gps_position(int d, int m, float s, const std::wstring &n) : degrees(d), minutes(m), seconds(s), name(n) {} }; int main() { // create and open a character archive for output std::wofstream ofs("filename"); // create class instance const gps_position g(35, 59, 24.567f, L"AДbc"); // save data to archive { boost::archive::text_woarchive oa(ofs); // write class instance to archive oa << g; // archive and stream closed when destructors are called } // ... some time later restore the class instance to its orginal state gps_position newg; { // create and open an archive for input std::wifstream ifs("filename"); boost::archive::text_wiarchive ia(ifs); // read class state from archive ia >> newg; // archive and stream closed when destructors are called } return 0; }

1 0

[OpenOffice] [Boost_Document_Library] [GSoC'15] Unable to compile and run the examples in the OpenOffice SDK
by Abhinav Tripathi 23 Apr '15

23 Apr '15

I know this question should be sent to OpenOffice forum. I sent it to their dev list but did not get any response so i am mailing it here in hope to get a response. . I downloaded The OpenOffice 4.1.1 deb files and Sdk 4.1.1 deb file... I used dpkg from command line to install all the deb files.. They got installed in /opt/openoffice4 and Sdk in /opt/openoffice4/sdk . I had to use deb files from the website because i couldn't download it from the apt-get... It showed errors like could not find... I am Using Ubuntu 14.10! When i tried to compile any example in /opt/openoffice4/sdk/examples/DevelopersGuide/ProfUNO/ i got many errors.. . To overcame some of these i did : 1. copied all files from /opt/openoffice4/sdk/bin/ to my root folder /bin/ because the error said /bin/cppumaker : command not found 2. Used a conf file to load all libraries in linux linker cache... using sudo ldconfig because g++ showed error that libreg.so.3 was not found! 3. copied the types.rdb file from sdk folder to my root folder / because it said something about registries not loaded. 4. made a few variables in the makefile like OO_SDK_HOME, JAVA_HOME, JAVA_BIN to allow compilation... 5. Made folder for each example in /opt/openoffice4/sdk/LinuxExamples.out/bin folder because g++ always gave the error that the there was no file or folder of the name of the example that i was compiling. . Now, i am able to compile the examples but when i try to run them with : make office_connect.run or anything like that then again i am getting errors regarding command not found. cd ../../../../LINUXexample.out/bin && office_connect /bin/sh: 1: office_connect: not found Makefile:100: recipe for target 'office_connect.run' failed make: *** [office_connect.run] Error 127 I think it is because of this line in the makefile : %.run: $(OUT_BIN)/%$(EXE_EXT) cd $(subst /,$(PS),$(OUT_BIN)) && $(basename $@) I have no experience of Makefiles and also i am new to openoffice sdk... I am guessing that these errors are happening beacause i installed the packages manually from dpkg instead of using apt-get... Also, i did use setsdkenv_unix once but i think it didnt work as expected as the variables in Makefile are NOT set.. . . It took me nearly a week to figure out these errors and now my patience is wearing out. I know that there has to be an elegant solution to this problem. Please help! . Abhinav

2 4

[Git] Pull requests and rebasing
by John Maddock 22 Apr '15

22 Apr '15

So I have a rebase vs pull question: Lets say I have a PR, if I merge that to my local tree using "git pull --rebase remote-repro branch-name" then I get a nice clean history locally without those pesky merge commits cluttering everything up. But... Now I can't fast-forward when I push to the remote, *because I've changed the existing history of the develop branch*. Would this not be a) bad form, and b) potentially dangerous to push to the remote develop branch? Still don't understand Git yours, John.

6 7

[typeof][CMT] Could the maintenance team please review and merge a trivial pull request?
by Adam Wulkiewicz 22 Apr '15

22 Apr '15

Hi, There is one trivial PR hanging for nearly a year now: https://github.com/boostorg/typeof/pull/1 In those 2 lines of code namespace boost was explicitly added in front of enable_if and disable_if. This allows msvc8 to compile the tests when Boost.Test and Boost.TypeOf are both used. Could you please have a look at it? Regards, Adam

3 4

Re: [boost] [ValueRef] Interest in a new library for immutable values with internal sharing?
by Thomas Jordan 22 Apr '15

22 Apr '15

> Message: 2 > Date: Mon, 20 Apr 2015 15:40:37 +0100 > From: Sam Kellett<samkellett(a)gmail.com> > > To:boost@lists.boost.org > Subject: Re: [boost] [ValueRef] Interest in a new library for > immutable values with internal sharing? > Message-ID: > <CAHK+-Fsy1-sCuMuz+hpjNC2ogAbxUazNY0Qt3xL__bndzkwduw(a)mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > I had a similar idea for a new smart pointer that would aim to obsolete the > shared_ptr-to-const idiom. The problem I found with that idiom is that it > only guarantees that you can't change it. There's no promise that somebody > else doesn't have a non-const ref to the data and so it could in the worst > case completely change from under your feet (even if you know it won't get > destroyed). ValueRef doesn't expose (shared) pointers/pointees, they are a hidden, implementation detail. Its interface just deals in values (as shown in the example usage).

3 2

Re: [boost] [ValueRef]
by THOMAS JORDAN 22 Apr '15

22 Apr '15

> Message: 7 > Date: Tue, 21 Apr 2015 15:37:56 +0000 (UTC) > From: Joaquin M Lopez Munoz <joaquin(a)tid.es> > To: boost(a)lists.boost.org > Subject: Re: [boost] [ValueRef] > Message-ID: <loom.20150421T164358-569(a)post.gmane.org> > Content-Type: text/plain; charset=utf-8 > THOMAS JORDAN <tomjordan766 <at> gmail.com> writes: > > > > > Message: 7 > > > Date: Mon, 20 Apr 2015 18:39:57 +0000 (UTC) > > > From: Joaquin M Lopez Munoz <joaquin <at> tid.es> > > > > > Boost.Flyweight uses move semantics and perfect fwd ction where > > > available, > > > I don't see how another solution can do better on this front > > > > Agreed, I'll withdraw that statement. However, as I said in the O.P., the > > ValueRef implementation I have done is currently only C++03. It uses a > > combination of N x forwarding constructor overloads taking arguments by > > const reference, and the client can use reference wrappers to forward to > > lvaluesto do the non-perfect forwarding (as boost.shared_ptr make_shared > > does) . The intention in the final library would be to support > > C++11/perfect forwarding and possibly Boost.Move for C++03 move semantics. > > So they would be equivalent in that regard. > Understood. Boost.Flyweight does in fact this something similar, > you might want to take inspiration from > http://boost.org/boost/flyweight/detail/perfect_fwd.hpp > > > Boost.Flyweight is indeed heavier on the include side than some > > > people might be comfortable with. > > > > I think this is my concern with having Boost Flyweight as the only option > > for what is a relatively simple type. ValueRef is currently about 350 > > lines of easy-to-understand code in a single header file, and has no > > dependencies on MPL or any other Boost or std libraries, with the > > exception of an atomic library. > > It is intended in particular as a lightweight, clean replacement for > > shared-ptr-to-const, which I see used a lot in code [...] > Of course I don't want to disregard the merit of a lightweight approach > to implementing this idiom. I'm curious: why are you implementing > this from scracth, using atomic etc. rather than wrapping > boost::shared_ptr? The latter, seems to me, is going to be much less > code on your side and the dependencies on the lib are not that many: > http://www.pdimov.com/tmp/report-b1adfee/smart_ptr.html I was inaccurate when I said that ValueRef did not depend on any std libraries, in fact it depends on <memory> for std::allocator<T>. I've modified it to use boost::shared_ptr and boost::allocate_shared (though still just with C++03 forwarding constructors at the moment) - it was trivial, and reduces the LOCS by ~half. > Joaqu?n M L?pez Mu?oz > Telef?nica Tom

1 0

Re: [boost] [Boost-bugs] [Boost C++ Libraries] #11225: failed to compile with msvc8, variadics used wrong
by Damien Buhl 22 Apr '15

22 Apr '15

Thanks Flast, Normally only warnings should be generated. Did you had warnings as errors active? Original Message ‎ From: Boost C++ Libraries Sent: mercredi 22 avril 2015 15:32 Reply To: boost(a)lists.boost.org Cc: boost-bugs(a)lists.boost.org Subject: Re: [Boost-bugs] [Boost C++ Libraries] #11225: failed to compile with msvc8, variadics used wrong #11225: failed to compile with msvc8, variadics used wrong -------------------------+------------------------------------------------- Reporter: | Owner: djowel ingo.loehken@… | Status: new Type: Bugs | Component: fusion Milestone: To Be | Severity: Regression Determined | Keywords: BOOST_PP_IS_EMPTY, phoenix vector, Version: Boost | variadics, vs2005, mscv8 1.58.0 | Resolution: | -------------------------+------------------------------------------------- Comment (by Kohei Takahashi <flast@…>): rels. to #11157 -- Ticket URL: <https://svn.boost.org/trac/boost/ticket/11225#comment:1> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries. _______________________________________________ Boost-bugs mailing list Boost-bugs(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-bugs

2 1

[thread] Windows compilation broke with 8853a4c
by Jürgen Hunold 22 Apr '15

22 Apr '15

Hi Vicente, the commit 8853a4cbdf34d2699d7997ea99adf62fe9d6d568 broke compilation on windows: compile-c-c++ E: \dev\devel\boost\bin.v2\libs\thread\test\test_barrier_void_fct.test\msvc-12.0\debug\test_barrier_void_fct.obj test_barrier_void_fct.cpp E:\dev\devel\boost\boost/thread/win32/condition_variable.hpp(344) : error C2039: 'is_pos_infinity' : is not a member of 'boost::xtime' E:\dev\devel\boost\boost/thread/xtime.hpp(35) : see declaration of 'boost::xtime' E:\dev\devel\boost\boost/thread/win32/condition_variable.hpp(349) : error C2039: 'is_special' : is not a member of 'boost::xtime' E:\dev\devel\boost\boost/thread/xtime.hpp(35) : see declaration of 'boost::xtime' It seems you are calling Boost.DateTime special functions on boost::xtime variables. I'm not sure on how to fix this. The change has not been pickup by the regression matrix yet. Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! * voice: ++49 4257 300 ! Fährstraße 1 * fax : ++49 4257 300 ! 31609 Balge/Sebbenhausen * jhunold(a)gmx.eu ! Germany

1 0

[github] contribution activity not updated
by Joaquin M Lopez Munoz 22 Apr '15

22 Apr '15

Hello, Not that this is very important, but seems like, at least for my GitHub user account, the contribution dashboard is not being updated: if you go to the bottom of https://github.com/joaquintides you'll see the dashboard says I haven't committed anything since Feb 23, which is certainly not the case. Just reporting here in case this might be a symptom of some more serious internal problem with the tool or the repository. Joaquín M López Muñoz Telefónica

2 2

[iostreams] Bogus gzip_alloc in gzip_test.cpp
by Stephan T. Lavavej 21 Apr '15

21 Apr '15

Hi, While testing VC 2015 with Boost, we've discovered a bug in Boost.Iostreams' tests. boost_1_58_0\libs\iostreams\test\gzip_test.cpp contains: struct gzip_alloc : std::allocator<char> { }; This doesn't conform to C++98-17's allocator requirements, because it isn't properly rebindable. (The Standard has always required that rebinding MyAlloc<T> to U and back to T produces MyAlloc<T>.) Thanks, STL

1 0

[polygon] polygon_traits.hpp is incompatible with C++17 std::size()
by Stephan T. Lavavej 21 Apr '15

21 Apr '15

Hi, While testing VC 2015 with Boost, we found that Boost.Polygon contains unqualified calls to non-member size() which are incompatible with C++17's std::size(). Specifically, lines 617 and 703 of boost\polygon\polygon_traits.hpp say: points.reserve(size(polygon)); The argument appears to be "typedef std::list<CPoint> CPolygon;" which is why ADL is considering std::size(). (Note that VC's current lack of Expression SFINAE is not relevant here, as std::size() is viable for std::list.) Here's the full error output (including a new shadow warning): C:\Temp>cl /EHsc /nologo /W4 /wd4100 /MTd /I C:\Temp\boost-1.58.0\include boost_1_58_0\libs\polygon\example\gtl_custom_polygon.cpp gtl_custom_polygon.cpp Unknown compiler version - please run the configure tests and report the results c:\temp\boost-1.58.0\include\boost\polygon\detail/property_merge.hpp(286): warning C4458: declaration of 'output' hides class member c:\temp\boost-1.58.0\include\boost\polygon\detail/property_merge.hpp(223): note: see declaration of 'boost::polygon::merge_scanline<coordinate_type,property_type,polygon_set_type,keytype>::output' c:\temp\boost-1.58.0\include\boost\polygon\detail/property_merge.hpp(584): note: see reference to class template instantiation 'boost::polygon::merge_scanline<coordinate_type,property_type,polygon_set_type,keytype>' being compiled c:\temp\boost-1.58.0\include\boost\polygon\polygon_traits.hpp(617): error C2668: 'boost::polygon::size': ambiguous call to overloaded function c:\temp\boost-1.58.0\include\boost\polygon\polygon_traits.hpp(478): note: could be 'unsigned int boost::polygon::size<polygon_type>(const T &)' with [ polygon_type=CPolygon, T=CPolygon ] \\vcfs\builds\VS\feature_WCFB01\1457423\binaries.x86ret\inc\xutility(1347): note: or 'unsigned int std::size<polygon_type>(const _Container &)' [found using argument-dependent lookup] with [ polygon_type=CPolygon, _Container=CPolygon ] c:\temp\boost-1.58.0\include\boost\polygon\polygon_traits.hpp(617): note: while trying to match the argument list '(CPolygon)' boost_1_58_0\libs\polygon\example\gtl_custom_polygon.cpp(38): note: see reference to function template instantiation 'std::list<CPoint,std::allocator<_Ty>> &boost::polygon::convolve<Polygon,CPoint>(polygon_type &,const point_type &)' being compiled with [ _Ty=CPoint, Polygon=CPolygon, polygon_type=CPolygon, point_type=CPoint ] boost_1_58_0\libs\polygon\example\gtl_custom_polygon.cpp(144): note: see reference to function template instantiation 'void test_polygon<CPolygon>(void)' being compiled c:\temp\boost-1.58.0\include\boost\polygon\polygon_traits.hpp(703): error C2668: 'boost::polygon::size': ambiguous call to overloaded function c:\temp\boost-1.58.0\include\boost\polygon\polygon_traits.hpp(478): note: could be 'unsigned int boost::polygon::size<polygon_type>(const T &)' with [ polygon_type=CPolygon, T=CPolygon ] \\vcfs\builds\VS\feature_WCFB01\1457423\binaries.x86ret\inc\xutility(1347): note: or 'unsigned int std::size<polygon_type>(const _Container &)' [found using argument-dependent lookup] with [ polygon_type=CPolygon, _Container=CPolygon ] c:\temp\boost-1.58.0\include\boost\polygon\polygon_traits.hpp(703): note: while trying to match the argument list '(CPolygon)' boost_1_58_0\libs\polygon\example\gtl_custom_polygon.cpp(40): note: see reference to function template instantiation 'std::list<CPoint,std::allocator<_Ty>> &boost::polygon::scale_up<Polygon>(polygon_type &,boost::polygon::coordinate_traits<int>::unsigned_area_type)' being compiled with [ _Ty=CPoint, Polygon=CPolygon, polygon_type=CPolygon ] Thanks, STL

1 0

Re: [boost] Feedback on Boost.Http
by Brian Wood 21 Apr '15

21 Apr '15

Bjorn Reese writes: > I am using Boost.Http in an embedded application, albeit work on the > integration has been slow due to company priorities. I see. Perhaps the author of the library would be willing to support you in that rather than creating his own applications. That's how I hope to do things also - http://webEbenezer.net/about.html . -- Brian Ebenezer Enterprises - So far G-d has helped us. http://webEbenezer.net

1 0

Re: [boost] [ValueRef]
by THOMAS JORDAN 21 Apr '15

21 Apr '15

> Message: 7 > Date: Tue, 21 Apr 2015 15:37:56 +0000 (UTC) > From: Joaquin M Lopez Munoz <joaquin(a)tid.es> > To: boost(a)lists.boost.org > Subject: Re: [boost] [ValueRef] > Message-ID: <loom.20150421T164358-569(a)post.gmane.org> > Content-Type: text/plain; charset=utf-8 > THOMAS JORDAN <tomjordan766 <at> gmail.com> writes: > > > > > Message: 7 > > > Date: Mon, 20 Apr 2015 18:39:57 +0000 (UTC) > > > From: Joaquin M Lopez Munoz <joaquin <at> tid.es> > > > > > Boost.Flyweight uses move semantics and perfect fwd ction where > > > available, > > > I don't see how another solution can do better on this front > > > > Agreed, I'll withdraw that statement. However, as I said in the O.P., the > > ValueRef implementation I have done is currently only C++03. It uses a > > combination of N x forwarding constructor overloads taking arguments by > > const reference, and the client can use reference wrappers to forward to > > lvaluesto do the non-perfect forwarding (as boost.shared_ptr make_shared > > does) . The intention in the final library would be to support > > C++11/perfect forwarding and possibly Boost.Move for C++03 move semantics. > > So they would be equivalent in that regard. > Understood. Boost.Flyweight does in fact this something similar, > you might want to take inspiration from > http://boost.org/boost/flyweight/detail/perfect_fwd.hpp Ok > > > Boost.Flyweight is indeed heavier on the include side than some > > > people might be comfortable with. > > > > I think this is my concern with having Boost Flyweight as the only option > > for what is a relatively simple type. ValueRef is currently about 350 > > lines of easy-to-understand code in a single header file, and has no > > dependencies on MPL or any other Boost or std libraries, with the > > exception of an atomic library. > > It is intended in particular as a lightweight, clean replacement for > > shared-ptr-to-const, which I see used a lot in code [...] > Of course I don't want to disregard the merit of a lightweight approach > to implementing this idiom. I'm curious: why are you implementing > this from scracth, using atomic etc. rather than wrapping > boost::shared_ptr? The latter, seems to me, is going to be much less > code on your side and the dependencies on the lib are not that many: > http://www.pdimov.com/tmp/report-b1adfee/smart_ptr.html There is no compelling reason why I shouldn't use shared_ptr. The first implementation I did of ValueRef was just a small modification to Adobe's C++03 copy_on_write library, because I had already been playing with that class, it was fairly quite simple and just involved: adding the forwarding constructors; removing the dependencies on the other (Adobe and Boost) libraries; changing the wrapped type to const T; removing the non-const write() function. I operate in a fairly constrained environment, and I generally like the idea of minimising dependencies, however, as you imply, there is no point reinventing the wheel (for example shared_ptr/make_shared would already provide most of the solution for the dual C++03/11 support for forwarding constructors, etc.). Furthermore, I'd guess using shared_ptr might help facilitate submission generally. > Joaqu?n M L?pez Mu?oz > Telef?nica Tom

1 0

Re: [boost] [ValueRef]
by THOMAS JORDAN 21 Apr '15

21 Apr '15

> Message: 7 > Date: Mon, 20 Apr 2015 18:39:57 +0000 (UTC) > From: Joaquin M Lopez Munoz <joaquin(a)tid.es> > To: boost(a)lists.boost.org > Subject: Re: [boost] [ValueRef] > Message-ID: <loom.20150420T202848-660(a)post.gmane.org> > Content-Type: text/plain; charset=utf-8 > THOMAS JORDAN <tomjordan766 <at> gmail.com> writes: >> > > > From: Andrey Semashev <andrey.semashev <at> gmail.com> > > > > > Is this similar to Boost.Flyweight? > > > > It is similar in that both provide a 'smart' handle which can be used > > pretty much as a drop in for the wrapped type. > > > > However, Boost.Flyweight requires the wrapped type to be hashable. > Not necessarily; set_factory, for instance, requires values to > be less-than comparable: > http://boost.org/libs/flyweight/doc/tutorial/configuration.html#set_factory Ok > Also, see below. > > Also, there is a level of indirection with Flyweight which can mean that > > unnecessary temps may need to be created to do the initial lookup (and > > addition) to the Flyweight store, unless you use the Flyweight key-map > > interface. > Boost.Flyweight uses move semantics and perfect fwd ction where available, > I don't see how another solution can do better on this front Agreed, I'll withdraw that statement. However, as I said in the O.P., the ValueRef implementation I have done is currently only C++03. It uses a combination of N x forwarding constructor overloads taking arguments by const reference, and the client can use reference wrappers to forward to lvaluesto do the non-perfect forwarding (as boost.shared_ptr make_shared does) . The intention in the final library would be to support C++11/perfect forwarding and possibly Boost.Move for C++03 move semantics. So they would be equivalent in that regard. > > ValueRef does not use 'flyweighting.' That is, if there are two > > ValueRefs created independently with the same value, e.g., > > > > ValueRef<std::vector<int> > v1(10,10), v2(10,10); > > > > there will be two separate wrapped vector<int> objects - it is only when > > copying/assigning that sharing takes place. It is simpler than Flyweight > > and is essentially intended to be a more value-orientated option to > > shared-ptr-to-const. > The lib is extensible to the point that ValueRef can potentially be > built on top of it: > template<typename Entry,typename Key> > struct ValueRefFactory > { > using handle_type=Entry*; > template <typename E> > handle_type insert(E&& x){return new Entry{std::forward<E>(x)};} > void erase(handle_type h){delete h;} > const Entry& entry(handle_type h){return *h;} > }; > template<typename T> > using ValueRefImpl=flyweight< > T,no_locking, > factory<ValueRefFactory<boost::mpl::_1,boost::mpl::_2>>>; > template<typename T> > struct ValueRef:ValueRefImpl<T> > { > using impl_type=ValueRefImpl<T>; > const impl_type& impl()const{return *this;} > using impl_type::impl_type; > ValueRef(const ValueRef&x):impl_type(x.impl()){} > ValueRef(ValueRef&x):impl_type(x.impl()){} > ValueRef(const ValueRef&&x):impl_type(x.impl()){} > ValueRef(ValueRef&&x):impl_type(x.impl()){} > using impl_type::operator=; > const T& operator*()const{return this->get();} > const T* operator->()const{return &this->get();} > bool identity(const ValueRef& x)const{return &**this==&*x;} > }; > See complete example at: > http://coliru.stacked-crooked.com/a/c33389766fac6ecb > (except the unique_instance bit, which can be done, but admittedly > with more effort). > > Another (less significant) difference is that ValueRef > > currently has no dependency on MPL, which I believe Flyweight does, though > > that could well change if needed. > Boost.Flyweight is indeed heavier on the include side than some > people might be comfortable with. I think this is my concern with having Boost Flyweight as the only option for what is a relatively simple type. ValueRef is currently about 350 lines of easy-to-understand code in a single header file, and has no dependencies on MPL or any other Boost or std libraries, with the exception of an atomic library. It is intended in particular as a lightweight, clean replacement for shared-ptr-to-const, which I see used a lot in code. I also unfortunately y see shared-ptr-to-non-const being used a lot when people should be using shared-ptr-to-const, which is less safe and makes it much harder to reason about what is going on. ValueRef is an explict, consistent and safe alternative to such (mis)usages, and would also sit more comfortably with people who have concerns about build times, library-dependencies and cross-platform issues, etc. > Joaqu?n M L?pez Mu?oz > Telef?nica Tom.

2 1

Configuration error on BenPope x86_64 Ubuntu - clang-linux-3.6~tsan~c14_libc++?
by Vicente J. Botet Escriba 21 Apr '15

21 Apr '15

Hi, There are some reported errors that seems to be associated to the configuration of the tester E.g. http://www.boost.org/development/tests/develop/developer/output/BenPope%20x… /home/ben/development/boost/test/build/results/boost/bin.v2/libs/chrono/test/test_7868_d.test/clang-linux-3.6~tsan~c14_libc++/debug/address-model-64/architecture-x86/test_7868_d: symbol lookup error: /home/ben/development/llvm/trunk/build/release/projects/compiler-rt/lib/tsan/libcxx_tsan/lib/libc++.so.1: undefined symbol: __tsan_unaligned_read16 Please, could you check it? Best, Vicente

2 3

Generating documentation
by Alain Miniussi 21 Apr '15

21 Apr '15

Hi, Just curious, has anyone been able to get the documentation generated (on a linux platform) by following the instructions in http://www.boost.org/doc/libs/1_58_0/doc/html/boostbook/getting/started.html ?? Alternatively, is there a place where the documentation is generated for develop and/or master branch ? Thanks Not that the error messages make much sense, but FWIW, right now, I'm stuck with: [alainm@tagir doc]$ ../../../b2 html Performing configuration checks - 32-bit : no (cached) - 64-bit : yes (cached) - arm : no (cached) - mips1 : no (cached) - power : no (cached) - sparc : no (cached) - x86 : yes (cached) - symlinks supported : yes (cached) /gpfs/scratch/alainm/view/modular-boost/tools/build/src/tools/boostbook.jam:683: in construct warning: object is empty /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:1336: in class(a)basic-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:757: in generate-really /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:729: in class(a)main-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:272: in class(a)project-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build-system.jam:707: in load /gpfs/scratch/alainm/view/modular-boost/tools/build/src/kernel/modules.jam:289: in import /gpfs/scratch/alainm/view/modular-boost/tools/build/src/kernel/bootstrap.jam:139: in boost-build /gpfs/scratch/alainm/view/modular-boost/boost-build.jam:17: in module scope /gpfs/scratch/alainm/view/modular-boost/tools/build/src/tools/boostbook.jam:693: in construct warning: object is empty /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:1336: in class(a)basic-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:757: in generate-really /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:729: in class(a)main-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:272: in class(a)project-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build-system.jam:707: in load /gpfs/scratch/alainm/view/modular-boost/tools/build/src/kernel/modules.jam:289: in import /gpfs/scratch/alainm/view/modular-boost/tools/build/src/kernel/bootstrap.jam:139: in boost-build /gpfs/scratch/alainm/view/modular-boost/boost-build.jam:17: in module scope /gpfs/scratch/alainm/view/modular-boost/tools/build/src/tools/boostbook.jam:707: in construct warning: object is empty /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:1336: in class(a)basic-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:757: in generate-really /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:729: in class(a)main-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build/targets.jam:272: in class(a)project-target.generate /gpfs/scratch/alainm/view/modular-boost/tools/build/src/build-system.jam:707: in load /gpfs/scratch/alainm/view/modular-boost/tools/build/src/kernel/modules.jam:289: in import /gpfs/scratch/alainm/view/modular-boost/tools/build/src/kernel/bootstrap.jam:139: in boost-build /gpfs/scratch/alainm/view/modular-boost/boost-build.jam:17: in module scope ...found 1 target... [alainm@tagir doc]$ -- --- Alain

2 4

Re: [boost] [ValueRef] Interest in a new library for immutable values with internal sharing?
by THOMAS JORDAN 21 Apr '15

21 Apr '15

> Message: 2 > Date: Tue, 21 Apr 2015 10:33:26 +0100 > From: Sam Kellett <samkellett(a)gmail.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] [ValueRef] Interest in a new library for > immutable values with internal sharing? > Message-ID: > <CAHK+-Fu6aYO2UwNkSvJWpn6UzmLjr+qNu+K3x8OSto8dyYGSBA(a)mail.gmail.com > > Content-Type: text/plain; charset=UTF-8 > On 20 April 2015 at 18:07, Thomas Jordan <tomjordan766(a)gmail.com> wrote: > > ValueRef doesn't expose (shared) pointers/pointees, they are a hidden, > > implementation detail. Its interface just deals in values (as shown in the > > example usage). > Absolutely! Hence the ref in the name. :) > I kept the pointer as part of the interface seeing as I saw it as a smart > pointer to replace another smart pointer, but either direction is not wrong > for sure. > The thing I like about the schrodinger_ptr is that I can carry on mutating > it while nobody else is looking, it seems with yours you would have to add > all data to it on it's construction, is that right? Yes, it is an immutable value with sharing of the underlying value object, that is pretty much the gist of it

1 0

Missing 1.58.0 tag on github.com
by Florent Guiliani 21 Apr '15

21 Apr '15

Hi, The release tag for Boost 1.58.0 is missing on github.com: https://github.com/boostorg/boost/releases Could someone please push the tag on github.com ? -- Florent

1 0

Re: [boost] [Boost-bugs] Fwd: [Boost C++ Libraries] #11211: Fusion example no longer compiles
by Joel de Guzman 21 Apr '15

21 Apr '15

Yes we should. This is a showstopper. On 4/21/15 3:06 PM, Damien Buhl wrote: > Sorry for this message, I just saw after sending that Flast already > replied about the problem : > > https://svn.boost.org/trac/boost/ticket/11211?replyto=3#comment:3 > > Shouldn't we make some bugfix release ? Because it is a seriously weird > issue. > > On 21/04/2015 09:01, Damien Buhl wrote: >> Hi Joel, >> >> Thanks for forwarding. >> >> Looks like the support for BOOST_CONSTEXPR BOOST_FUSION_GPU_ENABLED was >> added to DEFINE_STRUCT in a too strong way, which makes it impossible to >> use non-constexpr enabled types (namely std::string). >> >> I think the problem comes from the addition of BOOST_CONSTEXPR where >> BOOST_FUSION_GPU_ENABLED already was. >> >> In this commit >> https://github.com/boostorg/fusion/commit/2114bfca6c8d5e4f7fe2439346e1feddf… >> >> there is BOOST_CONSTEXPR added for the constructors and assignment >> operators. >> >> I think we have to remove the constexpr for this part, because we cannot >> add the requirements that the types the users gives to DEFINE_STRUCT are >> valid within constant expression. >> >> It also didn't come out by unit-tests runs, because our test are only >> done with int types. We have to add types which aren't constant-enabled >> to the tests for DEFINE_STRUCT and by the way for ADAPT also. >> >> I understand the idea behind adding BOOST_CONSTEXPR everywhere where >> BOOST_FUSION_GPU_ENABLED was, but actually it's not the same : on GPU >> there isn't any scenarii where one uses std::string I think, while it is >> typical in normal execution platform, and by the way BOOST_CONSTEXPR >> shouldn't be in this file. >> >> I've pushed a small commit where it then compiles for me on clang + g++ >> with C++03,11,14 : >>> https://github.com/boostorg/fusion/compare/boostorg:master...daminetreg:fea… >> >> >> Cheers, >> >> -- >> Damien Buhl >> >> On 20/04/2015 21:18, Joel de Guzman wrote: >>> Hello Kohei, Damien, >>> >>> Uh oh. Do you know what's happening here? >>> I'm getting: >>> >>> Constexpr constructor never produces a constant expression >>> >>> How did this slip? >>> >>> -------- Forwarded Message -------- >>> Subject: [Boost C++ Libraries] #11211: Fusion example no longer compiles >>> Date: Mon, 20 Apr 2015 19:01:29 -0000 >>> From: Boost C++ Libraries <noreply(a)lists.boost.org> >>> CC: boost-bugs(a)lists.boost.org >>> >>> #11211: Fusion example no longer compiles >>> -----------------------------------------------------+--------------------- >>> Reporter: Adrián Etchevarne <adrian.etchevarne@…> | Owner: djowel >>> Type: Bugs | Status: new >>> Milestone: To Be Determined | Component: fusion >>> Version: Boost 1.58.0 | Severity: Problem >>> Keywords: fusion | >>> -----------------------------------------------------+--------------------- >>> From the manual: >>> >>> {{{ >>> >>> #include <string> >>> #include "boost/fusion/adapted/struct/define_struct.hpp" >>> >>> // demo::employee is a Fusion sequence >>> BOOST_FUSION_DEFINE_STRUCT( >>> (demo), employee, >>> (std::string, name) >>> (int, age)) >>> >>> >>> int main() >>> { >>> } >>> >>> }}} >>> >>> It fails to compile with boost 1.58. With boost 1.57, compiles >>> successfully. >>> >>> g++ --std=c++11 test.cpp -I /home/saknussemm/downloads/boost_1_58_0 >>> >>> clang fails with a similar error. >>> >> _______________________________________________ >> Boost-bugs mailing list >> Boost-bugs(a)lists.boost.org >> http://lists.boost.org/mailman/listinfo.cgi/boost-bugs >> -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/

1 0

[convert] Help. Need promotion from 'develop' to 'master'.
by Vladimir Batov 20 Apr '15

20 Apr '15

On 04/21/2015 05:38 AM, Edward Diener wrote: > On 4/20/2015 1:10 PM, Vicente J. Botet Escriba wrote: >> Le 20/04/15 00:09, Vladimir Batov a écrit : >>> Daniel James created an entry point for 'convert' in the Boost >>> 'develop' branch and 'convert' has been sitting there for quite some >>> time. Now that Boost 1.58.0 has been released I would like to have >>> 'convert' promoted from 'develop' to 'master' so that 'convert' would >>> make it to 1.59. Is there anything that *I* can/need to do to have an >>> entry point created for 'convert' in the Boost 'master' branch? >> I would start a new thread and add you review manager. It is the review >> manager that should check everything is okay. > I was the review manager for 'convert' and it was accepted into Boost. > It has been on 'develop' and been regression tested. > > I myself am not sure of the process of moving a library from 'develop' > to 'master' so maybe someone dealing with the boostorg/boost project > can comment. > > My educated guess is that it would involve a fork of boostorg/boost, a > local 'pull --rebase' from that fork, changes locally that add the > library submodule to 'master' with the necessary commit, a 'push' back > to the fork, and then a pull request so that it shows up at > boostorg/boost and eventually gets merged into the superproject. I > believe part of the local changes are also that status/jamfile.v2 has > to be changed so that the library's tests are added to it. I would expect the master-branch-related "procedure" to be the same as for "develop". As I understand, I myself cannot create an entry point for the library (which is reasonable) and Daniel did that for me in the develop branch. So, I suspect, someone with super-duper permissions would need to step in. Any help in the matter would be greatly appreciated. Tnx, V.

1 0

open for merge?
by Oliver Kowalke 20 Apr '15

20 Apr '15

Hello, is boost open for merging into branch master after the release (unfortunately no entry in the calendar as it was available for previous releases)? thx, Oliver

1 0

DLL library: In search for Review Manager
by Antony Polukhin 20 Apr '15

20 Apr '15

Hi, Boost.DLL library seems ready, users use it and do not complain. Is there anyone wishing to help with review and become a Review Manager? Boost.DLL is a C++98 library for comfortable work with DLL and DSO. Library provides a portable across platforms way to: - load libraries at runtime - import and export any native functions and variables - make alias names for C++ mangled functions and symbols - query libraries/objects and executables for sections and exported symbols - self loading and self querying - getting program and module location by exported symbol Github: https://github.com/apolukhin/Boost.DLL Docs: http://apolukhin.github.io/Boost.DLL/index.html -- Best regards, Antony Polukhin

4 6

Re: [boost] [ValueRef]
by THOMAS JORDAN 20 Apr '15

20 Apr '15

> Message: 11 > Date: Mon, 20 Apr 2015 13:22:35 +0300 > From: Andrey Semashev <andrey.semashev(a)gmail.com> > To: boost(a)lists.boost.org > Subject: Re: [boost] [ValueRef] Interest in a new library for immutable values with internal sharing? > Message-ID: <1988978.ROPBOsQPor@lastique-pc> > Content-Type: text/plain; charset="us-ascii" > On Monday 20 April 2015 11:04:22 THOMAS JORDAN wrote: > > Hi, > > I'd like to gauge whether there might be any interest in a new Boost > > library comprising a generic, non-intrusive, wrapper class for creating > > immutable/const values with sharing of the underlying object via internal > > reference counting. > Is this similar to Boost.Flyweight? It is similar in that both provide a 'smart' handle which can be used pretty much as a drop in for the wrapped type. However, Boost.Flyweight requires the wrapped type to be hashable. Also, there is a level of indirection with Flyweight which can mean that unnecessary temps may need to be created to do the initial lookup (and addition) to the Flyweight store, unless you use the Flyweight key-map interface. ValueRef does not use 'flyweighting.' That is, if there are two ValueRefs created independently with the same value, e.g., ValueRef<std::vector<int> > v1(10,10), v2(10,10); there will be two separate wrapped vector<int> objects - it is only when copying/assigning that sharing takes place. It is simpler than Flyweight and is essentially intended to be a more value-orientated option to shared-ptr-to-const. Another (less significant) difference is that ValueRef currently has no dependency on MPL, which I believe Flyweight does, though that could well change if needed.

2 1

Re: [boost] Feedback on Boost.Http
by Brian Wood 20 Apr '15

20 Apr '15

Vin?cius dos Santos Oliveira: > I recently submitted an HTTP server library to Boost Incubator and I'd > appreciate feedback: > http://rrsd.com/blincubator.com/bi_library/http/?gform_post_id=1460 <http://rrsd.com/blincubator.com/bi_library/http/?gform_post_id=1460> > > I intend to submit to Boost later. > > This is the library that I developed during GSoC 2014 and I made several > improvements (new features, bug fixes, better and extended > documentation...) after the end of GSoC. There are a few improvements that > I still want to do, but none of them would be a barrier for Boost > integration, in my opinion. > > This library doesn't have a builtin request router, opposed to several > libraries out there, then you can use whatever routing style you wish > (tree-based, middleware-based, no router...). > > Also, it follows Boost active style, then you can build your own scheduler > around it (prioritize requests from certain IPs, defer acceptance of new > connections during server high load, reuse prior constructed objects...). > > The library follows Asio threading model, then you also choose whether you > will handle all requests from the same thread (useful for embedded devices) > or multiples ones. The library is fully async, then one thread is not a > problem. > > It has a powerful and flexible file server API, supporting range-based > requests, conditional requests, support for ETags and so on. > > After the GSoC, I had the chance to add tests for asynchronous abstractions > and now the implementation is much more trustable and stable. The choice to > reuse an existing HTTP parser (the Node.js's C parser) also helps a lot. > > The simple message-based API helps to support HTTP pipelining, allocation > fine tuning and much more. Besides HTTP pipelining, HTTP chunking (and > other modern features like 100-continue and HTTP Upgrade) are also > supported. > Do you have any users? If you don't have users, I suggest you become the first user by developing an application. -- Brian Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

4 3

Boost.locale update
by Maks Naumov 20 Apr '15

20 Apr '15

Any plans to update the Boost.Locale ? In https://github.com/boostorg/locale/pulls there are some fixes.

1 0

[ValueRef] Interest in a new library for immutable values with internal sharing?
by THOMAS JORDAN 20 Apr '15

20 Apr '15

Hi, I'd like to gauge whether there might be any interest in a new Boost library comprising a generic, non-intrusive, wrapper class for creating immutable/const values with sharing of the underlying object via internal reference counting. This new class would be called ValueRef (or possibly just Value), and it would effectively provide an assignable/swappable 'reference'/handle to shared, const values. It can be considered an effective alternative to the commonly used shared-pointer-to-const idiom, providing cleaner and more explicit value semantics, whilst also hiding calls to 'new' as an internal implementation detail. In a nutshell, ValueRef adapts a regular type T to give a new type ValueRef<T> with const T value semantics and uses reference counting of an underlying object on the heap internally to reduce copying overhead. ValueRef will spawn off a new copy of the wrapped object (if necessary) if the ValueRef is assigned another ValueRef or another object of type T. Const functions of T do not incur any overhead of counter access or copy and are invoked by either * or -> syntax. Forwarding constructors are provided which permit the wrapped value to be constructed in place, and conversion operator allows inter-operation with values of the unwrapped type. ValueRef also provides the common relational operators. I have so far implemented a rough (C++03-only so far) version of this (based on a stripped down version of Adobe::copy_on_write library) and a test suite and it seems to work okay. Example usage: /* type of ValueRef wrapped std::vector<int> */ typedef ValueRef<std::vector<int> > ValueRefVecType; /* create vector of 10 elements via forwarding constructor */ ValueRefVecType valueRefVector1(10,1); /* non-mutating/const op */ assert( valueRefVector1->size() == 10 ); /* non-mutating/const op */ assert( (*valueRefVector1)[0] == 1 ); /* error - compilation failure occurs calling a non-const op */ (*valueRefVector)[0] = 2; /* copy ctor */ ValueRefVecType valueRefVector2(valueRefVector1); /* test for equality */ assert( valueRefVector1 == valueRefVector2 ); /* test for equality (implicit conversion) */ assert( valueRefVector2 == std::vector<int>(10,1) ); /* valueRefVector1 and valueRefVector2 share same std::vector */ assert( valueRefVector1.identity(valueRefVector2) ); /* ref count is no longer one */ assert( !valueRefVector1.unique_instance() ); /* new value */ valueRefVector1 = std::vector<int>(5); /* non-mutating/const */ assert( valueRefVector1->size() == 5 ); /* test for equality - value semantics */ assert( !(valueRefVector1 == valueRefVector2) ); /* valueRefVector1 and valueRefVector2 do not share same std::vector */ assert( !valueRefVector1.identity(valueRefVector2) ); I am not aware of anything else current that provides this functionality. Regards, Tom

3 2

[release] Python 3 build problems
by Daniel James 20 Apr '15

20 Apr '15

Hi, Is there anyone who can write a brief description of the build problem with python 3 for the release notes? We probably should say something. thanks, Daniel

4 12

[regex] Support for Perl's (*SKIP)
by Sei Lisa 20 Apr '15

20 Apr '15

I'd like to see support for Perl's (*SKIP) regex verb in Boost. There are a number of verbs, but that one has an interesting and frequent use case: it enables searching for an expression but only outside of some contexts. There is a page called "The best regex trick" with details about the process and a number of examples. I can't link to it as this is my first message (I attempted before but it was rejected). It explains how to do it with and without (*SKIP). I've seen several questions in Stack Overflow asking how to accomplish that task, so it seems it's quite frequent to run into that need. Let's say for example that we want to find the string 'foo' as an identifier in C. This is a crude example of a Perl regex that does it (a real one might need to be more elaborate; in particular, backslashes for line continuation are not considered): (?x-s) (?# free spacing, dot doesn't match newline) (?://.*+ (?# eat single-line comment text) |/\*[\S\s]*?\*/ (?# eat multi-line comment text) |"(?:\\.|[^"\n])*+" (?# eat string text) )(*SKIP)(?!) (?# skip these) |\bfoo\b (?# match this) regex::search will match that expression only when foo is present outside of a string or comment. Without (*SKIP), it can be done only by calling regex::search multiple times, using an expression like this: (?-s)//.*+|/\*[\S\s]*?\*/|"(?:\\.|[^"\n])*+"|(\bfoo\b) and ignoring every match where group 1 wasn't matched. That's presumed to be slower, and certainly more inconvenient for the programmer. Support for this particular use case would be a great feature to have in the regex engine. Sei

2 3

[master] Open for 1.59?
by Joaquin M Lopez Munoz 20 Apr '15

20 Apr '15

Is master already open for commits towards Boost 1.59? Thank you, Joaquín M López Muñoz Telefónica

1 0

[config] BOOST_SYMBOL_VISIBLE on MinGW
by Robert Ramey 20 Apr '15

20 Apr '15

I made adjustments so that the serialization library on Develop branch will build with default visibilty = hidden. There is a little more to this than one would think. Basically I used BOOST_SYMBOL_VISIBLE on all "exported" classes (and their base classes) and BOOST_ARCHIVE_DECL ( defined as either BOOST_ARCHIVE_IMPORT or BOOST_ARCHIVE_EXPORT) on exported/visible member functions. This seems to give me what I need in that things build and test for gcc, clang, MSVC. EXCEPT for gcc under MinGW. see http://www.boost.org/development/tests/develop/developer/output/MinGW-32%20… The message seems to indicate to me that I should have BOOST_SYMBOL_VISIBLE on the class declaration - which seemed to resolve similar compilation errors with GCC on other platforms. Poking around config/compiler/gcc.hpp and config/plaform/w32.hpp It seems to me that this scheme things look OK - that is it looks that BOOST_SYMBOL_VISIBILITY should be defined as __attribute__((__visibility__("default"))) I'm also puzzled by the fact that the linker craps out only on this on declaration. Any help appreciated. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/config-BOOST-SYMBOL-VISIBLE-on-MinGW-tp4… Sent from the Boost - Dev mailing list archive at Nabble.com.

2 2

[container][stable_vector] What does reserve() do for stable_vector
by Arindam Mukherjee 19 Apr '15

19 Apr '15

Consider the following code. #include <string> #include <boost/container/stable_vector.hpp> #include <iostream> int main() { boost::container::stable_vector<std::string> vec; vec.reserve(10); std::cout << "capacity = " << vec.capacity() << '\n'; } On running this (on g++ and Linux), the output is: capacity = 4294967286 (that's 2^32 - 10) If replace boost::container::stable_vector with std::vector above, the output is: capacity = 10 I know it could as well have been capacity = 20, or capacity = 64 or whatever but that's still sane behavior. What capacity() returns for stable_vector seems to be (2^32 - N), N being the requested capacity. I didn't see such a definition of capacity in the docs: http://www.boost.org/doc/libs/1_56_0/doc/html/boost/container/stable_vector… Thanks, Arindam

2 1

[type_traits] Testing for copy constructor
by Edward Diener 19 Apr '15

19 Apr '15

Does one use has_trivial_copy or has_nothrow_copy to determine if a class has a copy constructor or not ? I am writing some code that can do different things depending on whether a particular class has a copy constructor or does not have a copy constructor. I do not really care whether the copy constructor is a compiler generated copy constructor or not.

2 1

Feedback on Boost.Http
by Vinícius dos Santos Oliveira 18 Apr '15

18 Apr '15

I recently submitted an HTTP server library to Boost Incubator and I'd appreciate feedback: http://rrsd.com/blincubator.com/bi_library/http/?gform_post_id=1460 I intend to submit to Boost later. This is the library that I developed during GSoC 2014 and I made several improvements (new features, bug fixes, better and extended documentation...) after the end of GSoC. There are a few improvements that I still want to do, but none of them would be a barrier for Boost integration, in my opinion. This library doesn't have a builtin request router, opposed to several libraries out there, then you can use whatever routing style you wish (tree-based, middleware-based, no router...). Also, it follows Boost active style, then you can build your own scheduler around it (prioritize requests from certain IPs, defer acceptance of new connections during server high load, reuse prior constructed objects...). The library follows Asio threading model, then you also choose whether you will handle all requests from the same thread (useful for embedded devices) or multiples ones. The library is fully async, then one thread is not a problem. It has a powerful and flexible file server API, supporting range-based requests, conditional requests, support for ETags and so on. After the GSoC, I had the chance to add tests for asynchronous abstractions and now the implementation is much more trustable and stable. The choice to reuse an existing HTTP parser (the Node.js's C parser) also helps a lot. The simple message-based API helps to support HTTP pipelining, allocation fine tuning and much more. Besides HTTP pipelining, HTTP chunking (and other modern features like 100-continue and HTTP Upgrade) are also supported. There are zero reviews/comments on Boost Incubator right now and I'd love to see more eyes on this lib that does better on many fronts than previous choices. Benchmark is one item that I still need to tackle, btw. But I hope to see good results here too. -- Vinícius dos Santos Oliveira https://about.me/vinipsmaker

1 0

[tools] How to use 1.58.0/bjam --toolset=sun for specified stdlib feature?
by Sergey Sprogis 18 Apr '15

18 Apr '15

Running boost regression unit tests I found it convenient to direct output from every single tested library into a separate logfile. To do that, my testing script (bash) at first extracts the list of all <library>/test lines from status/Jamfile.v2, and puts them into another test_suites.txt file. Then it runs all extracted test suites like this: my_res_dir= `pwd` for dir in `cat test_suites.txt`; do dir1=`echo $dir | sed "s/\//\./g"` cd $BOOST_ROOT/libs/$dir bjam --toolset=sun variant=release > $my_res_dir/$dir1.log 2>&1 done All that worked fine until boost-1.58 in which tools/build/src/tools/sun.jam file was modified so that instead of single standard library it now allows the possibility of using any of 5 available libraries. The question is, how exactly should I define bjam's options in my bash script shown above, if for example, I want to use gnu library in c++03 mode? The proper code inside sun.jam file looks like this: feature.extend stdlib : gnu ; feature.compose <stdlib>gnu : <cxxflags>-std=c++03 <linkflags>-std=c++03 ; but how should I tell to bjam to use this specific library? Thanks, Sergey

3 2

[build] [boost 1.58] Error when compiling with MSVC-7.1
by Ion Gaztañaga 18 Apr '15

18 Apr '15

Hi, I just tried the newly released version with this toolset (I don't think many will use and support it, but still useful). Output when building move from boost/libs/move/test: ..\..\..\b2.exe toolset=msvc-7.1 variant=debug C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:1075: in configure-really *** argument error * rule generate-setup-cmd ( version : command : parent : options * : cpu : global-setup : default-global-setup-options : default-setup ) * called with: ( 7.1 : C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin : C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7 : <command>C:\Program Files (x86)\Microsoft Visual Studio .NET 2003\Vc7\bin\cl.exe : i386 : : x86 : vcvars32.bat ) * missing argument global-setup C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:809:see definition of rule 'generate-setup-cmd' being called C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:201: in configure C:/Data/Libs/boost/tools/build/src/tools\msvc.jam:153: in msvc.init C:/Data/Libs/boost/tools/build/src/build\toolset.jam:43: in toolset.using C:/Data/Libs/boost/tools/build/src\build-system.jam:461: in process-explicit-toolset-requests C:/Data/Libs/boost/tools/build/src\build-system.jam:527: in load C:\Data\Libs\boost\tools\build\src/kernel\modules.jam:289: in import C:\Data\Libs\boost\tools\build\src/kernel/bootstrap.jam:139: in boost-build C:\Data\Libs\boost\boost-build.jam:17: in module scope I've found a workaround adding this to user-config.jam, in case anyone needs a workaround: using msvc : 7.1 : : <setup>"C:/Program Files (x86)/Microsoft Visual Studio .NET 2003/Vc7/bin/vcvars32.bat" ; Of course that path is in a 64-bit Windows OS, adjust it to your installed path. Best, Ion

1 0

[Hana] Formal review dates
by Louis Dionne 17 Apr '15

17 Apr '15

Dear Boost, As I already announced in a previous message, a formal review is about to be asked for Hana. The current preferred dates would be April 25 - May 8. However, we are concerned that people might be unavailable to do reviews such a short time before C++Now. The goal of this message is to ask potential reviewers whether they would be available during the proposed period. If people seem unfavorable or if there is too little feedback to this message, we will consider pushing back the review to after C++Now. Note that one reason why I'm trying to squeeze the review before C++Now is because it could hugely help with marketing the library if it was accepted. Regards, Louis

3 4

Release Status?
by Olaf van der Spek 17 Apr '15

17 Apr '15

Hi, What's the status of the release? -- Olaf

2 1

Re: [boost] [Boost-users] [IPC Named Mutex]
by Tom Kent 16 Apr '15

16 Apr '15

On Thu, Apr 16, 2015 at 3:01 AM, Lorenzo Trivelli < trivelli.lorenzo(a)konvergence.it> wrote: > Hi to everyone, > I'm experiencing a strange behaviour of named mutex on > a windows 2008 machine. > symptoms: when the system event log is empty, creation > of named mutex fails with a boost::interprocess::interprocess:exception > with msg boost::interprocess_exception::library_error. > Now some data: > 1) Boost 1.57.0 + stlport 5.2 > 2) VS 2005 > 3) Target Environment: Win 2008/32 > 3) after a night of code digging I managed to crete a small sample > which raises the exception: > > #include <boost/shared_ptr.hpp> > #include <boost/interprocess/sync/named_mutex.hpp> > #include <boost/interprocess/sync/scoped_lock.hpp> > #include <iostream> > > typedef boost::shared_ptr<boost::interprocess::named_mutex> > safe_ipc_mx; > > static safe_ipc_mx __mx; > int main(void) { > system("pause"); > try { > __mx = safe_ipc_mx(new > boost::interprocess::named_mutex(boost::interprocess::open_or_create_t(),"JAEGER")); > std::cout << std::endl << "Mutex created !" << std::endl; > } catch(boost::interprocess::interprocess_exception const& e) { > std::cout << std::endl << "Mutex creation error " << > e.what() << " /" << e.get_error_code() << " /" << e.get_native_error(); > } > system("pause"); > return 0; > > } > > I tried it also, and got the same result. I also tried with msvc-12.0, same result. > as far as I digged, it seems that the trouble is in the > winapi::get_last_bootup_time(stamp) call > in shared_dir_helpers.hpp, but up to now I had not been able to reproduce > it on a machine with > all the debugging tools installed > get_last_bootup_time() looks through the system event log for event ID == 6005 (event log started)...since the event log was cleared out, this is not found. I guess that is a bug in boost. One thing you could try...in interprocess's win32_api.hpp, there is another implementation of get_last_bootup_time() which uses WMI instead of the event log (there were warnings in the source about WMI not supporting hibernation/clock changes correctly, so beware). If you define BOOST_INTERPROCESS_BOOTSTAMP_IS_LASTBOOTUPTIME it should use that other version...give that a try. (in visual studio Project Properties -> C/C++ -> Preprocessor -> Preprocessor Definitions: add a semi colon ';' then the above item) That worked for me on windows 7. I submitted a pull request to automatically fallback to WMI if the event log started event isn't in the log. https://github.com/boostorg/interprocess/pull/18 Tom

1 0

[serialization] failing MPI build
by Alain Miniussi 16 Apr '15

16 Apr '15

Hi, Am I the only one with a (global) failing build on MPI ? ../../../boost/archive/detail/interface_oarchive.hpp(63): error: no instance of overloaded function "boost::mpi::detail::content_oarchive::save_override" matches the argument list argument types are: (const boost::archive::tracking_type) object type is: boost::mpi::detail::content_oarchive this->This()->save_override(t); I am going to investigate, but maybe I missed something obvious. Thanks Alain

2 17

std::map<> - like structure for other than std::pair<>?
by David Hagood 16 Apr '15

16 Apr '15

Several times I have run into a use case where I have some object that I would like to access via something like a std::map<>, but which already contains a member that I would like to use as a key. Is there any data structure that "acts like a map", but instead of storing std::pair<key,value> allows me to store an object directly, and specify what member of that object is the key value? I can give a specific use case for this: For those of you not familiar with the SCA, there is an object called CF::Properties. This is a CORBA sequence (think std::vector) of objects of {string name, CORBA::Any value}, used to store metadata. Ideally, I'd like to have an object that I could initialize from that sequence that would allow me to do things like this: inline string &getKey(CF::Property &x) { return x.name; } void foo(CF::Properties &meta) { mapLikeThing<CF::Property,getKey> myMap(meta); double sampleRate; myMap["SampleRate"] >> sampleRate; setHardwareSampleRate(sampleRate); }

7 8

Fwd: Windows Intel Compiler problem
by Mari Pecha 15 Apr '15

15 Apr '15

Good morning, I try compile boost with Intel Compiler under Windows OS, but I got an error message screen is in attachments. I don't know what I'm doing wrong, can you help me? Thank you Mari --- This email has been checked for viruses by Avast antivirus software. http://www.avast.com

2 1

GSOC 2015 Sample Code
by Aditya Avinash Atluri 14 Apr '15

14 Apr '15

Hi, I was unable to put sample code during submission because I was busy with Mesa. Here is the sample code: https://gist.github.com/adityaatluri/22c97a726c304d9e5c50 -- Regards, Aditya Avinash Atluri, Graduate Student, Electrical and Computer Engineering, The George Washington University, Washington, DC.

1 0

htmlspecialchars and urlencode?
by Olaf van der Spek 14 Apr '15

14 Apr '15

Hi, Does Boost have functions like htmlspecialchars and urlencode (from PHP)? If not, I think they'd make a nice addition to the string algorithm lib. -- Olaf

4 6

boost::posix_time::duration_from_string throws std::out_of_range
by George Georgiev 13 Apr '15

13 Apr '15

Hi, I just noticed that boost::posix_time::duration_from_string throws std::out_of_range when I pass empty string to it. This seems like a bug, IMHO it should throw boost::bad_lexical_cast as it does for any other problem with the input. Thanks, George

2 2

Git tags and Boost release
by Robert Ramey 12 Apr '15

12 Apr '15

I look in my history of the master branch and It seems to me I would like to be able to know which commit corresponds to which Boost release. I think the correct functionality to do this is described here. http://git-scm.com/book/en/v2/Git-Basics-Tagging I'm wondering if we want to do this upon release so we can remember where we were when something blows up. Ideally, I'd like the release managers to be able to just global to the "mark" when the release is "official" I like git - but anything I haven't done before is out of my comfort zone. So any insight would be appreciated. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/Git-tags-and-Boost-release-tp4674328.html Sent from the Boost - Dev mailing list archive at Nabble.com.

3 3

[modular boost][install] Signals2 include links not being generated during build
by Greg Rubino 12 Apr '15

12 Apr '15

Hi, I'm building modular boost on 32-bit debian linux, and the build runs without error, but the links for some of the header files are not created. Here's what I'm running: $ bash bootstrap.sh $ ./b2 --runtime-link=static --without-python --without-mpi --without-iostreams At the end of the build (which shows warnings but no failures), I get this message: """ ...updated 836 targets... The Boost C++ Libraries were successfully built! The following directory should be added to compiler include paths: .../boost The following directory should be added to linker library paths: .../boost/stage/lib """ But for some reason signals2 is not being built. From the boost build directory: $ ls stage/lib/libboost_signals2* ls: cannot access stage/lib/libboost_signals2*: No such file or directory $ ls boost/signals2.hpp ls: cannot access boost/signals2.hpp: No such file or directory I'm not sure what happened or even how to diagnose whatever the issue might be. Has anyone seen this before or have any troubleshooting tips for me? Thanks, Greg

2 1

1.58.0 rc3 is now available
by Marshall Clow 12 Apr '15

12 Apr '15

Release candidate files for 1.58.0 are available at: http://boost.cowic.de/rc/ * Since rc1, the changes that were causing the serialization libraries to fail to build on MSVC have been reverted. * Since rc2, the documentation for bind, and mem_fun. No code changes. 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_58_0_rc3.7z) = f7255aeb692c1c38fe761c32fb0d3ecd MD5 (boost_1_58_0_rc3.tar.bz2) = b8839650e61e9c1c0a89f371dd475546 MD5 (boost_1_58_0_rc3.tar.gz) = 5a5d5614d9a07672e1ab2a250b5defc5 MD5 (boost_1_58_0_rc3.zip) = b0605a9323f1e960f7434dbbd95a7a5c Thanks! -- The release managers P.S. Release notes are here: http://www.boost.org/users/history/version_1_58_0.html

3 3

[serialization][develop] Unable to find file or target named 'test_polymorphic_helper.cpp'
by Dmitry Moskalchuk 11 Apr '15

11 Apr '15

It seems that latest commit to develop branch of Boost.Serialization (https://github.com/boostorg/serialization/commit/a32549c25fa983fea2b5dfeaf9…) break build of Boost: error: at /home/cislave/.crystax/ci-boost/regression/android-19-armeabi-v7a-develop/test/develop/regression/armeabi-v7a/test/boost_bb/src/kernel/modules.jam:107 error: Unable to find file or target named error: 'test_polymorphic_helper.cpp' error: referred to from project at error: '../libs/serialization/test' And really, there is no file libs/serialization/test/test_polymorphic_helper.cpp. I guess it was forgotten to be added to git. -- Dmitry Moskalchuk

2 1

[Boost Document Library] Which SDK / OS to use for development?
by Abhinav Tripathi 11 Apr '15

11 Apr '15

I am trying to start the development of a Document Library for Boost which was listed under the GSoC projects list. I successfully built Boost 1.57 on windows 8 with MinGW using some help from this mailing list. Now, i wish to develop the library on windows only (Although i can shift to linux if need be).... When i went through the links provided on the ideas list, i came across following things : --The OpenOffice SDK asks to either use linux or Visual Studio on Windows and there is practically nothing (documentation) for compiling with MinGW. --The LibreOffice SDK also asks to install many *nix tools first and also doesn't mention anything about compatibility with MinGW. --The last 2 links use .NET and some other MS libraries which i am pretty sure won't be much portable... . I wish to develop the library so as to get it accepted to Boost at some point. I assume that Boost would accept only cross platform code, so i discarded the last two links. I am now in a dilemma..... Which of the 2 SDK should i try to use on Windows with MinGW.. Or should i NOT develop on windows and shift to linux... . Also, The MS Office formats are not open but other office formats might be open and hence i can also try and develop something without using any of the available SDKs. So, instead of developing of a wrapper, i can aim to develop a complete library to load and manipulate document files... . Please suggest some option and show me a way as to which SDK/Platform should i use. And how to continue the development for the Document Library. . Regards, Abhinav

2 3

[fiber, afio, dl, bindlib, expected, hana, tick, fit, simd, dispatch] Checking my shortlist of upcoming Boost C++ 11/14 librari
by Niall Douglas 10 Apr '15

10 Apr '15

Dear Boost, I've spent the last few days reviewing the shortlist of C++ 11/14 libraries as suggested in this thread http://article.gmane.org/gmane.comp.lib.boost.devel/255548 which appear closest to entering Boost as per the rules in my C++ Now abstract: 1. The library must be C++ 11/14 only. As in, no C++ 03 compilation possible. 2. The order chosen shall be the closest to entering Boost in March/April (i.e. now), so already in Boost, approved to enter Boost, in the formal review queue, approaching the formal review queue. At https://drive.google.com/open?id=1Bizs9xz2dyt1d5GJv-pOCmu1cS67gRd0KNYn sjYK Ji w&authuser=0 you will hopefully find a traffic light dashboard spreadsheet (I tried posting a PNG here, it was refused). In it is shown the current state, as estimated by fallible me from a cursory glance at the library, for various measures of the library. Errors are entirely possible, hence me asking here before I make a fool of myself. List members may be as surprised as I was to learn that most of the upcoming libraries require C++ 14. They are also universally standalone from Boost, being about as weakly dependant as is possible and still be called a Boost library. That was a big surprise to me as well. Another surprise was the dislike of Boost.Test - a lot of libraries don't use it, indeed can't use it. And finally, almost everyone uses Travis CI, though not valgrind memcheck for leak detection nor coveralls for unit test coverage. The first category is libraries already in the formal review queue or better. These are: Fiber, AFIO, Dl. The second category is libraries where the authors have been visible enough for me to review the library and score it onto the dashboard. These are: BindLib, Expected, Hana, Tick, Fit. ... of which BindLib, Expected and Hana are the most "Boost ready" by my estimation. I still haven't reviewed Sqlpp11, SIMD, Dispatch, Range v3, Spirit X3 nor Proto 0x. The main reason why not is that I would never use any of those libraries in any work I expect to do anytime in the next five years. That's quite unfair to those libraries, but I have another big reason: I'm also hesitant to review libraries covered by their authors also present at C++ Now, or have presented on them in the past, as it won't add value plus I probably wouldn't know what I'm talking about compared to them so that removes Expected?, Hana, SIMD, Dispatch, Range v3, Spirit X3 and Proto 0x. Which leaves a shortlist of: Fiber, AFIO, Dl, BindLib, maybe Expected, maybe Tick and Fit. I think SIMD and Dispatch have been presented on before at C++ Now right? Could anyone also very quickly summarise the main differences in their C++ 11 only rewrite? I think I remember it was mainly compilation speed rather than doing anything unusually C++ 11 only? Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

4 4

[peer review queue tardiness] Cleaning out the Boost review queue
by Niall Douglas 10 Apr '15

10 Apr '15

I've been reviewing the Boost Formal Review queue as part of preparing my C++ Now presentation and I observe the following things: Observation 1. The following review submissions have not been updated by their authors in over two years and therefore count as unmaintained. Abandoned libraries before peer review are even more undesirable than abandoned official Boost libraries, I therefore suggest they be removed from the review queue until their authors bring them up to date: * Join (last update 2009) * Block pointer (last update: well, it's still in the SVN sandbox) * Singularity (last update 2011) * Extended Complex Numbers (last update 2012) * Array (last update 2012) * Countertree (last update 2012, I see a github import in 2013 but no new commits) * Process (last update 2012). This is a particularly useful library I have used myself in production code, and I see a number of mirrors of it on github each with varying patches and bug fixes. As a minimum, somebody needs to create a canonical github project for Process and merge the fixes from the many github copies. Otherwise, I'm sorry but this library needs to be considered abandoned otherwise, and removed from the review queue. It may be the case that the links on the review queue wiki page are simply out of date. If so, they need to be updated. Otherwise a purge of the queue is very desirable such that the queue accurately reflects ready to use new Boost libraries. Observation 2: Edit Distance (Algorithm) by Erik Erlandson shouldn't be in the queue. What he's done is to add a new algorithm to Boost.Algorithm, so the maintainer for Algorithm (Marshall?) should either merge his contribution or reject it as inappropriate or badly implemented. Failing that, Edit Distance should be spun into a standalone library instead of forking Algorithm. Right now it is supplied quite literally as a fork of the algorithm github. It should be a pull request, yet I don't see it in the pull requests for boostorg/algorithm, neither open nor closed. Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/

15 43

[AIX6.1] [64bit] [build boost 1.57] Help required to build boost
by 임영운 10 Apr '15

10 Apr '15

hi, I'm newbie. the only one thing that I wanted to ask is building boost 64bit on aix6.1. I try it a number of times. and I failed building 64bit boost objects. It built only 32bit objects. would you tell me how to build boost 64bit on aix6.1 thanks read this msg. 주식회사 테미 임영운(Yeong-woon Im) 305-764 대전광역시 유성구 대학로99 충남대학교 산학연교육연구관 807호 #807, TBI Center, Chungnam University 99 Daehak-ro, Yuseong-gu, Deajeon, 305-764 Korea Home URL : http://www.temee.co.kr Tel : 042-824-7014 Fax : 042-824-7015 Mobile : 010-6266-9960

2 1

Re: [boost] [Boost-users] 1.58.0 rc3 is now available
by Marshall Clow 09 Apr '15

09 Apr '15

On Thu, Apr 9, 2015 at 4:11 AM, Deniz Bahadir <dbahadir(a)benocs.com> wrote: > Building Boost 1.58.0-rc3 succeeded only partially. > > > Success: > > Debian 7 with GCC 4.8.2 (in C++03 mode) with build-command: > b2 -j4 --build-dir=/opt/build/test --build-type=complete > --layout=versioned address-model=64 architecture=x86 install > --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" > cxxflags="-fPIC" dll-path="/opt/test/lib/x86_64-linux-gnu" > > > Failure: > > Debian 7 with GCC 4.8.2 (in C++11 mode) with build-command: > b2 -j4 --build-dir=/opt/build/test --build-type=complete > --layout=versioned address-model=64 architecture=x86 install > --prefix="/opt/install/test" toolset=gcc-4.8 cflags="-fPIC" cxxflags="-fPIC > -std=c++11" dll-path="/opt/test/lib/x86_64-linux-gnu" > > > The main-error seems to come from "Boost.Context" and the use of unknown > "std::index_sequence": > > std::index_sequence is a C++14 feature. -- Marshall

1 0

[language] determine sence of language proposal concerning the 'default'-keyword
by Jakob Riedle 09 Apr '15

09 Apr '15

Hello boost community, since this seems to me kind of a proving ground for new C++ library/language features I'd ask this question here. Would you recon' writing a language proposal about: using the 'default'-keyword as some standard way of calling the default ctor of variables. I could imagine the following use-case: void foo( some::very_long_name<some_very_long_template_param> arg = default ){ return; } This would make things shorter, in the way 'auto' does it for types. You could also do it for passing parameters: foo( default ); This could interact very well with boost::optional, make it more intuitive and easier to use: optional<int> bar( optional<some_long_type_name> arg = default ){ return default; } bar( default ); This way, you don't have to write 'optional<some_long_type_name>()', both at the parameter and at the function call. What do you think of such a language proposal? Regards, Jakob Riedle

5 5

[MinGW] [Windows] [build boost 1.57] Help required to build boost
by Abhinav Tripathi 08 Apr '15

08 Apr '15

I had submitted a GSoC application regarding developing a document library for boost and i wanted to do something regardless of the results of selection. . SO, i downloaded boost 1.57 source and tried to build it using MinGW compiler that i downloaded with CodeBlocks IDE which i use. When i ran : bootstrap.bat gcc I got error "Failed to build Boost.Build Engine". . The bootstrap.log file was : ### ### Using 'gcc' toolset. ### E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>if exist bootstrap rd /S /Q bootstrap E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>md bootstrap E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>gcc -DNT -o bootstrap\jam0.exe command.c compile.c constants.c debug.c execcmd.c execnt.c filent.c frames.c function.c glob.c hash.c hdrmacro.c headers.c jam.c jambase.c jamgram.c lists.c make.c make1.c object.c option.c output.c parse.c pathnt.c pathsys.c regexp.c rules.c scan.c search.c subst.c timestamp.c variable.c modules.c strings.c filesys.c builtins.c md5.c class.c cwd.c w32_getreg.c native.c modules/set.c modules/path.c modules/regex.c modules/property-set.c modules/sequence.c modules/order.c E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>.\bootstrap\jam0 -f build.jam --toolset=gcc "--toolset-root= " clean ...found 1 target... ...updating 1 target... ...updated 1 target... E:\Prog Stuff\boost_1_57_0\tools\build\src\engine>.\bootstrap\jam0 -f build.jam --toolset=gcc "--toolset-root= " ...found 159 targets... ...updating 3 targets... [MKDIR] bin.ntx86 'C:\Users\Abhinav' is not recognized as an internal or external command, operable program or batch file. md "bin.ntx86" ...failed [MKDIR] bin.ntx86... ...skipped b2.exe for lack of bin.ntx86... ...skipped bjam.exe for lack of b2.exe... ...failed updating 1 target... ...skipped 2 targets... . . I am NOT any expert but as far as i can guess, it tried to execute "C:\Users\Abhinav" which ofcourse is NOT any valid command... . How can i build boost? Is there a way to use it without actually building the source? Please help! . Regards, Abhinav

2 2

Is boost.python dead?
by Mikhail Matrosov 08 Apr '15

08 Apr '15

Hello, I made a pull request for boost.python: https://github.com/boostorg/python/pull/15 Two weeks passed since then and I had no reaction still. Did I do something wrong? I see no pulse for the project. Is it alive? Is there a way to find out its status? The last meaningful commit is dated back to 7 Dec 2012. ----- Best regards, Mikhail Matrosov

5 7

[flat_map] Any interest in a flat_map variant that is much faster on insertion/erase at the price of a slower lookup?
by Giacomo Drago 08 Apr '15

08 Apr '15

Hi My library is not ready for a formal review process, and I'd like to ask whether there is some potential interest first, thus saving everybody a lot of time. I have been working on a flat_map (http://www.boost.org/doc/libs/1_57_0/doc/html/boost/container/flat_map.html) variant that keeps some of the distinctive features of the original one (contiguous storage/cache friendliness, zero memory overhead/shrink_to_fit support, vector-based representation, etc...) but makes insertion and erasure of the elements much faster, at the price of a slower lookup and in-order traversal. Explaining how it works requires time and it's not really necessary if there is no interest in the first place (e.g. "thanks, but we have no use for this"). Let's get straight to the benchmarks and to some conclusions. #elems: 50000 std::map: Random insertion: 18.605 ms Random find: 24.382 ms Iteration: 5.658 ms Random erase: 37.166 ms experimental::flat_map: Random insertion: 400.141 ms Random find: 12.352 ms Iteration: 7.099 ms Random erase: 467.051 ms boost::container::flat_map: Random insertion: 611.678 ms Random find: 6.293 ms Iteration: 0.038 ms Random erase: 615.311 ms #elems: 200000 std::map: Random insertion: 146.394 ms Random find: 163.506 ms Iteration: 21.973 ms Random erase: 225.314 ms experimental::flat_map: Random insertion: 5068.93 ms Random find: 65.618 ms Iteration: 34.244 ms Random erase: 6851.09 ms boost::container::flat_map: Random insertion: 10696.9 ms Random find: 43.896 ms Iteration: 0.254 ms Random erase: 10604 ms Of course one doesn't expect the random insertion to have a performance that is comparable to the one of a tree-based map, like std::map. However, my experimental::flat_map provides a better trade-off than boost's flat_map for me, as random insertion is massively faster and in the big picture of the application I am developing this is making a hell of a difference. Am I making any sense? Shall I polish the implementation, publish it, and submit a proposal? I'd really appreciate your feedback. Kind Regards Giacomo

8 37

1.58.0 rc2 is now available
by Marshall Clow 07 Apr '15

07 Apr '15

Release candidate files for 1.58.0 are available at: http://boost.cowic.de/rc/ Since rc1, the changes that were causing the serialization libraries to fail to build on MSVC have been reverted. 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_58_0_rc2.7z) = 43e0d47cc9f5f2a07761808b9da57c0a MD5 (boost_1_58_0_rc2.tar.bz2) = 52147381c97685eb045b5b022ad51a35 MD5 (boost_1_58_0_rc2.tar.gz) = cb33afaa557dea2f700bffec8a91d87e MD5 (boost_1_58_0_rc2.zip) = 412676a9a7d9903eb5a260209ad78f0a Thanks! -- The release managers P.S. Release notes are here: http://www.boost.org/users/history/version_1_58_0.html

6 5

Re: [boost] [SORT] Parallel Algorithms
by Francisco José Tapia 07 Apr '15

07 Apr '15

Hi , In the file of this link, in my dropbox space, you have the code, the test programs and the benchmarks with GCC. https://dl.dropboxusercontent.com/u/8437476/works/sort/Sort_V0.1.7z *FILE DESCRIPTION* In the root folder of the file you have a INSTRUCTIONS.txt file detailing the content of all the folders of the file, information for to compile the programs, where is each file, and which options and libraries you must link. *Test* Contains the test programs of each class and algorithms. *Src* Contains the source code of all. In the folder *src/boost/sort* there is a file *algorithm.hpp*, which is the only include file needed for invoke the algorithms. The parallel algorithms have a parameter of the NThread type which indicate the number of threads to use. By default use the same number than the HW threads of the machine. it's a very simple structure defined in boost/sort/util/atomic.hpp. *Benchmarks* In this folder are the benchmark code with GCC compiler under Linux x64. In the future I will add benchmarks with other compiler and Operating Systems. The folders *cpp-TimSort-master*, and *parallel_stable_sort* have the C++ code of the TimSort algorithm, found in https://travis-ci.org/gfx/cpp-TimSort, and the code of the sample sort with TBB. The code had been modified, due to the four versions use the same name space and many common names, and was not possible invoke the four versions in the same program. The modification put each version in a different name space. In the folder *GCC*, you can find 3 folders - *algorithm* : Have the code of the benchmark programs - *bin *: have the compiled and static linked version of the benchmark programs. In this folder you have a shell run.sh which run sequentially the programs and collect the results obtained in .txt files with the same name than the program - *Results *: in this folder you can find the result generated by the benchmark programs on different machines. Each machine have a folder where you can find the text files with the same name than the programs with the results, and a description.txt file with the description of the HW where run the benchmarks. The format used in this folder is the suggested for to present the results of all the machines used in the test. Here you have the result of my two computers, and can have a first idea about the results expected in other machines. The benchmarks, like in the old version, have a version with 64 bits numbers, and a version with objects of several sizes. About the memory used for of the algorithms. If you consider M the memory used by the data, the total memory used by the algorithms are : - GCC sort → M - boost sort → M - GCC parallel_sort → M - boost parallel_sort → M - TBB parallel_sort → M - GCC stable_sort → 2 M - boost stable_sort → 1.5 M - TimSort -> 2M - GCC parallel_stable_sort → 2.5 M - TBB parallel_sort → 2 M - boost sample_sort → 2 M - boost parallel_stable_sort → 1.5 M The algorithms use the indirect version when the size of the objects is greater than 128 bytes. I am speaking with several friends, for to run the benchmarks in more powerful machines. I think, the first is to check the speed. If the speed is good, we have something useful , if not, we must decide what must do with this. If something is useful , or we must leave all. If we decide continue, the next steps to do are : Reorganize the benchmark, and include benchmarks with string objects. Your idea about the use of files, I thing is the correct way to follow Finish all the documentation of the code for to generate a Doxygen documentation Generate the web pages of documentation for the Boost project Modify the test programs for to do according the bjam files If you found any problem , error or doubt, please , contact me for to resolve Francisco

7 16

[align] Conflicts during git pull
by Andrey Semashev 06 Apr '15

06 Apr '15

Hi, When updating my local copy 'git pull' failed on Boost.Align with the following error: git pull Auto-merging test/is_aligned_test.cpp CONFLICT (add/add): Merge conflict in test/is_aligned_test.cpp Auto-merging test/aligned_delete_test.cpp CONFLICT (add/add): Merge conflict in test/aligned_delete_test.cpp Auto-merging test/aligned_allocator_test.cpp CONFLICT (add/add): Merge conflict in test/aligned_allocator_test.cpp Auto-merging test/aligned_allocator_adaptor_test.cpp CONFLICT (add/add): Merge conflict in test/aligned_allocator_adaptor_test.cpp Auto-merging test/aligned_alloc_test.cpp CONFLICT (add/add): Merge conflict in test/aligned_alloc_test.cpp Auto-merging test/align_test.cpp CONFLICT (add/add): Merge conflict in test/align_test.cpp Auto-merging test/Jamfile.v2 CONFLICT (add/add): Merge conflict in test/Jamfile.v2 Auto-merging meta/libraries.json CONFLICT (add/add): Merge conflict in meta/libraries.json Auto-merging index.html CONFLICT (add/add): Merge conflict in index.html Auto-merging include/boost/align/is_aligned.hpp CONFLICT (add/add): Merge conflict in include/boost/align/is_aligned.hpp Auto-merging include/boost/align/detail/max_count_of.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/max_count_of.hpp Auto-merging include/boost/align/detail/max_align.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/max_align.hpp Auto-merging include/boost/align/detail/is_alignment.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/is_alignment.hpp Auto-merging include/boost/align/detail/is_aligned.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/is_aligned.hpp Auto-merging include/boost/align/detail/alignment_of.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/alignment_of.hpp Auto-merging include/boost/align/detail/aligned_alloc_sunos.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/aligned_alloc_sunos.hpp Auto-merging include/boost/align/detail/aligned_alloc_posix.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/aligned_alloc_posix.hpp Auto-merging include/boost/align/detail/aligned_alloc_msvc.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/aligned_alloc_msvc.hpp Auto-merging include/boost/align/detail/aligned_alloc_macos.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/aligned_alloc_macos.hpp Auto-merging include/boost/align/detail/aligned_alloc_android.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/aligned_alloc_android.hpp Auto-merging include/boost/align/detail/aligned_alloc.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/aligned_alloc.hpp Auto-merging include/boost/align/detail/align_cxx11.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/align_cxx11.hpp Auto-merging include/boost/align/detail/align.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/align.hpp Auto-merging include/boost/align/detail/addressof.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/addressof.hpp Auto-merging include/boost/align/detail/address.hpp CONFLICT (add/add): Merge conflict in include/boost/align/detail/address.hpp Auto-merging include/boost/align/aligned_delete_forward.hpp CONFLICT (add/add): Merge conflict in include/boost/align/aligned_delete_forward.hpp Auto-merging include/boost/align/aligned_delete.hpp CONFLICT (add/add): Merge conflict in include/boost/align/aligned_delete.hpp Auto-merging include/boost/align/aligned_allocator_forward.hpp CONFLICT (add/add): Merge conflict in include/boost/align/aligned_allocator_forward.hpp Auto-merging include/boost/align/aligned_allocator_adaptor_forward.hpp CONFLICT (add/add): Merge conflict in include/boost/align/aligned_allocator_adaptor_forward.hpp Auto-merging include/boost/align/aligned_allocator_adaptor.hpp CONFLICT (add/add): Merge conflict in include/boost/align/aligned_allocator_adaptor.hpp Auto-merging include/boost/align/aligned_allocator.hpp CONFLICT (add/add): Merge conflict in include/boost/align/aligned_allocator.hpp Auto-merging include/boost/align/aligned_alloc.hpp CONFLICT (add/add): Merge conflict in include/boost/align/aligned_alloc.hpp Auto-merging include/boost/align/align.hpp CONFLICT (add/add): Merge conflict in include/boost/align/align.hpp Auto-merging include/boost/align.hpp CONFLICT (add/add): Merge conflict in include/boost/align.hpp Auto-merging example/make_aligned.hpp CONFLICT (add/add): Merge conflict in example/make_aligned.hpp Auto-merging example/aligned_vector.hpp CONFLICT (add/add): Merge conflict in example/aligned_vector.hpp Auto-merging example/aligned_ptr.hpp CONFLICT (add/add): Merge conflict in example/aligned_ptr.hpp Auto-merging doc/align.qbk CONFLICT (add/add): Merge conflict in doc/align.qbk Auto-merging doc/Jamfile.v2 CONFLICT (add/add): Merge conflict in doc/Jamfile.v2 Auto-merging README.md CONFLICT (add/add): Merge conflict in README.md Automatic merge failed; fix conflicts and then commit the result. This is on the master branch. I didn't modify my local copy of Boost.Align, so there must have been some weird change upstream that cannot be merged automatically. Does anyone know why this happens? For now I just reset my local branch to be equal to the remote master, but this kind of problem happened before and it breaks my update scripts.

2 1

Call for Papers for Meeting C++ 2015 ends on Wednesday
by Jens Weller 05 Apr '15

05 Apr '15

Hello Boost & Qt Community, the call for papers for this years Meeting C++ Conference got extended and ends on Wednesday(April 8th) next week! Especially talks about libraries have still a good chance to get voted into the conference, and also the embedded theme track! CfP announcement: http://meetingcpp.com/index.php/newsreader/items/call-for-papers-for-meetin… The voting will begin shortly after the end of the CfP and run ~10 days, this will give me guidance to select the right talks for this years conference! thanks, Jens Weller

1 0

Equivalent of boost-commits?
by Steven Watanabe 05 Apr '15

05 Apr '15

AMDG I used to subscribe to boost-commits under svn. I couldn't find any way to set this up under github. Also, does anyone know how to subscribe to all repositories, without having to handle each repository individually? In Christ, Steven Watanabe

1 0

Messages from list marked as spam
by Olaf van der Spek 03 Apr '15

03 Apr '15

Hi, Email from certain people on the list is marked as spam by gmail: "Why is this message in Spam? It has a from address in teamviewer.com but has failed teamviewer.com's required tests for authentication. " Is there a problem with the setup of this mailing list? -- Olaf

9 15

[sync] Needs a 'master' branch
by Edward Diener 03 Apr '15

03 Apr '15

I created a Github issue that the sync library needs a 'master' branch, even if its just the current 'develop' branch. Please let's get this done. It is more than just irritating that: git submodule foreach --recursive git checkoout master stops and fails because a Boost library does not have a 'master' branch.

2 1

[where to start][got work for me?][newbee][can I help with something?]
by vivek dhiman 03 Apr '15

03 Apr '15

Hello all So I am not sure what's gonna happen to my GSoC application. But as this is my last sem(probably last chance to learn), I guess I can start doing some work anyways. May be 1 to 2 hours per weekday and 3-4 during the weekends. Is there some work that someone wants me to do? I am new to this. So I actually have no idea how to ask/start. But I am happy to be involved. Sorry if it is considered as spam. I am ready to learn and make mistakes. Thanks Vivek

2 1

[VS++ 2015 CTP 6] [build] Workaround for Visual Studio 2015 CTP 6 Preview breaking Boost.Build
by Beman Dawes 02 Apr '15

02 Apr '15

If you have previously been running Boost.Build on toolset=msvc-14.0 (Visual Studio 2015 Preview), installing CTP 6 causes some bjam/b2 builds to fail because of missing include files. What's happening is that Boost.Build caches several files in C:\Users\<name>\AppData\Local\Temp. For my installation these files are: b2_msvc_14.0_vcvarsall_x86.cmd b2_msvc_14.0_vcvarsall_x86_amd64.cmd b2_msvc_14.0_vcvarsall_x86_arm.cmd but the introduction of the new universal runtime stuff in CTP 6 added some additional paths to vcvarsall, so the cached files are no longer correct. The workaround is to simply delete the b2_msvc_14.0_vcvarsall* temporary files. The next time bjam/b2 is run correct versions of the files will be regenerated. --Beman

1 0

[rational] Can the community maintenance team and/or rational users please review some pull requests?
by John Maddock 02 Apr '15

02 Apr '15

I have a bunch of PR's against Rational, which of course is basically unmaintained. I'd be grateful if a second pair of eyes (at least) could take a look before I start agitating for someone to merge them ;) Each of the four, builds on the previous one(s). Three are basically trivial: https://github.com/boostorg/rational/pull/1/files https://github.com/boostorg/rational/pull/2/files https://github.com/boostorg/rational/pull/3/files The final one is much more complex, and disables "accidental" conversion from float to rational (which otherwise proceeds via truncation to integer first). As you can see from the commit history, I've had quite a few attempts at getting the final one correct. I believe it is now, doesn't break anything in Boost except, as noted in the discussion, Boost.Geometry, which relies on an unsafe float to rational conversion - Geometry's authors are aware of the issue here: https://github.com/boostorg/geometry/commit/c992eb61e8ef9e90fdae403ac6ff1ee…. So.... I'm interested in both eyeball-look-throughs from seasoned Boosters, but also feedback from Rational's users, and verification that it doesn't break end user code - other than unsafe conversions of course. If you just want the updated header to test, you can grab it from here: https://raw.githubusercontent.com/jzmaddock/rational/no-float-convert/inclu… Many thanks! John.

5 8

MPL and MPL core
by Edward Diener 02 Apr '15

02 Apr '15

Were the changes to MPL splitting it between a core and the rest of MPL supposed to be part of the upcoming release ? Because looking at MPL the 'master' branch is at the previous 1.57 release and there have been quite a number of changes to the 'develop' branch since then, much of it relating to the mpl/core split. The 'develop' regression tests for MPL look pretty green. I would like to get bruno Dutra's fix for MPL arity into the coming release as it has been thoroughly tested on 'develop', but I do not know whether or not all the other MPL 'develop' changes should go in 'master' although I suspect not.

11 20

questions regarding GCC visibility
by Robert Ramey 02 Apr '15

02 Apr '15

I made a few changes to simplify code in the serialization library. This entailed eliminating support for borland compilers, workarounds for compilers which fail to support partial specialization of template function and some general clean up. In the course of this effort, I had occasion to simplify the code which supports Auto linking - and by extension visibility. Things seemed to go pretty well. Feeling frisky, I added the switch -fvisibility=hidden to the gcc compile of library. Now applications won't link for lack of certain symbols. Well, they link and run fin on my machine here at home- but fail in the test matrix. http://www.boost.org/development/tests/develop/developer/output/Debian-Sid-… Funny thing is: doesn't seem to be a problem on my machine doesn't seem to occur with all exported symbols - only select ones - often but not always desctructors I can switch Jamfile back so it doesn't specify -fvisibility=hidden, but it seems that I'm really close to being able to generate a smaller, cleaner DLL which I would prefer to do. Any constructive suggestions would be appreciated. On a related note, it seems to me that http://www.boost.org/development/separate_compilation.html should be updated to explain BOOST_SYMBOL_EXPORT and BOOST_SYMBOL_IMPORT which are convenient for simplifying the auto-linking and visibility functionality. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/questions-regarding-GCC-visibility-tp467… Sent from the Boost - Dev mailing list archive at Nabble.com.

5 10

Boost 1.58.0rc1 release delayed
by Marshall Clow 01 Apr '15

01 Apr '15

Due to some problems in Boost.Test, and some unexpected doctor's visits (which delayed said problems getting fixed), the boost 1.58.0rc1 scheduled for today has been delayed until Friday. As a result, the "master" branch in git is still open for bug fixes (if they have been successfully tested on develop) and documentation fixes until 11:59 PM PDT Thursday night (4/2). Sorry for the delay. -- Marshall

2 1

what happened to the "tools/regression" directory - and the stuff in it?
by Robert Ramey 01 Apr '15

01 Apr '15

The tools in the tools/regression directory are critical to the testing of the serialization library on one's local machine. What happened to these. Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/what-happened-to-the-tools-regression-di… Sent from the Boost - Dev mailing list archive at Nabble.com.

9 26

[boostorg/regression] Build instructions updated for developers local test reporting
by Beman Dawes 01 Apr '15

01 Apr '15

A README file has been added and index.html updated to aid developers wishing to use these tools for local testing. While these tools are not worthwhile for a small number of tests run against a single variant of a single compiler, they are invaluable for large test matrices. See develop branch at https://github.com/boostorg/regression HTH, --Beman

2 1

Test message testing gsoc-admin@boost.org, please ignore
by Niall Douglas 01 Apr '15

01 Apr '15

Second attempt at getting this to work ... --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

1 0

[log] [asio] Conflicting default configs
by Andrey Semashev 01 Apr '15

01 Apr '15

Hi, In Boost.Log I'm using Boost.ASIO to implement network-based syslog backend. Boost.ASIO is used in the compiled part of Boost.Log and, obviously, can be used in the user's code as well. By default Boost.ASIO is header-only, so we basically have a copy of Boost.ASIO in Boost.Log and another copy in the user's app. In Boost.Log I have the option to enable compiler-based TLS at the library build stage (BOOST_LOG_USE_COMPILER_TLS macro), which is by default not enabled. In Boost.ASIO there is a similar option (BOOST_ASIO_DISABLE_THREAD_KEYWORD_EXTENSION macro) but the feature is enabled by default. I want Boost.Log built libraries to actually respect the BOOST_LOG_USE_COMPILER_TLS option, so I define BOOST_ASIO_DISABLE_THREAD_KEYWORD_EXTENSION internally when BOOST_LOG_USE_COMPILER_TLS is not defined. The problem is that Boost.ASIO changes implementation in an incompatible way when BOOST_ASIO_DISABLE_THREAD_KEYWORD_EXTENSION is defined. It is further worsened by a recent change that makes all of Boost.ASIO symbols externally visible. Basically, this means hard to debug trouble on user's end, when different versions of Boost.ASIO (one from Boost.Log binaries and the other used by the user's code directly) are used at the same time. I'd like to ask community what is the preferred resolution of this situation (and possibly similar ones in the future). I can see several ways of tackling this: 1. Introduce an inline ABI namespace in Boost.ASIO, much like the one I have in Boost.Log. The namespace name would depend on BOOST_ASIO_DISABLE_THREAD_KEYWORD_EXTENSION and other macros that affect binary compatibility. This would be my preferred solution, although I'm not sure how fast and easy it can be implemented. 2. Remove symbol visibility enforcement from Boost.ASIO, or at least make it optional. That way I could encapsulate my private copy of Boost.ASIO in Boost.Log binaries. 3. Change the defaults, either in Boost.Log or in Boost.ASIO, so that they are aligned by default. When the user changes Boost.Log config he would be expected to know that Boost.ASIO config also needs to be changed accordingly. If he doesn't, Boost.Log is still built consistently with its own config. Note, however, that since Boost.Log is a built library and in most distributions it is built with default options, the choice for Boost.Log is more significant and because of that should probably be more conservative. 4. Same as 3 but also remove the enforcement of Boost.ASIO config by Boost.Log. Whenever the user wants to change the default, he would have to define macros for the both libraries, otherwise Boost.Log can be built inconsistently. 5. Do not change the defaults but remove the config enforcement. BOOST_LOG_USE_COMPILER_TLS becomes Boost.Log-local and as such does not guarantee that the resulting binaries do not in fact use compiler-based TLS. Users can get surprised. 6. Do not change anything, let the users suffer because of ODR issues. Maybe document this somewhere... Opinions?

5 11

[serialization][release][teeks99] All MSVC tests for Boost.Serialization failing?
by Joaquín M Lopez Munoz 31 Mar '15

31 Mar '15

Hi All teeks99-* regression tests for Boost.Serialization in MSVC compilers appear as failing, yet when one clicks on any the information seems to indicate nothing went wrong: http://tinyurl.com/nf5bd9a Any clue? Thank you Joaquín M López Muñoz Telefónica

3 4

Transferring a library on Github
by Edward Diener 31 Mar '15

31 Mar '15

In order to get VMD under boostorg in order to begin the process of integrating the library into Boost for the release after the current pending one I tried to transfer the library as explained on the page https://svn.boost.org/trac/boost/wiki/NewLibFromGit. But I do not have the necessary admin rights for boostorg. How do I proceed ? I want to get VMD under boostorg and then do whatever is necessary to add it to the superproject and have it part of for regression testing.

2 4

[detail] Bug in is_postfix_incrementable
by Edward Diener 31 Mar '15

31 Mar '15

There is a rather bad bug in is_postfix_incrementable in the detail/is_incrementable.hpp header file. I noticed this when I was looking at how I can remove the dependncies in is_incrementable.hpp on the deprecated Type_traits header files in Version2 of type_traits. The bug looks totally obvious to me. It's that the is_postfix_incrementable metafunction is derived from the is_incrementable_::impl<T> implementation rather than the is_incrementable_::postfix_impl<T> implementation. I am sure this was just a copy-paste problem but evidently has been in the header file from the beginning. Can we fast forward the simple fix to the new release ? I posted this just to be sure I haven't missed anything in the file. I believe that only the iterator library currently uses the is_incrementable and is_postfix_incrementable metafunctions in its tests. Since it is Boost detail no end-user should be using it. Still we should have it correct, shouldn't we, in our release ?

1 0

Conflicts when building libraries at root
by Peter Dimov 31 Mar '15

31 Mar '15

On Windows, at least, when I do ./b2 toolset=msvc-8.0 at Boost root, I get error: Name clash for '<pstage\lib>libboost_system-vc80-mt-gd-1_58.lib' error: error: Tried to build the target twice, with property sets having error: these incompatible properties: error: error: - <warnings>all error: - <address-model>32 <architecture>x86 <warnings>on When I add --without-context --without-coroutine, I now get error: Name clash for '<pstage\lib>libboost_system-vc80-mt-1_58.lib' error: error: Tried to build the target twice, with property sets having error: these incompatible properties: error: error: - <asynch-exceptions>off error: - <asynch-exceptions>on So I add --without-test. error: Name clash for '<pstage\lib>libboost_timer-vc80-mt-1_58.lib' error: error: Tried to build the target twice, with property sets having error: these incompatible properties: error: error: - <asynch-exceptions>on <library>object(file-target)@10959 error: - <asynch-exceptions>off <library>object(file-target)@9953 Now where did _that_ come from. :-) Ah. --without-endian. Builds now. This is perhaps old news for some, but it looks like it doesn't play well with our simple build instructions. Or maybe it doesn't occur on the master branch, so we don't care? I haven't checked yet. It's also perhaps an indication of a deeper problem. I can use b2 --with-test and have 'test' built; it builds its dependencies (system, chrono and timer) with <asynch-exceptions>on in bin.v2, and if I use it from within Boost.Build, it will link to them. But if I stage (or install) Boost.Test, and then stage or install Boost.System separately, Boost.System will be built with <asynch-exceptions>off. So the library user who just has headers and binaries will link those, potentially creating a conflict, which may in this case be benign. Or not.

12 55

[Container] const boost::container::vector is mutable??
by Eric Niebler 31 Mar '15

31 Mar '15

Why are the elements of a const boost::vector mutable through its const_iterator? #include <boost/container/vector.hpp> int main() { using C = boost::container::vector<int>; C c{1,2,3,4}; C const & r = c; r[0] = 42; // Error, good. *r.begin() = 42; // Compiles! huh?? } -- Eric Niebler Boost.org http://www.boost.org

2 3

how to contact iterator developers
by Claas H. Koehler 31 Mar '15

31 Mar '15

Hi! About a week ago I sent a question about a specific bug to the iterator developers via this list and haven't received any feedback yet. Is this list not the right place to ask such questions or are there currently no active iterator developers managing the project ? Regards Claas

3 3

Release deadlines
by Marshall Clow 30 Mar '15

30 Mar '15

Just a reminder that we’re coming up on a release; and if you have changes that you want to see in the release (I know *I* do), you should get them in ASAP. Check them into develop, and then, once the tests have cycled successfully, merge them to master. Please do not merge anything to master w/o permission from the release managers after the start of April (11:59 PM next Tuesday PDT). Also, if you know of problems with the current state of the master branch that would preclude releasing it, please let us know (preferably *before* next Wednesday). Thanks for your help with the releases. — Marshall & the rest of the release managers.

7 9

[serialization] Passing literals to oarchive
by Bjorn Reese 30 Mar '15

30 Mar '15

Currently we cannot pass literals directly to an oarchive like this: oarchive << 42; since compilation fails in interface_oarchive.hpp, as the operator<< only takes parameters by reference. We can remedy this by changing operator<< to take the parameter by const-ref instead, as show below. Is there any reason not to do this? --- a/include/boost/archive/detail/interface_oarchive.hpp +++ b/include/boost/archive/detail/interface_oarchive.hpp @@ -59,7 +59,7 @@ public: } template<class T> - Archive & operator<<(T & t){ + Archive & operator<<(const T & t){ this->This()->save_override(t, 0); return * this->This(); }

3 9

[mpl] Is BOOST_MPL_PP_TOKEN_EQUAL publicly usable ?
by Damien Buhl 30 Mar '15

30 Mar '15

Dear Boost.MPL developers, I was coming up to something really similar to BOOST_MPL_PP_TOKEN_EQUAL ( http://www.boost.org/doc/libs/1_57_0/boost/mpl/aux_/preprocessor/token_equa… ) in Boost.Fusion to fix warnings that my changes generate in MSVC 8 ( As discussed on this list as *[boost] MSVC warnings for BOOST_PP_IS_EMPTY in Boost.Phoenix* ) Instead of having a second implementation of the same macro within Boost.Fusion, is it ok if I use BOOST_MPL_PP_TOKEN_EQUAL from MPL ? I'm asking this because it isn't documented anywhere and is in mpl/include/boost/mpl/aux_/preprocessor/token_equal.hpp which sounds like a private header. Possibly there are reasons for not being documented ? Cheers, -- Damien Buhl

2 2

Re: [boost] [Locale] Boost.Locale cannot Run in Visual Studio 2010
by Artyom Beilis 30 Mar '15

30 Mar '15

> >I have been trying to learn Boost.Locale Module. Consider this >http://www.boost.org/doc/libs/1_55_0/libs/locale/doc/html/conversions_8cpp-… >example. The code gets successfully compiled but when I try to run it, it >gives the error > >Unhandled exception at 0x74d34b32 in LearningCPP.exe: Microsoft C++ >exception: std::bad_cast at memory location 0x00a6fa48.. > >I have attached the stack-trace of the program also. Here it is: > > [snip] > > Did anyone faced this issue when using Boost.Locale in Visual Studio 2010? > If so, how do I resolve this issue? 1. Do you use latest version of MSVC or public beta (there was facet related bug there)2. Make sure you don't mix debug and release code (which can be very likely stuff there) on both boost and its dependencies (icu if you use one) Artyom Beilis -------------- CppCMS - C++ Web Framework: http://cppcms.com/ CppDB - C++ SQL Connectivity: http://cppcms.com/sql/cppdb/

2 1

[GSOC] Request for proposal review and feedback
by Divyansh Gupta 30 Mar '15

30 Mar '15

Hi BOOST, I had submitted my proposal for the enhanced vector and deque project on 17th March, but I haven't received any comments yet. It would be great if I could get some feedback on the proposal, so that I can make any necessary changes while that's allowed. Thanks a lot. Regards, Divyansh Gupta PS- Here's the link to the proposal: https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015…

1 0

[thread] Alternate future implementation and future islands.
by Giovanni Piero Deretta 29 Mar '15

29 Mar '15

[cc'ing a few of the participants of the old thread] Hi All, Back in January, there was an interesting long thread about the problem of interoperation between futures of different libraries and the ability wait for heterogeneous futures. Different solutions were discussed like standardizing the future shared state or having an unified kernel wait object. I just wanted to share my attempt on a solution on the problem. The code can be found at https://github.com/gpderetta/libtask/blob/master/future.hpp (other interesting files are shared_future.hpp event.hpp and tests/future_test.cpp). It is an implementation a subset of the current boost and std future interface. In particular it has promise, future, shared_future, future::then, wait_any, wait_all. Most important missing piece are timed waits (for lack of, ahem, time, but should be easy to implement). The implementation requires c++14 and is only lightly tested, it should be treated as a proof of concept, not production-ready code. A few key design points: * The wait strategy is not part of the future implementation (although a default is provided). future::get, future::wait, wait_all and wait_any are parametrized by the wait strategy. * The design aims to streamline and make as fast as possible future and promise at the cost of a slower shared_future (although there is room for improvement). * The wait strategy only deals with 'event' objects, which act as a bridge between the future and the promise. The event object is really my the core of my contribution; it can be thought of as the essence of future<void>::then; alternatively it can be seen as a pure user space synchronization primitive. Other features of this implementation: * Other than in the blocking strategy itself, the future and promise implementation have no sources of blocking (no mutexes, not even spin locks). * The shared state is not reference counted. To demonstrate the generality of the waiting concept, I have implemented a few waiter objects. * cv_waiter: this is simply a waiter on top of an std::mutex + cond var. * futex_waiter (linux): an atomic counter + a futex, possibly more efficient than the cv_waiter * sem_waiter (posix): a waiter implemented on top of a posix semaphore. More portable than the futex waiter and possibly more efficient than the cv_waiter * fd_waiter(linux, possibly posix): a waiter implemented on top of linux eventfd (for portability it can also be implemented on top of a pipe); you can use select with futures! * task_waiter: a completely userspace based coroutine waiter which switches to another coroutine on wait and resumes the original coroutine on signal. * scheduler_waiter: another coroutine based waiter, but on top of an userspace task scheduler. On wait switch to the next ready task, on signal enqueue the waiting task to the back of the ready queue. I know that there is a plan to reimplement a new version of boost::threads, hopefully this implementation can contribute a few ideas. HTH, -- gpd

4 18

[vmd] Updated VMD library
by Edward Diener 28 Mar '15

28 Mar '15

I have updated the VMD library which has been accepted into Boost based on the reviews and comments of others. The macro interfaces have been simplified and redesigned for easier use and the documentation has been updated to provide more examples and samples of using VMD in code. The library is currently at https://github.com/eldiener/variadic_macro_data. The latest library code is now on the 'master' branch and the code that was reviewed is on the 'Version17' branch. The VMD library is a library of variadic macros which enhance the functionality in the Boost preprocessor library ( Boost PP ). The main focus of the library is the parsing/identifying of a subset of C++ preprocessor data types and of all Boost PP data types. This allows enhanced preprocessor metaprogramming based on the type of macro input. The library has been successfully tested on gcc 4.3.0 on up, VC++ 8 on up, clang 3.3 on up, and Intel 12.1 on up. The library has been tested on Windows and Linux. Comments, questions, bug reports are welcome.

1 0

sun toolset buggy and outdated?
by John Maddock 28 Mar '15

28 Mar '15

I'm trying to test the new Oracle-solaris compiler but I'm running into Boost.Build issues. First off what looks like a bug, if I build with with b2 stdlib=native Then I *still* get stlport You can easily reproduce this on another platform with: cd libs/config/test ../../../b2 config_info toolset=sun stdlib=native -n -d2 which yields: sun.compile.c++ ..\..\..\bin.v2\libs\config\test\config_info.test\sun\debug\stdlib-sun-stlport\config_info.obj "CC" +d -library=stlport4 -g -erroff=%none -KPIC -DBOOST_ALL_NO_LIB=1 -I"..\..\.." -c -o "..\..\..\bin.v2\libs\config\test\config_info.test\sun\debug\stdlib-sun-stlport\config_info.obj" "config_info.cpp" Now for the outdated part: the oracle compiler (12.4) now supports three std lib options: 1) The default - I can't make this work in C++03 mode, but it's the only option that does work in C++11 mode (where it appears to be a recent GNU libstdc++ version). 2) STLPort - only works in C++03 mode. 3) Apache - only works in C++03 mode. So ideally we would probably have: stdlib=stlport, sets -library=stlport4 for both compile and link. stdlib=apache, sets -library=stdcxx4 for both compile and link stdlib=native, sets -std=c++11 for both compile and link. And yes I realise we're mixing up two different features here, but as they can't be mixed and matched anyway it at least gets things working. I guess the toolset should be renamed either "oracle" or "solaris" as well? If anyone has any ideas how to patch the toolset, I have a working virtual machine to test on (or you can do as I did and download a pre-build VirtualBox machine). Thanks in advance, John.

5 13

[gsoc15] Please help rank GSoC 2015 student projects
by Niall Douglas 27 Mar '15

27 Mar '15

Dear Boost Community, The Google Summer of Code 2015 proposals for Boost are in, and we would deeply appreciate the community's help in ranking the proposals according to merit before the 6th of April. To vote, the process is easy: 1. Go to this page https://www.google-melange.com/gsoc/homepage/google/gsoc2015 and click the "Log in" button under Mentors and Administrators. 2. Now click "Create Profile" on the same page. Note that even if you registered last year, you must register again in 2015. Fill in the form. Note that after submitting it drops you at "Edit Profile", which is confusing. 3. Click "My Dashboard", then "Connect with organisations". 4. Choose "Boost C++ Libraries". 5. In the message box, write this: "I am a member of the Boost community and the email(s) I normally post to boost mailing lists with is <email>" filling in the email address(es) you normally use to post to boost mailing lists. This lets us verify that you are indeed a long standing member of the Boost community. 6. Once we approve your request, you will get an email with the subject "Welcome as organisation member". You can now return to the Dashboard on the GSoC website where there will be a new item "Proposals". 7. Work your way through as many of the 33 proposals as you can. You can score them using the stars at the bottom of each proposal page, taking care to read any comments by the mentors and students if present. PLEASE try to rank some of the lowest scored proposals, every year we get a lot of people who only rank the top five and don't bother with the rest. Try to score on the priority basis of: (i) ability to write quality C++, using the programming competency test or samples of programming the student supplied. (ii) proposal quality and your best estimate of the student's understanding of how best to solve the problem at hand. Bear in mind a gifted programmer with a strong work ethic but poor English may appear to not understand the problem as well as native English speakers, this is why we have asked for examples of their programming competency. (iii) if the student came early to the mailing lists to ask for help writing the proposal (the mentors who helped them with their proposals have usually indicated this in the private comments). (iv) usefulness/appropriateness of the feature or work being proposed. Remember a good GSoC is more about getting promising new engineers into Boost and C++ than necessarily getting code to pass Boost peer review in a single summer. 8. Optional: If a proposal looks especially great to you and you feel able to mentor a student this year, please slide the "wish to mentor" button. Just because a proposal already has willing mentors does NOT mean you should not add yourself - if you can substitute for an existing mentor, that may mean we use that mentor for another proposal. As you know, Google Summer of Code is usually worth $42,000 - $48,000 to Boost each year, and a successful GSoC raises our visibility and reputation in the wider open source community. Our thanks to you in advance for taking the time to vote. Niall Douglas Boris Schäling --- Boost C++ Libraries Google Summer of Code 2015 admin https://svn.boost.org/trac/boost/wiki/SoC2015

2 1

[SmartPointers] Determine interest in a new pointer wrapper class "flex_ptr"
by Jakob Riedle 27 Mar '15

27 Mar '15

Hello Boost Community, In the last few weeks, I heavily felt the lack of boost not having a more lightweight solution to a "not-necessarily-owning" pointer-wrapper than shared_ptr. shared_ptr is quite slow in the context that I need it to work. Furthermore it always is owning, even though ownership is shared in between instances. This is unhelpful, if you have an std::list of both non-owning and owning pointers. Hence, if you do not want to use shared_ptr all over your project, or especially want to interact with C, you need a not-necessarily-owning pointer-wrapper. This is why I collected some ideas on how to improve the situation. I came up with a little class named 'flex_ptr', that can hold both strong and weak references (therefore the name 'flexible', but it can also be 'the name of whatever proves itself to be good ...'). It keeps track of whether the held pointer is strong or weak. The Class doesn't need reference counting, since an Instance either is owning, or non-owning. Ownership is transferred between Instances using the default Move/Copy behavior. By Default the Constructor takes a pointer and treats it as a weak one. This is required, since this class aims on being used only at places, that are ought to be able to but not necessarily own objects. (Excuse me for the long sentence) A flex_ptr instance holding a strong pointer is created using a static non-member method named 'make_owning_flex', which accepts an rvalue pointer. As a result, it is not required to use the class at every single pointer occurrences in the project, but only at places, where the programmer wants to allow but not force strong references. The flex_ptr class is easily integrated into existing code using unique_ and shared_ptr's: One could think of - a constructor accepting a const lvalue reference unique_ptr, creating a (flex_ptr-instance holding a) weak reference, - a constructor accepting an rvalue unique_ptr, creating a strong pointer, that is owning an object it received from unique_ptr, - as well as a constructor taking a const lvalue reference shared_ptr, creating a weak pointer. Résumé: This pattern allows outright memory management, it uses less memory than shared_ptr (because no reference counting object required), therefore is faster, allows well-defined interactions similar to unique_ptr (especially at interaction with C) and thus fills a yet unclosed gap in the boost library as well as the Standard. Since this is (only) my personal opinion, I'd like to see how people feel about this 'gap' and think about this addition in the library (however the pattern may be implemented in the end). Regards, Jakob Riedle

6 10

GSoC 2015 Boost Compute Proposal
by Aditya Avinash Atluri 27 Mar '15

27 Mar '15

Hi, This is my proposal. Please suggest edits. Thank you!! :) *Personal Details:* Name: Aditya Atluri University: The George Washington University Major: Computer Engineering Degree: MS Email: adityaavinash1(a)gmail.com Homepage: adityaatluri.github.io Availability: 1. 7 days a week 2. 27 April to 28 August 3. Nothing. *Background Information:* *Educational Background:* I did my undergrad from Indian Institute of Technology, Dhanbad, India. Currently, I am pursuing my Masters at The George Washington University. The courses I have taken are, High Performance Computing, Advanced Computer Micro Architecture, Computer Graphics, Advanced Topics in Computer Graphics, VLSI Design, Low Power VLSI Design, Compiler, Machine Learning. I have did lots of projects in these courses which can be seen on my website and in my bio[1]. *Programming Background and Interests:* I am researcher, I program GPUs with IRs, writing work arounds and using a specific hardware for other applications (example, implementing ray tracing on rasterizer on GPUs, using tessellators for generating procedural textures). I wrote high productive parallel programming abstractions for GPUs[2]. I presented my work at GTC 2014. For this work, NVIDIA supported me with a couple of Tesla K40s. As CUDA, OpenGL, OpenCL, Metal, Thrust are C/C++ APIs I use C++ extensively. I also create databases on GPUs which is now in deep interest from NVIDIA, Google and MapD. I worked with Mesa, Open Source graphics drivers for Linux to build ARB_shader_atomic_counters for R600 backend. I also worked at IBM software labs, where I worked majorly on Java. *Why I opted Boost?* I use boost on daily basis as a part of PyCUDA. I write work arounds which involve some of boost libraries. The next thing I am interested in Boost is its Compute library. I have used other GPU STL style libraries but, none are as good as Compute (simple and elegant). I couldn't contribute to Compute via GSOC last year due to my CPT. I don't want to lose that chance again. This time, I want to take Boost.Compute to a whole new level. I like to program anything related to GPUs, compilers, drivers, APIs. *Interest in Boost.Compute:* As I have mentioned earlier, I am all-in for anything related to GPUs. Either graphics or compute libraries. I believe in Boost.Compute that it can be a widely used API, hence I want to make it more powerful and more useful. *Previous Work:* I work on graphics drivers on regular basis. I write loads of OpenGL compute and shader code (part of my TA job and Mesa testing on local systems). I am good at using APIs, making optimizations, less memory footage. For example, increasing the number of draw calls per second without stalling CPU, writing shaders with more ALU operations than Load/Store operations. Aligning data properly to memory width size, minimizing padding done by compilers by struct unrolling (to get exact multiple of word size). These are a few of the optimizations I do every day. I am currently working on running Metal Shading Language on Intel processors (using AVX).[3] *Plans beyond SoC*: I want to extend Compute to ARM and Qualcomm devices that support both OpenCL and ARM Neon. This brings all "compute-intense" APIs under one roof. C++ 98/03 - 03 C++ 98/14 - 03 C++ STL - 4 Boost C++ Libraries - (Knowledge: 2, Usage: 2) Git: 3 I program using Visual Studio and Xcode. Using Terminal on Linux. I am good with Doxygen. *Project Proposal:* Introduction: Boost Compute library is so far the best portable STL-like C++ library for accelerated computing leveraging the underlying parallel hardware. Boost Compute works well on OpenCL compatible desktop/notebook devices. In this project, we implement Boost Compute on mobile devices. Current mobile devices doesn’t provide good STL style abstractions that are accelerated by SIMD and OpenCL. With the introduction of Metal graphics API for iOS devices, development of compute application for non-iOS and iOS devices requires knowledge multiple skill sets. With this project, we bring all compute abstractions of different mobile devices under one roof that is, Boost.Compute. Project Goals: Make C++ extensions from Objective-C. Integrate device containers to Boost.Compute front end. Make Metal API data types visible to user through Boost.Compute. Implementing BOOST_COMPUTE_FUNCTION() to run custom kernels. Most important, implementing algorithms for Boost.Compute on iOS devices using Metal Shader Language. *Implementation:* Building Boost.Compute APIs for iOS devices. - Metal graphics APIs are used as backend to create Boost.Compute APIs in conjunction with Metal Shading Language Make C++ extensions from Objective-C. - Metal is Objective-C graphics API whereas Boost.Compute is C++ compute API. Hence a bridge between these two APIs should be made to use Compute on iOS devices. Hence, we build C++ extensions from Objective-C APIs. As C++ is also used in building iOS apps, writing Boost.Compute for iOS devices makes it easier to leverage compute performance from an iOS app. Build resource management Metal API backend for Boost.Compute - Here we develop infrastructure which make "algorithms" run on the hardware. Like, creating automated CommandQueues, CommandBuffers, Resources (buffers or textures) - As Metal APIs does not have ‘context’ related API, mapping can be done to Metal command buffer API. Some OpenCL APIs which are natively available (using in Boost.Compute) are not present in Metal API, appropriate mapping from Boost.Compute to Metal API commands will be found. Integrate device containers from Metal API to Boost.Compute front end. - Boost.Compute provide vector and array containers. These should be declared in Metal and integrated to Boost. Device containers include, device vectors, initializing vectors, moving vectors, similarly for arrays, etc., and their STL type functionality (.size(), .length()) - Implementing iterators for the containers should also be done. Make Metal API data types visible to user through Boost.Compute. - Mapping Metal data types to current Boost.Compute data types, while making them consistent with current Boost.Compute APIs. Certain new data types to Metal are being added which improve the performance and decrease memory footprint. Making these visible to the programmer and building building algorithms with them is done in this section. Implement algorithms for Boost.Compute in Metal Shading Language. - This makes the biggest challenge as Metal compute shaders support two modes of execution (fast and precise modes). Algorithms written in each mode should be iterated over to judge the best performance without losing precision for speed. Testing the existing Boost.Compute code on iOS devices and debugging for errors. - With Metal emulators not being available for Xcode, hardware testing will be done[4]. *Timeline:* The timeline is straight forward, for details check Implementation section. 27 April – 25 May: Community bonding, testing the Xcode and iOS infrastructure to find any possible build problems. Build a test run environment (iOS app) to check any other hardware/software issues in deploying Metal API code to iOS device. 25 May – 10 June: Wrap C++ Metal extensions with C++, submit patches. 10 June – 25 June: Implement data types and containers for Boost from C++ Metal APIs. Make appropriate changes to the code after getting feedback from community. Submit patches. 25 June – 3 July: Review community feedback and change patches accordingly. 3 July – 3 August: Write BUILD_COMPUTE_FUNCTION() and Boost.Compute algorithms on Metal Shading Language and integrate it to Boost.Compute Metal APIs. Submit patches. 3 August – 17 August: Write tests and debug by running them on iOS test app 17 August – 28 August: Cleaning up code and review with community. Available Hardware: iPhone 4s, 6Plus, Mac Mini. Mentor: Kyle Lutz (kyle.r.lutz(a)gmail.com) *Competency:* The project I started which creates the actual Metal API, is iaMetal (Metal for Intel processors)[3]. It does not uses Metal SL, it converts Metal SL to AVX extensions. [1]. https://github.com/adityaatluri/adityaatluri.github.co/blob/master/CV.md [2]. https://github.com/urutu/Urutu [3]. https://github.com/iaMetal/iaMetal [4]. https://devforums.apple.com/message/971605#971605 -- Regards, Aditya Avinash Atluri, Graduate Student, Electrical and Computer Engineering, The George Washington University, Washington, DC.

1 0

[asio][android][clang-x86] cannot locate symbol "___tls_get_addr"
by Dmitry Moskalchuk 27 Mar '15

27 Mar '15

As you can see at http://www.boost.org/development/tests/master/developer/asio.html, there are many fails on Android/x86, when tests are built by clang. There was ticket filed to CrystaX NDK tracker about that: https://tracker.crystax.net/issues/912. After some research, I've found reason of fails and created pull request for Boost.Asio: https://github.com/boostorg/asio/pull/17. Shortly speaking, there is intersection of several bugs - one is inability of clang to emulate thread-local variables without support from underlying runtime (gcc can do that), and second is misconfiguration in Boost.Asio headers. I've tested locally with change from https://github.com/boostorg/asio/pull/17 and all '___tls_get_addr' errors disappeared. Now I'm waiting for that pull request to be merged into upstream, but I don't see any activity in Boost.Asio repository. Is there something wrong with my pull request? It's very simple so I wonder why it not yet merged? I'd like to see it merged to the upstream (including 'master') before 1.58 release - just because this bug cause not only Boost.Asio fails, but several others libraries too. -- Dmitry Moskalchuk

2 3

[GSoC] Proposal for uBLAS
by Ganesh Prasad 27 Mar '15

27 Mar '15

Hello everybody, Here is the final draft of my proposal for GSoC'15 and I have made it public. https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015… The same text can be found on Gist at https://gist.github.com/GnsP/72dce0ac96394f54797c Reviews are requested and welcome. Best wishes Ganesh Prasad

1 0

No automatic super project commits at the moment.
by Daniel James 27 Mar '15

27 Mar '15

Hi, Github is currently going through a DDOS attack, which is why the super project isn't getting updated for new commits. I imagine testers will also have problems running. Daniel

1 0

GSOC 2015 Proposal
by Aditya Avinash Atluri 27 Mar '15

27 Mar '15

Hi, This is my proposal for GSoC 2015. Please suggest me some edits. Thank you!! :) https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015… -- Regards, Aditya Avinash Atluri, Graduate Student, Electrical and Computer Engineering, The George Washington University, Washington, DC.

5 4

Proposal "Enhanced vector and deque containers" project (GSoC 2015)
by Nico Hartmann 27 Mar '15

27 Mar '15

Hello everyone, as a student with quite some experience developing C++ I finally decided to participate in an open source project instead of just writing all the code for myself. To do so I chose to join the boost community in the course of this year's Google Sommer of Code. Therefore I wrote a proposal for the "enhanced vector and deque containers" project that really drew my interest. I like to invite you to take a look at my proposal as well as the requested implementation of a small vector class (including unit tests) to prove my capability to write C++ code. Thank you very much Nico project announcement: https://svn.boost.org/trac/boost/wiki/SoC2015#a5.Enhancedvectoranddequecont… project proposal (GSoC 2015): https://www.google-melange.com/gsoc/proposal/review/student/google/gsoc2015… small vector class implementation on github: https://github.com/nh-/gsoc_vector

1 1

GSOC 2015 Proposal
by vivek dhiman 26 Mar '15

26 Mar '15

Hello all This is my proposal for GSoC 2015. http://www.google-melange.com/gsoc/proposal/public/google/gsoc2015/vdhiman/… It would be awesome if you guys could suggest some changes/edits. Thanks Vivek Dhiman

2 1

Boost.uBLAS a library for matrix computations Project: Data Frame
by Sahba E 26 Mar '15

26 Mar '15

Hello all, My name is Sahba Etezad. I'm studying masters of Computing Science in Simon Fraser University, Canada.I'm really interested in working on ublas library and matrix computations. Particularly, I'm really passionate about the data frame project. My thesis concerns graph embedding so I've been working with Boost graph library for over a year now. I've been also coding in Matlab for over 4 years, and I think my familiarity with matrix operations and all that can be an asset for this project. I've finished implementing the competency code. https://github.com/setezad/ublasAnd I know it's really last minute, but I'd really appreciate it if you would give me some advice on what I should include to provide a precise project proposal. It has been mentioned that a data frame similar to R should be implemented with extension to implementing the summary and aggregate functions. I studied the two links provided in the project description ( http://pandas.pydata.org/pandas-docs/dev/generated/pandas.DataFrame.html, and http://cran.r-project.org/web/packages/data.table/index.html ). Now my question is knowing that a data frame can have countless attributes and methods, should I specify what attributes and methods I'd like to implement? Or will it be decided later and need not to be proposed by me? Thank you very much. Regards,Sahba Etezad

1 0

[SORT] Parallel Algorithms
by Francisco José Tapia 26 Mar '15

26 Mar '15

Sorry by the delay, As promised, the sorting parallel algorithms On my computer (Quad Core) the GCC std::sort and stable_sort are slight faster than my version of intro_sort and merge_sort (stable sort is a synonym of merge_sort). In other computer with an Intel I3, my algorithms are slight faster than in the GCC version. Trying to optimize the parallel implementation. I modified the parallel version for to use the std::sort and std::stable_sort. The parallel_sort version response good, but the parallel_stable_sort increase the time around a 60% compared with the version with countertree::parallel_merge_sort . After many test, I discover the cause of the problem. The demonstration is in the test_stress_sort_01.cpp. In this program we have a big vector of 100 000 000 elements uint64_t. The program make parts of the same size for each HW core. On my computer 4 parts and 4 cores. The program execute the part sequentially checking the time, and after do the same but in parallel, each thread sort a part, and check the time. This is done with the std::stable sort and countertree::merge_sort. The data input is the same for all. The next lines are the result show max. OpenMP threads: 4 (4 processors) Sort of 100000000 elements in a vector --------------------- Random elements, few repeated ( rand() )----------------------- Stable Sort Part 0 secs :2.77955 Part 1 secs :2.75015 Part 2 secs :2.76068 Part 3 secs :2.76284 Parallel Sort secs :8.49796 Countertree stable sort Part 0 secs :2.72802 Part 1 secs :2.71614 Part 2 secs :2.72074 Part 3 secs :2.722 Parallel Sort secs :4.80692 Surprisingly the parallel sort with countertree::stable_sort is much more faster than the sort with std::stable_sort in the GCC 4.8 and 4.9 compiler. This is the secret of the speed of the countertree::parallel_merge_sort. This is very important, because when the size of the elements is small, the GCC and the countertree algorithms have similar performance. But when the size of the elements grow, the std::stable sort is slower than the countertree::merge_sort. This difference is increased in the parallel version. The next lines are part of benchmark_sort_05.cpp *************************************************************** Sort of N = 6250000 elements of size 128 ***************************************************************** Random elements, few repeated ( rand() )----------------------- STL std::sort :2.9188 secs countertree::intro_sort :2.87864 secs parallel::sort :2.46113 secs tbb::parallel_sort :1.86458 secs countertree::parallel_sort:1.89263 secs std::stable_sort :8.77963 secs countertree::merge_sort :5.70694 secs parallel::stable_sort :8.03946 secs countertree::parallel_merge_sort :4.90815 secs I have in mind a new version of the stable sort in order to improve the speed, reducing the number of internal copy of elements. I hope to have time in Christmas, but I can't guarantee. If the results are the expected I will send you You have too, a version of indirect_sort, which sort pointers to the elements, and at end sort the elements according the pointers. You can replace any sort algorithm by their indirect version, obtaining the same results, with the only difference of the time needed. You have a benchmark_indirect_sort.cpp where see the comparison of the time needed of several sort methods and their indirect version with elements of different size. This code is a preliminary version, done for my countertree library. If you consider useful, I will change the name space and document the code, the algorithms and the ideas obtained from the benchmarks. Please feel free for ask me any question or for to modify or change anything. The goal is to provide good sort methods to the users. In the zip file you have the code and a file with a description of each code. Yours

5 20

[Locale] Boost.Locale cannot Run in Visual Studio 2010
by Sarvagya Pant 26 Mar '15

26 Mar '15

I have been trying to learn Boost.Locale Module. Consider this http://www.boost.org/doc/libs/1_55_0/libs/locale/doc/html/conversions_8cpp-… example. The code gets successfully compiled but when I try to run it, it gives the error Unhandled exception at 0x74d34b32 in LearningCPP.exe: Microsoft C++ exception: std::bad_cast at memory location 0x00a6fa48.. I have attached the stack-trace of the program also. Here it is: KernelBase.dll!74d34b32() [Frames below may be incorrect and/or missing, no symbols loaded for KernelBase.dll] KernelBase.dll!74d34b32() > msvcr100d.dll!_nh_malloc_dbg(unsigned int nSize, int nhFlag, int nBlockUse, const char * szFileName, int nLine) Line 302 + 0x1d bytes C++ msvcr100d.dll!malloc(unsigned int nSize) Line 56 + 0x15 bytes C++ LearningCPP.exe!std::use_facet<boost::locale::converter<char> >(const std::locale & _Loc) Line 526 C++ LearningCPP.exe!boost::locale::to_upper<char>(const char * str, const std::locale & loc) Line 225 + 0x9 bytes C++ LearningCPP.exe!main() Line 170 + 0xc4 bytes C++ LearningCPP.exe!__tmainCRTStartup() Line 555 + 0x19 bytes C LearningCPP.exe!mainCRTStartup() Line 371 C kernel32.dll!75268543() ntdll.dll!776bac69() ntdll.dll!776bac3c() Did anyone faced this issue when using Boost.Locale in Visual Studio 2010? If so, how do I resolve this issue? *PS:* I have used option Use Unicode Character Set under the Character Set option of Visual Studio. I believe the libraries are correctly linked too. -- *sarvagya*

1 0

[threads / signals2] Win events replace by boost signals (threadsafe)
by Fu ji 26 Mar '15

26 Mar '15

Hello, I have to change win32 events with something portable so I decided to use boost.signals2. Right now I have something like: ret = WaitForMultipleObjets{ switch(ret) { case Timeout: something; break; case Event1: something; break; case Event2: something; break; }} and I think that the good idea is to replace this with something like that: for(;;){ Execute code from timeout, if event occurs interrupt and execute code which is responsible for event handling} but for test I write this: boost::signals2::signal<void()> signal; void SendSignal() { std::cout << "Send signal"; boost::this_thread::sleep_for(boost::chrono::milliseconds(200)); signal(); boost::this_thread::sleep_for(boost::chrono::milliseconds(2000)); } int main() { boost::thread t1(SendSignal); for (;;) { std::cout << "."; boost::this_thread::sleep_for(boost::chrono::milliseconds(100)); } auto c = signal.connect([]() { std::cout << "Signal receive" << std::endl; boost::this_thread::sleep_for(boost::chrono::milliseconds(1000)); }); return 0; } unfortunately this example is not working, what I've done wrong ? Best regards

6 10

Server certificate expired on svn.boost.org
by William Gallafent 26 Mar '15

26 Mar '15

“The certificate expired on 2015-03-22 02:33” … ! -- Bill Gallafent.

2 1

Removing auto_ptr/etc. from Boost
by Stephan T. Lavavej 25 Mar '15

25 Mar '15

Hi Boost devs, I need your help to get rid of auto_ptr forever. I want to implement C++17's N4190 "Removing auto_ptr, random_shuffle(), And Old <functional> Stuff", although it's going to take a while. In VC 2015, the removal will be opt-in (requested via a macro; I've already checked this in). My plan is for the removal to be opt-out in the version after that, and unconditional in the version after that. To achieve the opt-in removal, I've already eliminated the STL's internal dependencies on this stuff (nothing derives from unary_function/binary_function anymore, and shuffle() isn't directly implemented with random_shuffle() anymore). To prepare for the future of opt-out removal, I've also been removing usage from the compiler and other stuff. However, Boost is used in our tests in a number of places. What I'd like to ask is for Boost to begin removing its usage of this stuff (unconditionally or for VC 2015+, your pick). According to my understanding, only unary_function/binary_function and auto_ptr are used extensively by Boost, with the other stuff being used rarely or not at all. Thanks, Stephan T. Lavavej Senior Developer - Visual C++ Libraries

10 23

[iterator] Bug #7526
by Claas 25 Mar '15

25 Mar '15

Hi! I was wondering, how the iterator developers intend to proceed with ticket #7526 (https://svn.boost.org/trac/boost/ticket/7526) Two fixes are available and seemingly just wait to be applied. One fix has been available for two years, and a more sophisticated (probably preferable) fix has been submitted 9 month ago. Has this simply been forgotten or are there any reasons, not to apply one of the available patches ?. Since I require the requested functionality, I would like to press the issue. If more support is required to fix this, please let me know. Since two years I have had to patch each version of boost manually to deploy this fix, which is a little frustrating. So I would gladly contribute, if this is required. Any update on the issue would be appreciated. Regards Claas

1 0

[TypeSort] Automatic type sorting
by costis glynos 25 Mar '15

25 Mar '15

Hello,Is there any interest in a library which automatically sorts types from smallest to largest at compile time?The benefit would be the automatic Data Structure Alignment and potential improvement in performance.Foo<int,bool,Custom16ByteType,char,double,short> foo_1; //normal Foo<int,bool,Custom16ByteType,char,double,short> foo_2; //using the TypeSort output: size of foo_1 = 48 size of foo_2 = 32 Kind Regards, Constantinos

6 17

Messages from list marked as spam
by Matus Chochlik 25 Mar '15

25 Mar '15

On Wed, Mar 25, 2015 at 1:33 PM, Christian Hägele <haegele(a)teamviewer.com> wrote: > Am 24.03.2015, 19:27 Uhr, schrieb Marcel Raad <raad(a)teamviewer.com>: > > Email from certain people on the list is >>> marked as spam by gmail: "Why >>> is this message in Spam? It has a from >>> address in teamviewer.com but >>> has failed teamviewer.com's required >>> tests for authentication. " >>> >> >> I guess that's me. Probably because I use >> Gmane's web interface to post messages >> instead of my e-mail account. >> > > I'm using my e-mail account to write this mail from the same domain as > Marcel does. > I hope this mail is not marked as spam. > > I would appreciate if somebody would give feedback if this mail is marked > as Spam by Gmail or similar providers. > It gets into spam in my gmail account (together with some messages sent from yahoo.com)

1 0

Boost 1_58_0_rc1 is available for testing
by Marshall Clow 25 Mar '15

25 Mar '15

Release candidate files for 1.58.0 beta 1 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. IMPORTANT NOTE: There is a bug with the build scripts; you have to specify the address-mode and architecture to b2. I used: ./b2 address-model=64 architecture=x86 to test this. The files (and associated md5s) are: MD5 (boost_1_58_0_b1_rc1.7z) = 302c7dfc917227843d24beed33ccc99c MD5 (boost_1_58_0_b1_rc1.tar.bz2) = d7d030e85bf5534a328c108c62a7fb0e MD5 (boost_1_58_0_b1_rc1.tar.gz) = ec90cd23bdc99c5eaf88245ea94a28e0 MD5 (boost_1_58_0_b1_rc1.zip) = dc8379fb95c84fe2fca53a4b2c96da23 Thanks! -- The release managers

13 18

Re: [boost] [test] boost.test owner unresponsive to persistent problems for multiple years
by Raffi Enficiaud 24 Mar '15

24 Mar '15

Le 18/03/15 14:43, Edward Diener a écrit : > On 3/18/2015 5:49 AM, Paul A. Bristow wrote: > > Do I have to rebuild the Boost.Test library to get the new docs ? > Because the first thing I did was to try to view the new docs by opening > index.html only to find that there was no html documentation. Then I > tried 'b2 toolset=gcc-4.9.2' for building Boost.Test and received: > > Performing configuration checks > > - symlinks supported : yes > error: Unable to find file or target named > error: 'dyn_ut_example.cpp' > error: referred to from project at > error: '../../libs/test/example' > > It does not appear that the 'develop' branch is ready for me at all. This is the location of the new documentation: http://www.boost.org/doc/libs/develop/libs/test/doc/html/index.html I do not know about the update frequency In order to build the doc: cd $boost/libs/test/doc ../../../bjam -sDOCBOOK_XSL_DIR=/some/path/docbook-xsl-1.78.1/ -sDOCBOOK_DTD_DIR=/some/path/docbook-xml-4.2/ Doxygen should be in the $PATH. The previous command will build whatever is necessary. Best, Raffi

6 8

[build] broken documentation links
by dominic meiser 24 Mar '15

24 Mar '15

Hi, The links to the documentation (html and pdf) at http://www.boost.org/doc/libs/1_57_0/tools/build/index.html are broken. Cheers, Dominic

1 0

[Hana] Informal review request
by Louis Dionne 24 Mar '15

24 Mar '15

Dear Boost, As some may be aware of, I am currently working on a metaprogramming library called Hana, with the intention of proposing it for inclusion in Boost. The purpose of that library is to act as a toolbox for expressing computations on both types (like the MPL) and heterogeneous values (like Fusion). The library is built around C++14 idioms and implementation techniques to maximize expressiveness and performance. I am now requesting feedback from the community, with the intention of asking for a formal review in the next months. A similar review was asked for in last August. The library has undergone several modifications since then, both to address issues raised during the review and for general improvement. Here are some issues that were raised during the review and addressed: - Usage of names and terms unknown to C++ programmers: Efforts were made to make this better, and several functions were renamed (`fmap` is now `transform`). When possible, the documentation also uses terms more familiar to C++ programmers, like concept instead of "type class". - The order of the arguments to some algorithms was unfortunate for C++. It was consistent with Haskell, but it turned out to be cumbersome in C++. This is changed in most places. - Inability to easily implement individual algorithms: This is fixed, and algorithms are now standalone structures using tag-dispatching, almost exactly as in Fusion. - Lack of a good introductory tutorial: A lot of work has gone into improving both the tutorial and the reference documentation. - Lack of support for mainstream compilers: The library is now almost fully functional with Clang 3.5. A GCC 4.9 port with reduced functionality is also underway on the `redux` branch. The library is available at [1] and the documentation at [2]. Comments should be directed to this mailing list, while bugs and other similar problems should be directed to the GitHub issue tracker. Please participate, especially if you have interest and/or experience in metaprogramming; after all, you represent the target audience for Hana. Thank you, Louis Dionne [1]: https://github.com/ldionne/hana [2]: http://ldionne.github.io/hana/

13 48

boost regex recursive quesion
by 温西波 24 Mar '15

24 Mar '15

This is my first time to using maillist I'm learning to use boost::regex for a month , a few days ago I found a problem( maybe is my mistake ?) I construct a simple recursive regular expression: a(?0)? This regex contains a recursive call (?0). It should match a string with any arbitrary length filled with 'a' characters. regex_match only returns true for "a" and "aa", but failed to match "aaa" and any string longer than three characters. Why? I try it on boost 1.45 and 1.57 , both get same result . I had sent this question on stackoverflow , but had not get a answer now . Is there any flag should be used with regex_match to use recursive call ? Thank you .

2 3

[rational] has no maintainers
by Peter Dimov 23 Mar '15

23 Mar '15

Currently, nobody has write access to Boost.Rational, and I see a number of open pull requests (mostly by John Maddock) lingering. John, would you like write access to it so that you can apply your suggested changes?

5 6

BOOST_SYMBOL_VISIBLE
by Robert Ramey 23 Mar '15

23 Mar '15

I'm trying to get my MAC OS (Yosemite) to build the boost serialization library and I've having a problem. In a couple of tests, the program throws some exceptions. When this occurs I get a message something like "terminate called after throwing an instance of 'boost::archive::archive_exception'". I'm quite sure that I used to be able to do this without problem - as of a couple of months ago. I recently "upgraded" to Yosemite. My gcc-4.8.1 version I'm getting from HPC website. In the course of trying to figure this out, I've come upon boost documentation which explains BOOST_SYMBOL_VISIBLE which was new to me. It suggests that my code which looks like class archive_exception : public virtual std::exception { ... could be creating a problem. due to deriving from some other class which might be defined a runtime shared library. So I replaced it with: class BOOST_SYMBOL_VISIBLE archive_exception : public virtual std::exception { ... and I also tried class BOOST_SYMBOL_VISIBLE archive_exception : public virtual std::exception { ... This doesn't change anything so it looks like I'm barking up the wrong tree. Is there anyone here who might want to shed some light on this? Robert Ramey -- View this message in context: http://boost.2283326.n4.nabble.com/BOOST-SYMBOL-VISIBLE-tp4673673.html Sent from the Boost - Dev mailing list archive at Nabble.com.

3 3

Bug in boost asio on mac
by Philippe Daouadi 23 Mar '15

23 Mar '15

Hi, I have had this bug on mac os Yosemite where I would call async_connect and my code would never be called back. I didn't have any answer to my bug report and I would like to be sure that it it is not lost. https://svn.boost.org/trac/boost/ticket/11070 Any suggestion or workaround is welcome. Cheers, Philippe -- *This email and any attachment thereto are confidential and intended solely for the use of the individual or entity to whom they are addressed.If you are not the intended recipient, please be advised that disclosing, copying, distributing or taking any action in reliance on the contents of this email is strictly prohibited. In such case, please immediately advise the sender, and delete all copies and attachment from your system.This email shall not be construed and is not tantamount to an offer, an acceptance of offer, or an agreement by Aldebaran Robotics on any discussion or contractual document whatsoever. No employee or agent is authorized to represent or bind Aldebaran Robotics to third parties by email, or act on behalf of Aldebaran Robotics by email, without express written confirmation by Aldebaran Robotics’ duly authorized representatives.* ------------------------------ *Ce message électronique et éventuelles pièces jointes sont confidentiels, et exclusivement destinés à la personne ou l'entité à qui ils sont adressés.* *Si vous n'êtes pas le destinataire visé, vous êtes prié de ne pas divulguer, copier, distribuer ou prendre toute décision sur la foi de ce message électronique. Merci d'en aviser immédiatement l'expéditeur et de supprimer toutes les copies et éventuelles pièces jointes de votre système.* *Ce message électronique n'équivaut pas à une offre, à une acceptation d’offre, ou à un accord d'Aldebaran Robotics sur toute discussion ou document contractuel quel qu’il soit, et ne peut être interprété comme tel. Aucun employé ou agent d’Aldebaran Robotics n'est autorisé à représenter ou à engager la société par email, ou à agir au nom et pour le compte de la société par email, sans qu’une confirmation écrite soit donnée par le représentant légal d’Aldebaran Robotics ou par toute autre personne ayant reçu délégation de pouvoir appropriée.*

3 4

Multiple-pattern string search algorithms
by meghana madhyastha 23 Mar '15

23 Mar '15

Hi all ! I noticed that Boost's algorithm module does not include multiple pattern string searching algorithms such as the Rabin Karp algorithm and Aho-Corasick algorithm. I think these algorithms are very useful and should be implemented in the library. If no one is currently working on them, I am willing to implement them. Please let me know your opinion. Regards, Meghana

2 1

Enhanced Vector and Deque Competency Test
by Islam Taha 23 Mar '15

23 Mar '15

Hi all I’m sorry with inconvenience with my last mail, it’s just my first to write in a mail list. I’ve fixed some issues with my code but now it may run completely, I would be thankful if anyone has some free time to give a feedback to my fixed code and tell me if any issues. code https://github.com/islam-taha/stdVector/blob/master/vector.cpp <https://github.com/islam-taha/stdVector/blob/master/vector.cpp> . thanks in advance Islam

1 0

transforming ex. boost lib into C++11-only lib?
by Oliver Kowalke 23 Mar '15

23 Mar '15

Hello, is it permitted to transform an existing boost library into a C++11-only library? best, Oliver

15 19

[endian] Testing floating point interoperability
by Beman Dawes 23 Mar '15

23 Mar '15

On Fri, Jan 30, 2015 at 5:25 AM, Paul A. Bristow <pbristow(a)hetp.u-net.com> wrote: > > >> * Anything else that you can think of to improve FP support. > > The proof of the pudding is in the eating. > > I'd suggest that *testing interoperability* is the key precaution that you should advise. I'm starting to write a caution to go in the release, and will make that point. A new test, "floating_point_test", has been added to the endian test suite. It will focus on interoperability. (I know that you are talking about users testing their application needs, but I want to test Boost.Endian to be able to warn users of areas where there are known issues.) > It should obviously be between all possible combinations of processor hardware types. It isn't just processor types. std::numeric_limits<float>::signaling_NaN() representation is 0x7fc00001 for Microsoft/Dinkumware, but is 0x7fa00000 for gcc and clang:-( > The test should include a range of floating-point values from min to max, > and include NaN and infinity unless it is certain that they will never occur. To get started, floating_point_test.cpp is testing float and double: numeric_limits<>::min() numeric_limits<>::max() numeric_limits<>::lowest() numeric_limits<>::epsilon() numeric_limits<>::round_error() numeric_limits<>::infinity() -numeric_limits<>::infinity() numeric_limits<>::quiet_NaN() numeric_limits<>::denorm_min() 0.0 -0.0 1.0 -1.0 native uint32_t 0x12345678U as a float native uint64_t 0x0123456789abcdefULL as a double pi<>() Are there other specific values worth testing?> (Unless very special precautions are taken, then infinity and NaN are like to rear their ugly heads > at some time - probably when you least want to see them!) > > It must be possible to 'round-trip' all floating-point values. That's one of the tests performed on each value. > You can't test all possible values (except for 32-bit float - 64-bit double takes about 50 years at > current processor speeds ;-) > but you can chose values (floating-point bit patterns) at random for a test lasting some minutes or > even hours. Could you provide the random number generation and otherwise help with this? I've only ever used integer RNGs. Thanks, --Beman

7 11

GSoC project
by Lulu C. Li 23 Mar '15

23 Mar '15

Hi! I wish to participate in GSoC this summer and I am very interested in Boost, in particular concurrent hash tables project. I am familiar with STL and worked on synchronization problems and concurrent processes in C. I can work on all the functionalities mentioned. What are other features that I should know for this project and proposal? Lulu

2 1

Test Runner: teeks99-08f - msvc-14.0 - Extra Define
by Tom Kent 23 Mar '15

23 Mar '15

The Test runner teeks99-08f has been running the msvc-14.0 - CTP 6 release for a bit now. It runs with the extra bjam option "define=BOOST_MSVC_ENABLE_2014_JUN_CTP". Is this still necessary? I was going through and updating some settings and I notices this was still there and was trying to decide if I should clean it up or not. Thanks, Tom

2 1

How to install a algorithm to Boost
by jianwei li 23 Mar '15

23 Mar '15

Hi Now,I have implemented a linear algorithm.How can i install it to Boost project. Jianwei Li

2 1