CP guidelines for mutex in class

[KindDragon]

Try to use single mutex to protect all class data members
http://stackoverflow.com/a/14600868/61505

If you have several mutexes in one class try to divide to several classes or at least document which mutex protect which data members.

[AndrewPardoe]

Jonathan, can you take a stab at this? We should consider surfacing an anti-pattern (Monitor, with the nearly always wrong locking granularity) before discussing the pattern (synchronized object).

Herb suggests there is a second distinct issue of recursive mutexes: Releasing before the nested transaction and then re-acquiring, which makes it clear that these are two transactions. We may not want to capture this problem as it is discussed .

[jwakely]

c.f. http://www.drdobbs.com/windows/associate-mutexes-with-data-to-prevent-r/224701827 and http://www.drdobbs.com/cpp/enforcing-correct-mutex-usage-with-synch/225200269