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

[1.54.0] Beta Release Candidates available
by Marshall Clow 04 Jun '13

04 Jun '13

Release candidate files for 1.54.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. The files (and associated md5s) are: 31266b7dcc6f557ad839e4e87317cd6e *boost_1_54_0_beta1_rc1.tar.gz fbf7be9cbaf9ea6fb21ae73d0c17100d *boost_1_54_0_beta1_rc1.tar.bz2 7de4299ab69c941e83fe3fc46dddc15f *boost_1_54_0_beta1_rc1.zip c73e5118ff585d9f1d68542f96a0758a *boost_1_54_0_beta1_rc1.7z Thanks, --The release managers

11 17

[1.54.0] [log] Permission to merge bugfix to release
by Andrey Semashev 04 Jun '13

04 Jun '13

Hi, May I merge the following changesets to the release branch? In short, it fixes the ticket [1] for Boost.Log and the similar issue for string_ref - incorrect handling of width specification with stream IO. Boost.Log: https://svn.boost.org/trac/boost/changeset/84512 https://svn.boost.org/trac/boost/changeset/84514 string_ref: https://svn.boost.org/trac/boost/changeset/84511 https://svn.boost.org/trac/boost/changeset/84513 https://svn.boost.org/trac/boost/changeset/84518 The tests are green. Also, there's a small fix for MinGW 4.4 tests of Boost.Log: https://svn.boost.org/trac/boost/changeset/84515 MinGW 4.4 tests have not been run for quite some time, but I believe it's safe to merge it as well. [1] https://svn.boost.org/trac/boost/ticket/8614

2 1

Request to contribute boost::FFT
by Nathan Bliss 03 Jun '13

03 Jun '13

Dear Boost Community Members, I am writing to ask if I could contribute a C++ FFT implementation to the boost library. I noticed that there is a boost::CRC so I thought it would be a good addition to have boost::FFT as well. MIT have an existing open-source FFTW library, but it is GPL-licensed which is much more restrictive than the Boost license. I should imagine a commercial FFTW license would be very expensive. I have working FFT code which I have tested on Ubuntu Linux GNU gcc and also Visual Studio Express 2012 (MS VC++) for Windows. My code, when run as a 2048-point FFT, agrees with the MIT FFTW one to a max error margin of 6 parts per million. It is implemented using templates in a .hpp file and is very easy to use: ------------------------------------------------------------------------------------------------------------[fft.hpp] template<class FLOAT_TYPE, int FFT_SIZE, int NUM_THREADS>class FFT;///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////[Invocation example] typedef double My_type;FFT<My_type, 2048, 4> user_fft;user_fft.initialise_FFT();get_input_samples(*user_fft.input_value_array, user_fft.m_fft_size);user_fft.execute_FFT();print_output_csv(user_fft.output_value_array, 2048);------------------------------------------------------------------------------------------------------------ It's uniqueness compared to other FFT implementations is that it fully utilises the boost::thread library, to the extent that the user can give the number of threads they want to use as a parameter to the class template (above case is for 4 parallel threads). It is structured and organised so that users could customise/optimise it to specific processor architectures. I've also tried to develop it in the spirit of Boost in that all class members which users should not access are private, only making public what is necessary to the API. My code is a decimation-in-time radix-2 FFT, and users could in theory use the existing API as a basis to extend it to more complex implementations such as the Reverse/Inverse FFT, bit-reversal of inputs/outputs and multi-dimensional FFTs. I look forward to your reply. Kind regards,Nathan Bliss

14 21

web page copyrights
by Charles_J_Wilson＠Dell.com 03 Jun '13

03 Jun '13

I was reading the 1.54.0 beta 1 release notes and managed to scroll down to the bottom of the page. I noticed that the copyright information was not current, so I looked at the main page. It's not current either. As this probably falls on any number of people, I'm posting instead of opening an issue. Charles Wilson Principal Software Development Engineer Dell | Enterprise Solutions Group

2 1

Request for permission to apply a multi library patch (misspell on comment only)
by Vicente J. Botet Escriba 03 Jun '13

03 Jun '13

HI, https://svn.boost.org/trac/boost/ticket/8558 "some misspell fixes" contains a patch that concerns some misspell on comments only code or on documentation. The patch is quite big and concerns almost all the Boost libraries. Could I apply it all at once, e.g. just after the release 1.54 is delivered? Best, Vicente

1 0

[1.54.0] release branch reopened for bug fixes ONLY
by Marshall Clow 03 Jun '13

03 Jun '13

Now that we have released the first beta, the release branch is open for bug fixes. Only bug fixes, please.[*] No new features. No new libraries. You do not need a release manager's approval to merge a bug fix. The earlier you can merge your bug fixes, the better. The branch will close again for final release preparations on June 24. As usual, you can see the release calendar here: http://www.boost.org/development/index.html [*] Changes to documentation are always allowed. -- Marshall Marshall Clow Idio Software <mailto:mclow.lists@gmail.com> A.D. 1517: Martin Luther nails his 95 Theses to the church door and is promptly moderated down to (-1, Flamebait). -- Yu Suzuki

1 0

weirdness in documentation of boost::chrono?
by Anthony Foiani 01 Jun '13

01 Jun '13

Greetings -- The online reference for boost::chrono seems to have an odd error in it. If one looks at: http://www.boost.org/doc/libs/1_53_0/doc/html/chrono/reference.html#chrono.… (or: http://preview.tinyurl.com/lcl8j3c ) There is an "operator*==" (note double '='). The actual live link is to "operator*=", and the link works. I took a quick look, and this glitch does not seem to be present in the HTML documentation included in the 1_53_0 tarball. Am I just imagining things? Is my browser being stunningly clever in a way I don't understand? Thanks, Tony

2 1

Re: [boost] [Boost-users] [Thread] Can't compile package_task code with 1.54
by Vicente J. Botet Escriba 01 Jun '13

01 Jun '13

Le 01/06/13 07:30, Vicente J. Botet Escriba a écrit : > Le 01/06/13 00:56, Szymon Gatner a écrit : >> Hi, >> >> I just tried to compile my 1.52- based code with 1.54 beta and run >> into package_task compilation issue. >> >> In 1.52 I was using BOOST_THREAD_VERSION=3 define but with 1.54 I >> complied with =4. >> >> Test program: >> >> #define BOOST_THREAD_VERSION 4 >> >> #include <boost/thread/future.hpp> >> #include <boost/function.hpp> >> >> struct MyFunc >> { >> void operator()()const {} >> }; >> >> int main() >> { >> boost::function<void()> f; >> MyFunc mf; >> >> boost::packaged_task<void()> t1(f); // error 1 >> boost::packaged_task<void()> t2(mf); // error 2 >> } >> >> >> error 1 being: >> >> d:\devel\boost_1_54_0_beta1\boost\thread\future.hpp(2848): error >> C2664: >> 'boost::detail::task_object<F,R>::task_object(boost::detail::task_object<F,R> >> &)' : cannot convert parameter 1 from 'boost::function<Signature>' to >> 'boost::detail::task_object<F,R> &' >> >> and error 2 similarly: >> >> d:\devel\boost_1_54_0_beta1\boost\thread\future.hpp(2848): error >> C2664: >> 'boost::detail::task_object<F,R>::task_object(boost::detail::task_object<F,R> >> &)' : cannot convert parameter 1 from 'MyFunc' to >> 'boost::detail::task_object<F,R> &' >> >> (I tried with custom functor because I thought maybe error was >> related to boost function) >> >> Compiling with Visual Studio 2012 Update 3 >> >> > Hi, > > this is related to https://svn.boost.org/trac/boost/ticket/8596 which > is fixed now, but maybe it doesn't works for you. > Note that the trunk regression test since revision 84414 run with this > compiler pass ( > libs/thread/test/sync/futures/packaged_task/func_ctor_pass.cpp) > <https://svn.boost.org/trac/boost/browser/branches/release/libs/thread/test/…> > http://www.boost.org/development/tests/trunk/developer/thread.html. > > Unfortunately not a single msvc tester has run after revision 84468 on > release branch. > > I have no the possibility to reproduce it now. Please could you send > the whole log? (privately if you prefer? Or via a ticket? > I have found the error. My tests don't test for packaged_task<void()>. The following patch should fix the issue (see attached file) Please could you apply it a tell me if it fix with your compiler? Best, Vicente svn diff future.hpp Index: future.hpp =================================================================== --- future.hpp (revision 84547) +++ future.hpp (working copy) @@ -2362,18 +2362,12 @@ task_object(task_object&); public: F f; -#ifndef BOOST_NO_CXX11_RVALUE_REFERENCES - task_object(BOOST_THREAD_RV_REF(F) f_): - f(boost::forward<F>(f_)) - {} -#else task_object(F const& f_): f(f_) {} task_object(BOOST_THREAD_RV_REF(F) f_): - f(boost::move(f_)) // TODO forward + f(boost::move(f_)) {} -#endif #if defined BOOST_THREAD_PROVIDES_SIGNATURE_PACKAGED_TASK && defined(BOOST_THREAD_PROVIDES_VARIADIC_THREAD) void do_apply(BOOST_THREAD_RV_REF(ArgTypes) ... args) @@ -2616,18 +2610,12 @@ task_object(task_object&); public: F f; -#ifndef BOOST_NO_CXX11_RVALUE_REFERENCES - task_object(BOOST_THREAD_RV_REF(F) f_): - f(boost::forward<F>(f_)) - {} -#else task_object(F const& f_): f(f_) {} task_object(BOOST_THREAD_RV_REF(F) f_): - f(boost::move(f_)) // TODO forward + f(boost::move(f_)) {} -#endif #if defined BOOST_THREAD_PROVIDES_SIGNATURE_PACKAGED_TASK && defined(BOOST_THREAD_PROVIDES_VARIADIC_THREAD) void do_apply(BOOST_THREAD_RV_REF(ArgTypes) ... args)

1 0