December 2012 - Boost - lists.boost.org

[string_ref] Feature requests
by Daniel James 01 Jan '13

01 Jan '13

Hi, I've been trying to convert quickbook to use boost::string_ref, and there are a few missing features that might be useful: Construction from a pair of iterators, either std::basic_string::const_iterator, or boost::basic_string_ref::const_iterator. Which of course can be the same type, which is annoying but not too hard to work around. Easy conversion to std::basic_string. There's a C++11 explicit string operator, but that isn't much good for portable code. Something like a 'string' or 'to_string' member would do the trick. Support for comparisons with std::basic_string. The comparison operators are templates so they aren't called with an implicit conversion. Could use a template parameter for the type so that it picks up anything which is (implicitly?) convertible to boost::basic_string_ref, maybe using SFINAE. I didn't need it, but could probably also could do with a 'hash_value' function for boost::hash support. Is potentially error prone if the original string is modified or destroy, but there are some valid use cases. thanks, Daniel

4 13

[exception][iostream] link error in boost_1_52_0
by Jeff Flinn 31 Dec '12

31 Dec '12

I'm getting the following link error using boost_1_52_0 with Xcode 3.2.6 gcc 4.2: "std::bad_alloc::what() const", referenced from: vtable for boost::exception_detail::error_info_injector<std::bad_alloc>in libboost_iostreams-mt.a(zlib.o) vtable for boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<std::bad_alloc> >in libboost_iostreams-mt.a(zlib.o) Boost exception is listed as a header only library, but there is clone_current_exception_non_intrusive.cpp in ..\boost_1_52_0\libs\exception\src. Does boost.exception lib need to be built? thanks, jeff

2 2

[trunk] permission denied?
by Oliver Kowalke 31 Dec '12

31 Dec '12

Did you reset the passwords for trunk? Until today I was able to commit changes to boost-trunk - but my password is invalid now?! Oliver

7 9

[Git] Regression testing modular Boost
by Beman Dawes 30 Dec '12

30 Dec '12

Starting a new thread - this is far to important to bury in the long documentation thread! On Tue, Dec 11, 2012 at 10:52 AM, Rene Rivera <grafikrobot(a)gmail.com> wrote: >What is the procedure that testers will follow? I've been assuming testers will follow the same general procedure. But other than verifying that hand-invoked b2 runs tests as expected, nothing else has been done that I'm aware of. > Is there documentation equivalent to < > http://www.boost.org/development/running_regression_tests.html> for the new > setup? None yet. I've been assuming we will just update www.boost.org/development/running_regression_tests.html > What changes to the current tools need to happen to the adjust to > the new setup? As a first cut, branch the current tools and convert any code that currently uses svn commands to use git commands. But before any testing is done, it would be helpful if Boost.Build was updated to handle the generation of boost-root/boost header file links, rather than relying on the workaround cmake script. Do you feel comfortable enough with git to handle the conversion? --Beman

6 22

[Trac] Internal Server Error
by Vicente J. Botet Escriba 30 Dec '12

30 Dec '12

Hi, I'm getting a Internal Server Error TracError: IOError: [Errno 13] Permission denied: u'/opt/trac/boost/log/trac.log Could someone take a look? Vicente

1 0

[type_traits] Typo in Boost.TypeTraits
by Michel Morin 30 Dec '12

30 Dec '12

Patch attached for fixing typos in Boost.TypeTraits P.S. John, could you also apply the patch attached in #7683? https://svn.boost.org/trac/boost/ticket/7683 Regards, Michel

3 5

[algorithm] Typo in Boost.Algorithm
by Michel Morin 30 Dec '12

30 Dec '12

Patch attached for fixing typos in Boost.Algorithm P.S. Marshall, could you also apply the patch attached in #7714? https://svn.boost.org/trac/boost/ticket/7714 Regards, Michel

2 2

[Git] Modularization of Boost.Any, Boost.Array, and Boost.StaticAssert
by Daniel Pfeifer 29 Dec '12

29 Dec '12

Hi, according to our preliminary modularization, the candidates Boost.Any, Boost.Array, and Boost.StaticAssert each have their own repository, even though each of them consists of a single header file only (disregarding tests, examples and documentation). I propose to put all three of them into the Boost.Utility repository. Comments? --Daniel

7 9

[git] Boost.Build location
by Vladimir Prus 29 Dec '12

29 Dec '12

I am wondering what will be the location of Boost.Build after the git switch. It seems to be part of http://github.com/boost-lib/boost right now. Maybe, it would be best to have separate git repository for Boost.Build? In particular, that would allow to fork just Boost.Build, which is important given git's inability to handle partial checkouts. It would also allow giving push access for Boost.Build to other people, without also giving access to superproject. Comments? Thanks, Volodya

18 44

[python] Proposal: RAII for Global Interpreter Lock (GIL)
by John Zwinck 29 Dec '12

29 Dec '12

There are many questions and example classes online for dealing with Python's Global Interpreter Lock (GIL) using RAII. I think Boost.Python should provide this functionality, rather than having users who build hybrid C++/Python applications copy-pasting code from various places. I was one of those users recently, and the code I developed to deal with it is now public: https://github.com/jzwinck/pccl/blob/master/InterpreterLockGuard.hpp https://github.com/jzwinck/pccl/blob/master/InterpreterLockGuard.cpp https://github.com/jzwinck/pccl/blob/master/test/InterpreterLockGuard.test.… Comments in the header explain how to use it in the context of Boost.Python, and contain a link to a wiki from which some of the code was originally copied. Why add this to Boost? It's clearly code that a bunch of people need, often people who are already using Boost.Python. It has a permissive license, and I can re-license it if need be. And it depends on Boost (mostly for thread-specific storage--I hope this dependency won't be seen as a liability here, though it could be removed if needed). This particular implementation was used successfully in a few programs in a commercial setting on Fedora and RHEL systems. It has some extra checks that we found helpful compared to some of the versions you'll find posted online. The code also builds and passes its tests with GCC on Mac OS X. I welcome any feedback regarding the suitability for inclusion in Boost of this particular code and/or the concepts it implements. John Zwinck

2 2