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

[predef] Boost detail/endian.hpp
by Rene Rivera 07 Aug '13

07 Aug '13

FYI.. I just tested, locally, and checked in the replacement for the "boost/detail/endian.hpp". This file is now non-BSL license free. If this is a header you rely on I would appreciate it if you could do your own testing to make sure it lives up to the previous header's functionality. Thanks, Rene. -- -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo

2 1

Re: [boost] Removing old config macro and increasing compiler requirements.
by Brian Wood 07 Aug '13

07 Aug '13

Dave Abrahams wrote: >>on Tue Aug 06 2013, Brian Wood <woodbrian77-AT-gmail.com> wrote: >> >> I was going to ask for an update on these things, but this >> will do. I think it's just morass without an e. It sounds like >> it's time to reboot. I haven't followed this real closely, but >> know a lot of effort has gone into trying to preserve >> information in the conversion. That may be too much to ask. > > Boy, you really haven't been paying attention: that part is done. > Throwing out all that work at this point because you get the sense "it's > time to reboot" would be... well, pick your adjective. Too many are > flying through my brain right now to choose. I thought the use of the word morass was honest and putting it mildly. I'm not saying to abandon the goal. I recommend a modular approach, but it seems the years are passing without much happening. -- Brian Wood Ebenezer Enterprises - In G-d we trust. http://webEbenezer.net

1 0

Re: [boost] Removing old config macro and increasing compiler requirements.
by Brian Wood 07 Aug '13

07 Aug '13

Dave Abrahams wrote: > That's how Boost works. One of the ideas of the Git separation (and > hopefully eventual Ryppl) transition is to give maintainers more of a > sense of control over these things. I'm sure the commitment to quality > is there, but I think there's probably a lot of resignation over the > seemingly-intractable morasse. I was going to ask for an update on these things, but this will do. I think it's just morass without an e. It sounds like it's time to reboot. I haven't followed this real closely, but know a lot of effort has gone into trying to preserve information in the conversion. That may be too much to ask. -- Brian Wood Ebenezer Enterprises - So far G-d has helped us. http://webEbenezer.net

3 2

[mpl] at<> example bug?
by Mostafa 06 Aug '13

06 Aug '13

Looks like the example found here: http://www.boost.org/doc/libs/1_54_0/libs/mpl/doc/refmanual/at.html is buggy: BOOST_MPL_ASSERT_RELATION( (at< range, int_<0> >::value), ==, 10 ); It should be: BOOST_MPL_ASSERT_RELATION( (at< range, int_<0> >::type::value), ==, 10 ); Mostafa

3 3

How do folks test serialization code?
by John Maddock 06 Aug '13

06 Aug '13

Title almost says it all, how do you verify that your classes serialization code is truly platform independent, and doesn't accidently break later? I have some trivial tests that round trip to a stringstream using boost::archive::text_i/oarchive, but of course that only verifies that platform-specific serialization works. So what do folks do - generate text archives on different platforms, deserialize and compare? How does Boost.Serialization itself verify this? Cheers, John.

6 17

[git] Deleted file in detail module
by Daniel James 05 Aug '13

05 Aug '13

Hi, I just look in the detail module, and it contains this file: boost/functional/detail/container_fwd.hpp This file was deleted from trunk in r80288 and from release in r81356. https://svn.boost.org/trac/boost/changeset/80288 https://svn.boost.org/trac/boost/changeset/81356 Would it be possible to reflect that? Btw. I would have put it in functional, but that isn't a big deal. thanks, Daniel

2 1

[move] Documentation example typo.
by Jurko Gospodnetić 04 Aug '13

04 Aug '13

Hi. Just reporting a slight typo in boost::move library documentation's file_descriptor class example code for closing the OS file descriptor. It says: > if(!os_descr_) operating_system_close_file(os_descr_); in its destructor & assignment operator when it should in fact say: > if(os_descr_) operating_system_close_file(os_descr_); [notice the removed ! operator] Hope this helps. Best regards, Jurko Gospodnetić

2 1

[asio] condition_variable for coroutine-powered ASIO
by TONGARI J 04 Aug '13

04 Aug '13

Hi, Since Boost 1.54, ASIO introduced yield_context, which is very helpful to alleviate the pain of writing async ops. Unlike multi-threading, with cooperative multi-tasking, generally we don't have to worry about synchronization, but we still need some sort of mechanism to sync the coroutines in cases like producer-consumer for waiting the data... While I haven't seen any sync tool for asio/coroutine, having a condition_variable or such may be very useful, what do you think? Attached is the poor-man's implementation...

2 1

[timer] May I apply trivial fix?
by Antony Polukhin 03 Aug '13

03 Aug '13

Hi, As far as I know Beman is almost always busy, so may I apply trivial fix described in this ticket https://svn.boost.org/trac/boost/ticket/8956 ? This fix is essential for running regression tests with Intel compiler. -- Best regards, Antony Polukhin

5 6

[utility] [swap] How about Boost.Move?
by Antony Polukhin 03 Aug '13

03 Aug '13

Hi, Sources of Boost.Variant have a swap implementation that takes advantage of move emulation. That code can be useful for Boost.Swap. The idea is not to use std::swap in case of ADL failure, but use a swap implementation that is aware of move emulation: namespace boost_swap_impl { namespace swap_move_emulated { template <typename T> inline void swap(T& lhs, T& rhs) { T tmp( boost::move(lhs) ); lhs = boost::move(rhs); rhs = boost::move(tmp); } } template<class T> void swap_impl(T& left, T& right) { //using namespace std;//use std::swap if argument dependent lookup fails using namespace boost_swap_impl::swap_move_emulated; swap(left,right); } // ... With that code types that use move emulation can be swapped faster and even move only types can be swapped. So, what do the community think about such optimization? -- Best regards, Antony Polukhin

5 8