January 2011 - Boost - lists.boost.org

Re: [boost] BoostCon 2011 keynote speaker
by Dave Abrahams 19 Jan '11

19 Jan '11

At Sat, 15 Jan 2011 16:56:51 -0600, Hartmut Kaiser wrote: > > Hey all, > > This is to inform you, that Hans Boehm (HP, > http://www.hpl.hp.com/personal/Hans_Boehm/) accepted to give this year's > keynote. I believe this is excellent news for the conference and for all > participants. He will have a lot to say, which directly concerns many C++ > developers. He will give us a topic for his keynote asap at which point we > should add a note to the website. This is awesome news! Hans is a C++ Committee member, probably the primary driving force behind the new C++ memory model that allows concurrency, and is also famous as the developer of a widely-used C++ garbage collector, and a bit less famous for the "rope" data structure. I know he will give a great keynote and I'm eager to hear it. -- Dave Abrahams BoostPro Computing http://www.boostpro.com

1 0

Distributed Development Process (was Re: Development Practices (Proposal Progress))
by Dean Michael Berris 19 Jan '11

19 Jan '11

On Thu, Jan 13, 2011 at 9:15 PM, Beman Dawes <bdawes(a)acm.org> wrote: > On Tue, Jan 11, 2011 at 10:36 AM, Dave Abrahams <dave(a)boostpro.com> wrote: >> >> Create a new one... I don't think we want to tweak "the process." I >> think we want to create an alternative process for people who are >> interested in following a more modern, decoupled development model. >> Eventually, if it works, the other one will die of underuse. The >> thing is that you have to make sure that your proposal doesn't clash >> with the way we do things now: for example, it can't create >> significant new work for the release managers. >> > tl; dr; -- feedback on https://svn.boost.org/trac/boost/wiki/DistributedDevelopmentProcess would be very much appreciated! > Excellent points! > > For example, I'd very much like to move both the libraries I maintain and my > release management work to Git. I've been using it for a while now on > various projects, including one very small (three contributors) distributed > project, and find Git preferable by a wide margin. But others will want to > stick with SVN at least for awhile. Because Git can track a Subversion > repository, it is probably possible to use both without undue trouble. > I have the same experience -- and I've worked with larger teams that have been using Git exclusively with wonderful results. It's the difference between a concurrent lock-free queue and one that has a critical section on all the member functions. One invites a lot less friction and enables more fluid workflows while the other, not so much. > While I'm leery of anything that would "create significant new work for the > release managers" on an ongoing basis, I am willing to put in some extra > work during a transition. > Cool. :) > Areas where I personally don't want any big changes yet are the Boost build > and regression testing systems. Alternatives for either of these systems > don't appear anywhere near ready for prime time WRT Boost. > Right, I haven't gotten thinking about that part yet, but I think others are already working on that front. :) > The formal review system needs a drastic rework to make it more parallel and > remove bottlenecks, but I don't have anything beyond vague feelings about > how to do that. > Yes and I intend to address that in this document: https://svn.boost.org/trac/boost/wiki/DistributedDevelopmentProcess I haven't gotten to the part on the specifics yet but I think it would be good to get feedback on what's already there. :) -- Dean Michael Berris about.me/deanberris

3 10

review request: addition to type_traits library of has_operator_xxx
by Frédéric Bron 19 Jan '11

19 Jan '11

I would like to propose to your review the following addition to the type_traits library, available at the following addresses: https://svn.boost.org/trac/boost/browser/sandbox/type_traits http://dl.free.fr/lRm4VL6WP/type_traits.tar.bz2 The purpose of the addition is to add type traits to detect if unary and binary operators can be applied to given types. For example, is "x<y" or "!x" or "x+y" meaningful? If required, the return type of such an expression is checked to know if it is convertible to a given type. Default behaviour is to not check the return type. The following traits are added: // binary operators: template < typename LHS, typename RHS=LHS, typename RET=void > == has_operator_equal_to != has_operator_not_equal_to > has_operator_greater >= has_operator_greater_equal < has_operator_less <= has_operator_less_equal + has_operator_plus - has_operator_minus * has_operator_multiplies / has_operator_divides % has_operator_modulus && has_operator_logical_and || has_operator_logical_or & has_operator_bit_and | has_operator_bit_or ^ has_operator_bit_xor // unary operators: template < typename RHS, typename RET=void > + has_operator_unary_plus - has_operator_unary_minus ! has_operator_logical_not This new version reflects the discussions we had on the list: http://thread.gmane.org/gmane.comp.lib.boost.devel/194625 In particular about the check or not of the return type. All operators are now included and not only comparison binary operators. Example: has_operator_less<LHS, RHS, RET>::value_type is the type bool. has_operator_less<int> inherits from true_type. has_operator_less<int, int, std::string> inherits from false_type. has_operator_unary_minus<int, long> inherits from true_type. has_operator_unary_minus<double, int> inherits from true_type. has_operator_unary_minus<int, std::string> inherits from false_type. Documentation is accessible at libs/type_traits/doc/html/index.html in the archive. Regards, Frédéric PS: tested with g++ 4.4.5 on i686-linux.

14 53

[1.45][Serialization] fails to cross-compile using arm-linux-uclibc toolchain
by Alex Potapenko 19 Jan '11

19 Jan '11

Building boost 1.45 on Debian using arm-linux-uclibc toolchain fails to compile serialization lib, due to static assertions in basic_binary_?archive.hpp's at: BOOST_STATIC_ASSERT(sizeof(tracking_type) == sizeof(bool)); BOOST_STATIC_ASSERT(sizeof(class_id_type) == sizeof(int_least16_t)); BOOST_STATIC_ASSERT(sizeof(class_id_reference_type) == sizeof(int_least16_t)); It appears to be some uclibc issue, since it builds fine using glibc toolchains. Is it safe to simply comment out these assertions? Thanks in advance, Alex

2 1

Re: [boost] [context] Implementation comments
by Andrzej Krzemienski 19 Jan '11

19 Jan '11

>>> Why is boost::thread implemented with move-semantics? >> Boost.Context is much more low level than Boost.Thread. > why? thread and context are resources - I don't see context more low > level than thread Hold on. I understand that that you are saying that context is the same level as thread. On the other hand in the reply to my question (about using boost::function) you said > boost.context is intended to be the basis of such things like coroutines > (see boost.coroutine) and fibers (see boost.fiber). Which somehow implied that Context is lower-level than Coroutine or Fiber. If you really treat Context the same level as Thread, I would suggest passing function<void()> as trampoline function. If you can afford using pimpl, you can easily change function<void()> to void(*)(void*) and void* parameters: void call( void* arg) { auto ptr = static_cast< function<void()>* >( arg ); ptr->operator(); } function<void()> trampoline = ...; context_impl( call, &trampoline ); Using function<void()> makes it easier to understand for thread users and makes the interface similar to thread, task, etc... Regards, &rzej

2 2

Re: [boost] [Boost-commit] svn:boost r67792 - in branches/release: boost/iterator
by Michel MORIN 19 Jan '11

19 Jan '11

Hi Marshall, It seems there are missing merges in changeset [67792]. <marshall(a)idio.com> wrote: > Author: marshall > Date: 2011-01-08 13:38:08 EST (Sat, 08 Jan 2011) > New Revision: 67792 > URL: http://svn.boost.org/trac/boost/changeset/67792 > > Log: > Merging fixes to release; fixes #2294 fixes #4918 fixes #3645 refs #2823 refs #1427 refs #2893 > Properties modified: > branches/release/boost/concept_check.hpp (contents, props changed) > branches/release/boost/fusion/container/list/detail/build_cons.hpp (contents, props changed) > branches/release/boost/iterator/iterator_facade.hpp (contents, props changed) > branches/release/status/explicit-failures-markup.xml (contents, props changed) > Text files modified: > branches/release/boost/concept_check.hpp | 166 ++++++++++++++++++++------------ > branches/release/boost/fusion/container/list/detail/build_cons.hpp | 3 > branches/release/boost/iterator/iterator_facade.hpp | 28 ++-- > branches/release/status/explicit-failures-markup.xml | 199 ++++++++++++++++++++++++++++----------- > 4 files changed, 261 insertions(+), 135 deletions(-) The log message says that the fixes for tickets #1427 and #2893 (#1427: transform_iterator should use boost::result_of to determine functor result type) (#2893: Function Input Iterator) are merged to release. But this changeset does nothing with iterator/transform_iterator.hpp and iterator/function_input_iterator.hpp. Regards, Michel

2 4

[Locale] Boost Locale looks for review manager:
by Artyom 19 Jan '11

19 Jan '11

Hello All, There had been recently several discussions about review process Unicode etc. I think that Boost.Locale would allow us going forward in all Unicode related stuff in Boost and it would help us to get to some standardization in all related to Unicode handling in Boost. So I'm calling for You boost users and developers to volunteer to be a review manager of Boost.Locale. Thank you very much, Artyom

3 6

[website] running_regression_tests.html
by Jim Bell 19 Jan '11

19 Jan '11

I made changes to the "Running Regression Tests" page, per the list discussions of a few weeks ago. <http://beta.boost.org/development/running_regression_tests.html> Comments welcome. Do I transfer this page to the live website myself? (If so, how? I see </development/website_updating.html>, but that doesn't quite cover it.) Please advise. Thanks in Advance, -Jim

2 1

Boost.Pool - Are you using this library, please can we have your input?
by Paul A. Bristow 18 Jan '11

18 Jan '11

Boost.Pool is the subject of a 'make-over' by Boost.Guild. (This is some of a test-bed for a process of revision of older, perhaps orphaned, libraries using the relative safety of the sandbox). In order to permit any modification, the original (hand-written?) html documentation has been converted to Quickbook (and somewhat revised) at http://svn.boost.org/svn/boost/sandbox/guild/pool/libs/pool/doc/ You can build the html docs using the jamfile.v2 in the normal way, but you will probably find it more convenient to go direct to the pdf version http://svn.boost.org/svn/boost/sandbox/guild/pool/libs/pool/doc/pool.pdf This is fairly fully hyperlinked, and includes a reference section using Doxygen. Doxygen comments have been added to the header files (from the original html docs). (If you are a Doxygen fan, there is also a Doxyfile for generating Doxygen-style docs in the /doc/Doxygen/ folder). We are now considering some better tests, and perhaps some enhancements to the code. We'd like input from users about: 1 Things missing or wrong from the docs. More up to date references? 2 Things missing (or don't work well) from Pool. 3 New things that you would like (this is not a promise!). 4 Examples of your use. Perhaps you built some during your development that could be used? 5 Better tests. Thanks. Paul PS Don't panic - the release version will not be changed without a mini-review. --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

3 2

[1.46.0] [units] test_output failing all release regression compilers
by Beman Dawes 18 Jan '11

18 Jan '11

http://beta.boost.org/development/tests/release/developer/summary.html is looking pretty good for most libraries, but units test_output is failing all release regression compilers. Can we get a fix for this before the beta next week? Thanks, --Beman

4 9