Boost logo

Boost Users :

Subject: Re: [Boost-users] interprocess_condition::wait(scoped_lock<interprocess_upgradable_lock> &) missing
From: Ion Gaztañaga (igaztanaga_at_[hidden])
Date: 2011-02-04 13:54:43


El 04/02/2011 3:05, Howard Hinnant escribió:

> In this set condition_variable_any and unique_lock are in C++0x. I
> hope to propose shared_lock and shared_mutex for tr2 and ultimately
> c++1x. Field experience here (good or bad) would help. Here is a
> tutorial and implementation of the shared and upgrade mutexes and
> locks:
>
> http://home.roadrunner.com/~hinnant/mutexes/locking.html
>
> Here is an implementation of condition_variable_any:
>
> http://llvm.org/svn/llvm-project/libcxx/trunk/include/condition_variable

Thanks Howard! Just two comments:

a) Windows Vista condition variables natively supports Slim
Reader/Writer Locks
(http://msdn.microsoft.com/en-us/library/ms686304%28v=VS.85%29.aspx),
the implementation could take advantage of this if shared_mutex is based
on this primitive.

b) Is there any reason to store shared_ptr<mutex> instead of a mutex?

Best,

Ion


Boost-users list run by williamkempf at hotmail.com, kalb at libertysoft.com, bjorn.karlsson at readsoft.com, gregod at cs.rpi.edu, wekempf at cox.net