May 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

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

Re: [boost] Migrating www.boost.org to another server
by DongInn Kim 31 May '13

31 May '13

Any news from Beman? Regards, -- - DongInn On May 21, 2013, at 12:14 AM, Daniel James <daniel(a)calamity.org.uk> wrote: > On 21 May 2013 05:00, Marshall Clow <mclow.lists(a)gmail.com> wrote: >> On May 20, 2013, at 8:54 PM, Daniel James <daniel(a)calamity.org.uk> wrote: >> >>> On 21 May 2013 02:34, Marshall Clow <mclow.lists(a)gmail.com> wrote: >>>> [ Off-list ] >>>> Just as an update - Beman was _not_ at C++Now this year (the first time he has missed it). >>> >>> Do you know if he's available? >> >> Well, not at the moment - he's on the east coast (GMT-4), but in general, yes. > > I'll send him an email later then. Cc'd emails can get lost in the > noise of the list.

5 35

May I ask community to make a small review of the high-level network library we released?
by Dmitry Timoshenko 31 May '13

31 May '13

We released the beta version accessible here http://libunicomm.org. We would be really appreciated if this could happen. Thanx, Dmitry.

1 0

Git Modularization Review no vote heads-up
by Beman Dawes 31 May '13

31 May '13

If the steering committee's Git Modularization Review vote were held today, I've vote no since I think that we aren't yet ready. Since my concerns are apparently easy to fix technically, I'm mentioning them here to give Dave and Daniel a chance to address them before the actual Git Modularization Review starts. Concerns: 1) The mapping of svn branch names to modular git branch names needs to be revised: Svn "trunk" needs to become modular git "develop", not "master". Modular git needs to have a branch "master" that represents the latest stable release. Whether the content is identical to the last boost release or to branches/release at point of conversion needs to be decided, as does what the history, if any, of this branch looks like. 2) The procedures described in https://svn.boost.org/trac/boost/wiki/TryModBoost need to be updated, the dependency on CMake needs to be removed, and the procedures need to work. These are blocking issues because they prevent development and testing of modular boost testing procedures, developers procedures, release procedures, installation procedures, and documentation. Until they are resolved, the entire modular boost conversion rests on the shoulders of Dave and Daniel. Once they are resolved, others can pitch in and help since from that point forward we will be in a pure git environment and detailed knowledge of the conversion process from svn is not required. --Beman

9 25

[Atomic] Rationale for preventing copy construction/assignment?
by Collin Dauphinee 31 May '13

31 May '13

I've recently noticed that boost::atomic<T> prevents assignment from boost::atomic<T>, as well as copy construction. I'm having trouble understanding why this decision was made, as it makes boost::atomic<T> (and classes with a boost::atomic<T> member) very hard to store in containers, and I can't immediately see any safety issues that would be caused by allowing copy operations. What is the rationale for not allowing assignment or copy construction from another boost::atomic<T>?

6 10

Re: [boost] Git Modularization Review no vote heads-up
by "Jürgen Hunold" 30 May '13

30 May '13

Hi Dave, > Gesendet: Donnerstag, 23. Mai 2013 um 07:28 Uhr > Von: "Dave Abrahams" <dave(a)boostpro.com> > An: boost(a)lists.boost.org > Betreff: Re: [boost] Git Modularization Review no vote heads-up > > > on Wed May 22 2013, Jürgen Hunold <jhunold-AT-gmx.eu> wrote: > > > But this can easily be done after the conversion. > > > > I think we already lost too much time with failed rewrite attempts, so let us > > get a working repository first. Then Volodya can test git mv v2/* . and report > > results. Afterwards, we can always try rewriting in a separate clone. Done this myself yesterday. Works like a charm, git blame shows undisrupted history after git commit shows "rename" with 100% on each file moved. > Rewriting _published_ history is most strongly discouraged by the Git > people, for several good reasons. *If* there is to be any > rearrangement, it should happen before the switchover, so it doesn't > bork people who are doing work based on the history originally > published. Yes, the basic rule of git. > However, I am loath to do any rearrangement that doesn't (reasonably) > faithfully reflect how things were set up in the past. Otherwise, > someone will check out an old state of the super-module and find that > things have the wrong path relationships. Of course, path relationships > will not match SVN anyway (because we don't have a modular layout in > SVN), but people on this list made it quite clear that modularizing > history was important to them, so I presume they want the Git history to > reflect reality with maximal fidelity. Correct. > That said, if the consensus is that things should be rearranged in the > build repository, we can do that. We just need clear and explicit > instructions that cover what to do with *all* the paths that have been > used in Boost.Build (including branches and tags) throughout time. As > you can see from > https://github.com/ryppl/Boost2Git/blob/master/repositories.txt#L2261 > and following lines, just preserving the existing structure was > nontrivial. That one starts with repository build : common_branches { submodule of "boost" : "tools/build"; content { "tools/build/" : "build"; "tools/jam/" : "jam"; } right? So, this now creates "tools/build/build" with the contents of "tools/build" and "tools/build/jam" with the contents of "tools/jam" which is long gone. The former is wrong, as it does not preserve the current structure despite the thing you wrote above. I think that a one-to-one mapping like: repository build : common_branches { submodule of "boost" : "tools/build"; content { "tools/build/" ; } is the way to go now. If something goes wrong, please put "tools/jam/" somewhere else. Btw. would repository build : common_branches { submodule of "boost" : "tools/build"; content { "tools/build/v2" ; } be the right way to move v2 one directory up? Yours, Jürgen -- * Dipl.-Math. Jürgen Hunold ! juergen.hunold(a)gmx.eu * voice: 0049 4257 300 ! Fährstraße 1 * fax : 0049 4257 300 ! 31609 Balge/Sebbenhausen * mobil: 0049 178 186 1566 ! Germany

10 36

Re: [boost] [gsoc] Getting started with a repository (Was: Re: Live read-only GIT mirrors of Boost trunk SVN)
by Niall Douglas 30 May '13

30 May '13

> > I think the GIT team should make a decision NOW about whether GSOC > > students should use GIT or not. > > > I think I'm against this, on the grounds that there is a lot to go > > wrong, and much critical students Google-time, especially with those > > who may be even ranker amateurs than me ;-) > > +1 > > > Unless there is a firm commitment from the GIT team to support > > students using GIT, then I think they should stick to boost-sandbox > > and do things "the old way". > > > Views from the GIT team? > > Paul > > ...Or their mentors! > > I'm mentoring a project and I'm a total, absolute git-beginner (used it, like, only > sporadically for one small repo). > > Is there any way to send git newbies like me and my student to the sandbox, at > least one more year? GSoC Boost.AFIO lives at https://github.com/ned14/boost.afio but will auto mirror itself into Boost Sandbox once Paul registers for Boost SVN commit privs. If there's interest on how I configured this, do let me know. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.

3 3

Re: [boost] [ASIO] Issue with epoll reactor? Callback handler not executed.
by Marat Abrarov 30 May '13

30 May '13

Hi, Arpan. > Everything works fine till async_write. You forgot that free functions like asio::async_write(_until)/asio::async_read(_until)/etc. are composed operations (http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/reference/async_re ad/overload1.html): ... This operation is implemented in terms of zero or more calls to the stream's async_read_some function, and is known as a composed operation. ... Any composed operation (failed to find documentation for this) is implemented by means of multiple simple asynchronous operations. For example asio::async_read is implemented in terms of multiple calls of AsyncStream::async_read_some. So during any composed operation there are multiple (>=1) completions of simple asynchronous operations each of those has its own (intermediate) completion handler. Each of such intermediate completion handlers is dispatched like bound completion handler (http://www.boost.org/doc/libs/1_53_0/doc/html/boost_asio/reference/asynchro nous_operations.html) by the means of the same instance of asio::io_service as AsyncStream provides. So this code: > async_write(socket, buffer(command.c_str()), &write_handler); > io_service.reset(); > io_service.run_one(); will implement only one completions handler. That completion handler may be the intermediate completion handler if async_write needs to make more than one call to async_write_some (may be this needs to be explicitly described in Boost.Asio documentation?). That is the reason why your write_handler is not called sometimes. May be this can solve the problem: async_write(socket, buffer(command.c_str()), &write_handler); io_service.reset(); io_service.run(); async_read_until(socket, response, '\n', &read_handler); io_service.reset(); io_service.run(); Regards, Marat Abrarov.

3 6

Patch for Identification of NVCC with Changing Backends
by ryo-nishimura＠hpc.co.jp 30 May '13

30 May '13

Dear Members, I often program CUDA applications and use Boost with comforts. And I found Boost did not work fine when NVCC used a user-defined backend C++ compiler with the -ccbin option. The current implementation of Boost only identifies GCC and Visual C++ that are the default backend compilers of NVCC. So I wrote a patch for other backend compilers. It ports the generic identification routine of select_compiler_config.hpp to nvcc.hpp. Best regards, Ryohei

1 0