Subj : Re: Is locking required for this scenario
To   : comp.programming.threads
From : Torsten Robitzki
Date : Tue Feb 01 2005 10:12 pm

nin234@yahoo.com wrote:

> I have a global container (of type List ) which I plan to initialize
> during the daemon start up/initialization. During this time period
> there will be no reads on this container. Once the daemon is
> initialized multiple threads will simultaneously access the container
> for reading it's contents (ie it will iterate  through the container
> contents). But there will be no modification of the container contents
> during this phase. Does this container require synchronisation/locking.
> Ninan
> 

if you are done with the initialization of the container before you 
start any thread that will read that container later, there is a good 
chance that you will not need any locking. But this will depend on the 
implementation details of the container too. I've seen some silly static 
variables in even commercial C++ standard container implementations.

regards
Torsten

.