- Boost - lists.preview.boost.org

[thread] boost::future::then
by Vladimir Prus 06 Nov '15

06 Nov '15

Hi, looking through docs for some other futures implementation [1], I see this: Why not use boost::future? # At the time of writing, 1.53 (the first version with the requisite features) was brand new, not well-tested, and not available to [...] developers. It is still a bit buggy/bleeding-edge They haven't fleshed out the threading model very well yet, e.g. every single then currently spawns a new thread unless you explicitly ask it to work on this thread only, and executor support was nonexistent (and now, is still experimental). Now, 1.53 is ancient. Can anybody comment on these statements regarding boost::future::thread state in 1.59? In particular, suppose I have this: // Thread 1 boost::promise<int> pi; boost::future<int> fi = pi.get_future(); // pass pi to thread 2 somehow fi.then(....); // Thread 2 pi.set_value(100); And I want continuation to be executed in thread 1, assuming that thread 1 runs Qt event loop, allowing me to use QTimer::singleShot, or queued signal, or similar mechanism. How would I go about making boost::future do it? Has anybody done so? Thanks, Volodya

4 41

The release branch will close tonight for the 1.60 beta
by Marshall Clow 05 Nov '15

05 Nov '15

Please do not merge to the release branch after tonight until the 1.60 beta is released (scheduled for next Wednesday) unless you have specific approval from the release managers. Thank you. (There will be a chance to merge bug fixes and documentation updates after the beta) -- Marshall (and the rest of the release managers)

2 2

[config] macro for portable restrict and restrict references
by Joel FALCOU 04 Nov '15

04 Nov '15

I pushed a PR that adds the macro BOOST_RESTRICT to take place of the compielr specific __restrcict/__restrict__ keyword. It also comes with an indicator if said keyword can be applied to references. https://github.com/boostorg/config/pull/81 Comments welcome.

1 0

[String Algo] Any reason the predicates don't optimize for random access iterators?
by Nevin Liber 04 Nov '15

04 Nov '15

I was looking in boost/algorithm/string/predicate.hpp and noticed that that the predicates *starts_with, *ends_with, *contains and *equals don't optimize for random access iterators. While I haven't done any benchmarks yet, it seems like it would be faster for random access iterators to do an O(1) length check at the beginning and then while looping only check one iterator against its end instead of two. Thoughts? Nevin :-) -- Nevin ":-)" Liber <mailto:nevin@c <nevin(a)eviloverlord.com>plusplusguy.com> (847) 691-1404

2 1

[test][serialization] Fwd: [Boost-testing] regression testing failure on develop branch
by Rene Rivera 03 Nov '15

03 Nov '15

---------- Forwarded message ---------- From: Aparna Kumta <aparna.kumta(a)oracle.com> Date: Mon, Nov 2, 2015 at 2:42 PM Subject: [Boost-testing] regression testing failure on develop branch To: Running Boost regression tests <boost-testing(a)lists.boost.org> My regresion tests are failing on develop branch as follows: error: at /export/home/boost_regression_develop/boost_sparc-S2_stlport4/boost_bb/src/kernel/modules.jam:107 error: Unable to find file or target named error: 'test_boost_array.cpp' error: referred to from project at error: '../libs/serialization/test' Anyone seeing this issue? Thanks, Aparna _______________________________________________ Boost-Testing mailing list Boost-Testing(a)lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-testing -- -- Rene Rivera -- Grafik - Don't Assume Anything -- Robot Dreams - http://robot-dreams.net -- rrivera/acm.org (msn) - grafikrobot/aim,yahoo,skype,efnet,gmail

4 3

Interest in a Boost.Chrono/Date library
by Vicente J. Botet Escriba 03 Nov '15

03 Nov '15

Hi, maybe some of you have already see the Howard Hinnant presentation at CppCOn2015 [1] about his new data-v2 library [2]. My prototype of Boost.Chrono/Date library ([3] ] was based on the Howard original library, but when we want to reach the maximum of performances we need to use a specific date class for each usage. This is what Howard explains in his marvelous presentation ans his tiny date library My post here wants to know if there is interest in a library providing what H.H. date library provides in Boost. Note that his data-v2 library yet doesn't provides as much as Boost.Date provides but IMHO it is much elegant and efficient. If there is enough interest, I will request you to do a first review of the H.H. Date-V2 library. Then once we have a consensus I will make my POC Chrono/Date library ready for review. H.H. Date-V2 is under MIT license, which IIRC is compatible with the Boost license. I don't know yet if would need to add this license, as my POC [3] is already a good starting point, nevertheless, I would like to know if there could be any issues about having the source under both licenses. Best, Vicente [1] https://www.youtube.com/watch?v=tzyGjOm8AKo [2] https://github.com/HowardHinnant/date [3] https://github.com/viboes/chrono_date/commits/master First commit Nov/2011 Last-Mars2014

8 17

Math tools polynomial enhancements
by Jeremy Murphy 02 Nov '15

02 Nov '15

I was just looking at the polynomial class and thinking that it could be enhanced substantially with more operators. Presumably with division and remainder it would be a Euclidean ring and then you could even call gcd on it. I have a draft implementation ready but I wanted to check that there is interest from the maintainers. Cheers. Jeremy

9 27

[base_from_member][sun-next_cpp11] problem with variadics at base_from_member
by Joaquín M López Muñoz 02 Nov '15

02 Nov '15

Hi, In 2012, boost::base_from_member was equipped with variadics machinery to perfect-forward construction arguments to the contained member. Unfortunately, Solaris Studio 12.5 on Intel chokes on it (http://tinyurl.com/no7trgb ): "../boost/utility/base_from_member.hpp", line 137: Error: Parameter pack 'x' not expanded with '...' [...] Oddly enough, the same compiler does work fine on Sparc. May I suggest that lines 129-132 of boost/utility/base_from_member.hpp #if !defined(BOOST_NO_CXX11_RVALUE_REFERENCES) && \ !defined(BOOST_NO_CXX11_VARIADIC_TEMPLATES) && \ !defined(BOOST_NO_CXX11_FUNCTION_TEMPLATE_DEFAULT_ARGS) && \ !(defined(__GNUC__) && (__GNUC__ == 4) && (__GNUC_MINOR__ < 4)) be added a special provision for this environment (the same way it already has for GCC 4 and prior)? #if !defined(BOOST_NO_CXX11_RVALUE_REFERENCES) && \ !defined(BOOST_NO_CXX11_VARIADIC_TEMPLATES) && \ !defined(BOOST_NO_CXX11_FUNCTION_TEMPLATE_DEFAULT_ARGS) && \ !(defined(__GNUC__) && (__GNUC__ == 4) && (__GNUC_MINOR__ < 4)) && \ !(defined(__SUNPRO_CC) && defined(__i386) && (__SUNPRO_CC <= 0x5140)) I can't unfortunately test this myself as I don't have access to the compiler. FWIW, my interest in having this fixed is that it's seemingly the only bug preventing Oracle Solaris Studio 12.5 on Intel from supporting Boost.MultiIndex. Joaquín M López Muñoz Telefónica

3 3

[GitHub] [PR] setting default branch to 'develop'
by Michel Morin 01 Nov '15

01 Nov '15

Hi, We sometimes forget to change the base branch of PR from 'master' to 'develop', even if we know PR should be made against 'develop' branch! To prevent from accidentally making PR against master branch, it'd be nice to **set the default branch to 'develop' branch** for Boost repositories on GitHub. (Then, the default base branch of PR would be set to 'develop' branch.) To change the default branch, it takes just a few clicks on web browser: https://help.github.com/articles/setting-the-default-branch/ Thoughts? Regards, Michel P.S. Some libraries have already done this, but most of Boost libraries don't do this yet.

10 22

[Config] BOOST_HAS_PTHREAD_MUTEXATTR_SETTYPE not defined in MACOS for GCC-5
by Vicente J. Botet Escriba 29 Oct '15

29 Oct '15

Hi John, I'm having an issue with gcc-5.1 on MacOs. BOOST_HAS_PTHREAD_MUTEXATTR_SETTYPE is not defined. I see that there are things like #if __MACH__ && !defined(_MSL_USING_MSL_C) ... # if (__GNUC__ == 4) // Both gcc and intel require these. # define BOOST_HAS_PTHREAD_MUTEXATTR_SETTYPE # define BOOST_HAS_NANOSLEEP # endif #else ... // BOOST_HAS_PTHREAD_MUTEXATTR_SETTYPE not defined here #endif Wondering why the GCC version must be 4 and why when _MSL_USING_MSL_C is defined these PTHREAD attributes are not defined neither. BTW, when I compile with version 4 everything works correctly. Vicente

3 3