how to make stl thread safe

Question

0.00/5 (No votes)

See more:

C++

template<typename container="">
class Lock {
public:
    // have been omitted
    Lock(const Container& container)
        : c(container){
            getMutexFor(c);
    }
 
    ~Lock() {
        releaseMutexFor(c);
    }
private:
    const Container& c;
};

How to realize the releaseMutexFor and getMutexFor?

Posted 20-Nov-13 2:21am

G.aius.CodeCreator

Updated 20-Nov-13 7:54am

nv3

v2

Add a Solution

Comments

Philippe Mori 20-Nov-13 18:33pm

Contrary to .NET (C#, C++/CLI...), I don't think it is possible to do that in C++. One of the way would be to have a structure that contains the container and its lock... or maybe have a wrapped class so that no direct access is made to the container.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

nv3 · Answer 1 · 2013-11-20T09:43:00

Your idea is intriguing, but I guess it won't work. For a mutex to be effective it has to be part of or at least associated to the object it is supposed to protect. So you don't want to have one mutex per Lock object, but one mutex per container object.

A possible mechanism would be to allocate a map in you lock class that associates each container object with a dedicated mutex that is help by the Lock object. However, this approach won't really work, because your Lock object will not be informed when a container is destroyed. And hence your map will get bigger and bigger over time.

I don't see how it could be effectively done what you are trying.

CPallini · Answer 2 · 2013-11-20T02:44:00

Solution 1

Why don't you use C++11 locks? See, for instance C++11 threads, locks and condition variables[^].

Posted 20-Nov-13 2:44am

CPallini