October 2013 - Boost - lists.boost.org

[website][getting started] Linking to binaries
by Daniel James 08 Oct '13

08 Oct '13

On 8 October 2013 15:58, Tom Kent <lists(a)teeks99.com> wrote: > > The corresponding windows binaries for msvc-8.0, msvc-9.0, msvc-10.0, and > msvc-11.0 in 32 & 64 bit versions are now also available from sourceforge. > > https://sourceforge.net/projects/boost/files/boost-binaries/1.55.0_beta1/ We should probably link to binaries from the website somewhere. If not in the release notes, maybe there should be some information about alternative downloads on the download page. Any opinions? Also for other platforms? (e.g. debian packages). The getting started guide used to mention the old binaries, you can see what was removed at: https://svn.boost.org/trac/boost/changeset/82893/trunk/more/getting_started… We could put back something like that. Especially if anyone fancies writing it? I don't use windows much so I'm not the best person.

1 0

[graph] porting code from 1.46 to 1.54
by Maurizio Vitale 08 Oct '13

08 Oct '13

Hello boost, I'm trying to move some large code base to use boost 1.54. In some dark corner of it, the following was compiling fine: class Instance; typedef boost::setS OutEdgeList; typedef boost::listS VertexList; struct InstancePropertyTag { typedef boost::vertex_property_tag kind; }; typedef boost::property<InstancePropertyTag, Instance*> InstanceProperty; typedef boost::adjacency_list<OutEdgeList, VertexList, boost::bidirectionalS, InstanceProperty> Graph; typedef boost::property_map<Graph, boost::vertex_index_t>::type IndexGraph; under 1.54, I get 'attempt to form reference to void', but everything was fine under 1.46. I traced it a bit through template expansion, and the problem seems to be that the type for vertex_index_t is not found. The following declaration for InstanceProperty fixes (or hides) the problem: typedef boost::property<InstancePropertyTag, Instance*, boost::property<boost::vertex_index_t, int> > InstanceProperty; Does somebody know if some properties were added by default to graphs before and need to be explicitly added now? I don't find anything in the documentation and all examples I've found seem to imply that one wouldn't need to explicitly add a property declaration of vertex_index_t. Thanks a lot, Maurizio

3 4

[1.55.0] Release branch now open
by Marshall Clow 08 Oct '13

08 Oct '13

The release branch is now open for bug fixes and doc updates, without need to ask for a release manager's permission. It will remain open until Monday, October 28th. The 1.55.0 release is scheduled for November 4th. -- Marshall

1 0

[1.55.0] Release Notes
by Daniel James 08 Oct '13

08 Oct '13

Hello, If you haven't already, can you write your release notes for 1.55? You can send them to me, or add them yourself at: http://svn.boost.org/svn/boost/website/public_html/live/feed/history/ They're on the website at: http://www.boost.org/users/history/version_1_55_0.html thanks, Daniel

12 24

Boost.Application : Request for comments : Article / Thread Pool / Other Features / Documentation
by Renato Forti 08 Oct '13

08 Oct '13

Hi All, In this email I would like to discuss some areas of Boost.Application. 01) Thread Pool functionality One of the most recurring requests is that Boost.Application should provide Thread Pool functionality. A flexible Thread Pool can be a complex thing, need provide schedule polices, grow/reduce polices, Shutdown policies, deadline s and many others, and then I think that this feature devotes your own Boost library. The Boost.Application can be integrated easily with one Thread Pool provided by third parties, or the user can make one "specific" (Not flexible/Complex) to your needs, e.g.: I make a simple work queue model using Boost.Asio and Boost.Thread that I plug on Boost.Application, see these tutorial: * Creating a Work Queue (Thread Pool) Application Using Boost.Asio, Boost.Thread and Boost.Application http://www.codeproject.com/Articles/664709/Creating-a-Work-Queue-Thread-Pool -Application-Usin My question is: The boost users think that Boost.Application must provide a complex Thread Pool to be accepted? 02) Ideas (new features) So far these are the ideas proposed to improve Boost.Application: http://www.dokfile.com/appbeta3/docs/libs/application/doc/html/application/f uture.html What functionality do you think should already be included in the first release, and not only in future versions? (Please mention here!) If you have any other ideas, (or improvement of current list) please post here so that I can update the "TODO" session. 03) Articles About "Boost.Application" I published other articles about "Boost.Application" on Code Project Website. Code Project Tutorials * Create a Windows Service Application http://www.codeproject.com/Articles/662221/Create-a-Windows-Service-Applicat ion-Using-the-Boo 04) Documentation Feedback Also, the library documentation was updated. If someone can take a look! Please, tell me if this is a little more understandable. * On-Line Documentation http://www.dokfile.com/appbeta3/docs/libs/application/doc/html/index.html 05) Boost.Application Resources [Other Boost.Application Resources] * Download Last Version https://sourceforge.net/projects/boostapp/ Note that the latest version is (10/07/2013): Boost.Application_beta_3a_release_5.zip (1.4 MB) * Please Write a Review https://sourceforge.net/projects/boostapp/reviews Please send comments. (Specify if you think if the library should be accepted as part of boost) Thank you very much! -- Renato

4 6

1.55.0 beta 1 release candidates available for testing
by Marshall Clow 08 Oct '13

08 Oct '13

Release candidate files for 1.55.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: 9fa020efb06f5485628c646451b927c6 *boost_1_55_0b1_rc1.tar.gz 02d26b038ac96f19c3478d0c45a63c9b *boost_1_55_0b1_rc1.tar.bz2 de5f7d60b2387c4fe3d03eb327f095a9 *boost_1_55_0b1_rc1.zip 7deb9063846873452e6ec6918cb75a87 *boost_1_55_0b1_rc1.7z Thanks, --The release managers

7 13

Boost result_of maintainer
by Daniel Walker 07 Oct '13

07 Oct '13

Hi all, I have been the maintainer of boost::result_of since Doug Gregor handed it over to me a few years ago, but my circumstances are changing, and I'm afraid it's time for me to hand the library over to someone else. Any volunteers? - Daniel

3 5

boost 153 interprocess_mutex much slower in windows 7 than xp?
by Noll, Jeffrey T UTAS 07 Oct '13

07 Oct '13

We have 3 processes that are synchronized with an interprocess mutex. Basically one of them has a multiplier which allows the others to run at a synchronized accelerated rate. Under XP we typically can get it to run at 5000 times realtime. New desktop refreshes are coming out running Windows 7 and the same code with faster machines with more memory are maxing out at 250 times with 95%+ cpu idle time. Am new to boost so am wondering if we're doing something wrong. Here's the crux of the code. 3 processes and some shared memory. Share memory defines struct ds_control_sync { boost::interprocess::interprocess_mutex mutex; //Mutex to protect access to the queue boost::interprocess::interprocess_condition cond_running; //Condition to wait when the control software is running boost::interprocess::interprocess_condition cond_timestep; //Condition to wait until the control software is to run again }; struct ds_plant_sync { boost::interprocess::interprocess_mutex mutex; //Mutex to protect access to the queue boost::interprocess::interprocess_condition cond_running; //Condition to wait when the plant software is running boost::interprocess::interprocess_condition cond_timestep; //Condition to wait until the plant software is to run again }; Control process has a thread that waits for a signal to run once. DWORD __stdcall Control_Sync (LPVOID) { scoped_lock<interprocess_mutex> lock(sm_control_sync->mutex); while (1) { sm_control_sync->cond_running.notify_one(); sm_control_sync->cond_timestep.wait(lock); ns_common::TimeProfile_Periodic (&sm_io->status.control_sync, &sync_first, &sync_time); Control_PWM (); if (control_run) { Control_Run (); control_run = FALSE; } else { control_run = TRUE; } ns_common::TimeProfile_Execution (&sm_io->status.control_sync, &sync_first, &sync_time); } } Plant process has the same sort of thing DWORD __stdcall Plant_Sync (LPVOID) { scoped_lock<interprocess_mutex> lock(sm_plant_sync->mutex); while (1) { sm_plant_sync->cond_running.notify_one(); sm_plant_sync->cond_timestep.wait(lock); ns_common::TimeProfile_Periodic (&sm_io->status.plant_sync, &sync_first, &sync_time); Plant_Run (); ns_common::TimeProfile_Execution (&sm_io->status.plant_sync, &sync_first, &sync_time); } } And then main process counts down a multiplier to increase it's run rate. In this case 10000X boost::interprocess::scoped_lock<boost::interprocess::interprocess_mutex> plant_lock(plant_sync.mutex); boost::interprocess::scoped_lock<boost::interprocess::interprocess_mutex> control_lock(control_sync.mutex); mult = 10000; if(mult > 1) { iterations = 0; while(mult-- > 0) { plant_sync.cond_timestep.notify_one(); control_sync.cond_timestep.notify_one(); plant_sync.cond_running.wait(plant_lock); control_sync.cond_running.wait(control_lock); iterations++; } } Works great under XP, our new Windows 7 desktops it are dog slow by a factor of around 50. Any ideas why this would be? Thanks! Jeffrey Noll Software Engineer (860)654-6378 CONFIDENTIALITY WARNING: This email may contain privileged or confidential information and is for the sole use of the inteded recipients. Unauthorized disclosure or use of this communication is prohibited. If you believe that you have received this email in error, please notify the sender immediately and delete it from your system.

5 5

Re: [boost] boost 153 interprocess_mutex much slower in windows 7 than xp?
by jim＠jc-bell.com 07 Oct '13

07 Oct '13

> We have 3 processes that are synchronized with an interprocess mutex. > Basically one of them has a multiplier which allows the others to run at a > synchronized accelerated rate. Under XP we typically can get it to run at > 5000 times realtime. New desktop refreshes are coming out running Windows > 7 and the same code with faster machines with more memory are maxing out > at 250 times with 95%+ cpu idle time. > > Am new to boost so am wondering if we're doing something wrong. Here's the > crux of the code. 3 processes and some shared memory. > ... It might be hitting the disk when it shouldn't be. Try pointing SysInternals' ProcMon at each and see if one's doing file accesses where the other isn't. (SysInternals.com.)

1 0

[interest] rich-typed smart pointers
by Julian Gonggrijp 07 Oct '13

07 Oct '13

Dear Boost members, I have designed a smart pointer that relies on the type system to offer safe and flexible automatic memory management at no runtime cost. It combines single ownership as in std::unique_ptr and reliable access from multiple places as in std::shared_ptr with some additional features. I believe it to be about as safe and practically useful as a smart pointer in C++11 could get. Further explanation and a proof-of-concept implementation is available over here: https://github.com/jgonggrijp/rich-typed-pointers There is no license yet, but you have my explicit permission to try the library and the example programs at your own risk. :-) Could this library be useful addition to Boost? I look forward to your comments. Thanks in advance, -Julian PS: a possible minor seed for discussion is the current lack of an implicit cast to bool. I agree with Jeff Flinn's argument why the implicit cast may be desirable [1]. However, it interferes with the comparison operators when one of the operands should be implicitly cast to weak_ptr, as explained in [2]. I could repeat myself and write comparison functions for all possible overloads, but this seems inelegant. [1] http://boost.2283326.n4.nabble.com/Looking-for-thoughts-on-a-new-smart-poin… [2] https://github.com/jgonggrijp/rich-typed-pointers/commit/89fcf2821cb39bbb9f…

5 24