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

Migrating www.boost.org to another server
by DongInn Kim 17 Jun '13

17 Jun '13

Hi, The CREST is planning to move all the boost services that OSL/CREST has provided to another server. All the services in the current OSL/CREST server are: - Web services: www.boost.org boostcon.boost.org svn.boost.org/svnmanager svn.boost.org/trac/boost beta.boost.org - Subversion, trac, and SVNManager - Mailinglist mailman hypermail First, we would like to migrate www.boost.org and beta.boost.org which are not dependent on any other services and domains at all. The data of www.boost.org and beta.boost.org can be simply moved but I need someone's help who can switch the domain record to make these two hostnames point to the new server. Who can I talk to about this domain migration? I will setup another schedule for the next migrations and I do not have any particular lists yet but probably the rest of web services and Subversion would be the candidate. We will see. Regards, -- - DongInn

4 7

[parameter] BOOST_PARAMETER_CONSTRUCTOR bug
by James Hirschorn 10 Jun '13

10 Jun '13

I've already submitted a bug report, but I'm also posting it here in case anyone has more info. ------------- The following variation on the example from the boost::parameter tutorial, where the required parameter is changed to optional, fails to compile. myclass_impl is being passed an empty argument list. #include <iostream> #include <boost/parameter.hpp> BOOST_PARAMETER_NAME(name) BOOST_PARAMETER_NAME(index) struct myclass_impl { template <class ArgumentPack> myclass_impl(ArgumentPack const& args) { std::cout << "name = " << args[_name] << "; index = " << args[_index] << std::endl; } }; struct myclass : myclass_impl { BOOST_PARAMETER_CONSTRUCTOR( myclass, (myclass_impl), tag , (optional (name, *) (index, *) ) ) // no semicolon }; int main(int argc, char * argv[]) { myclass C(_name="hello", _index=0); }

3 6

[GIL] Can image::recreate reuse the memory?
by TONGARI 06 Jun '13

06 Jun '13

Hi, I'd expect image::recreate to reuse the memory much like std::vector::resize, but looked into the code shows that it creates a new one and swaps... So, is there a way to 'resize' the image without reallocating if the internal memory is sufficient? Thanks

2 17

Migrating svn.boost.org
by DongInn Kim 06 Jun '13

06 Jun '13

Hi, This time I would like to setup a schedule to migrate svn.boost.org to the new server (wowbagger.crest.iu.edu) This migration may need some downtime on the subversion, trac, and svnmanager services because we do not want to have any inconsistencies in SVN and or trac database. I have already rsynched the 1) boost SVN repository including its hook script, 2) trac db, and 3) SVNManager and its database. Do you have any hidden processes to manage the subversion repository, trac, or SVNManager? I implemented some simple testings with some SVN activities on the new server and it seems to work fine. Can anyone volunteer to play with the migrated SVN repository, trac, and SVNManager on the new server? I can test the very basic stuff and I may miss some functionalities of the current services. If anyone who actually work on the boost project can check this out, it would be much appreciated. I would feel much safer. 1. The downtime that we may have while migrating svn.boost.org I expect that TTL value be changed to 1hour or so. While the new DNS entries are populated, the current server will NOT service svn.boost.org and the new server will instead. - Date: Wednesday June 5th, 2013 - Time: 11:00am-12:00pm Pacific US time 12:00pm-1:00pm Mountain US time 1:00pm-2:00pm Central US time 2:00pm-3:00pm Eastern US time 6:00pm-7:00pm GMT 2. The unavailable services hosted on svn.boost.org : - Subversion - trac - SVNManager 3. The DNS entries to update: - Make svn.boost.org and wiki.boost.org point to 129.79.13.33 Please let me know if you have any questions or concerns about this migration. Regards, -- - DongInn

7 15

Re: [boost] [circular_buffer] New version of documentation
by Paul A. Bristow 06 Jun '13

06 Jun '13

> -----Original Message----- > From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Marshall Clow > Sent: Thursday, May 23, 2013 8:01 PM > To: boost(a)lists.boost.org > Subject: Re: [boost] [circular_buffer] Volunteer(s) needed After more work than I bargained for (see below for excuses) I have produced a Quickbook, Doxygen, Autoindex version from the existing documentation for Boost.Circular_Buffer at https://svn.boost.org/svn/boost/trunk/libs/circular_buffer/doc/circular_buf… I have made few substantive changes to the text, mainly adding more hyperlinks, (and correcting some that were wrong of missing - using the inspect tool is a really, really good idea!) So that users can comment on this new version, I have put html and pdf versions in my Dropbox. The pdf version is at https://dl.dropboxusercontent.com/u/43940943/circular_buffer.pdf which can of course be viewed by any PDF reader (I have recently moved to using Foxit instead of Adobe Reader). The html Quickbook version is from folder (libs/circular_buffer/doc/html) the at https://dl.dropboxusercontent.com/u/43940943/html/index.html (Sadly some of the icon .png files are inaccessible from the Dropbox version, which mars its beauty but you'll get the idea). This library uses the full automatic indexing of C++ names and hyperlinking to and from the text. The header files have the classes and functions fully documented in Doxygen format, and this is used to create the C++ reference sections: https://dl.dropboxusercontent.com/u/43940943/html/boost_circular_buffer_c__… to that you can see what the classes do and the parameters, template parameters, returns etc for the functions. I believe that these details are essential for Really Useful documentation. The original Doxygen standalone (whose format some users prefer) is at https://dl.dropboxusercontent.com/u/43940943/doxygen/html/index.html So you can see the pros and cons of the same information displayed side by side. The PDF and HTML versions also has an index at the end (this could be improved as it only gives C++ functions etc at present). Enjoy! (?) Comments welcome - praise preferred ;-) Paul PS Implementation notes: To get all the links correct proved *very* tiresome. Much of the trouble was inconsistent layout of existing documentation and files. IMO we need to use the GITMOD project to impose much more order on the file structure. I fear that the modularization changes will invalidate many links in documentation, so much revision will be needed :-( We must be able to predict where index.html etc will be to be able to write links without the current hassle. The Boost inspect tool proved invaluable, and all links are now reported correct. (Lots were wrong - in Doxygen comments in the header files, and in the Quickbook stuff :-( ) Despite this, there are still some sections in red where the html layout is wrong :-( I hope to find all of these in a later revision. --- Paul A. Bristow, Prizet Farmhouse, Kendal LA8 8AB UK +44 1539 561830 07714330204 pbristow(a)hetp.u-net.com

2 3

[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