protecting access to std::map

[Shea Martin]

I have multiple threads that need access to single std::map. Currently
I am using mutex's to regulate ANY access to the list.

My questionion is, is it safe to have multiple threads READING the list
at the same time, so long as they don't alter it?

~S

 

[joe]

I have multiple threads that need access to single std::map.
Currently I am using mutex's to regulate ANY access to the list.

My questionion is, is it safe to have multiple threads READING the
list at the same time, so long as they don't alter it?

Theoretically, unless there's a thread writing to it as well.

Try posting this question to comp.programming.threads

Joe

 

[Fletcher Glenn]

Theoretically, unless there's a thread writing to it as well.

Try posting this question to comp.programming.threads

Joe

I would have to agree with this answer. Many std::map's are
implemented as an AVL tree under the covers. It would not
do to well to be doing a read-only walk down a tree when the
pointers begin shifting around.