Re: What's the connection between objects and threads?
On May 19, 7:10 pm, Szabolcs Ferenczi <szabolcs.feren...@gmail.com>
wrote:
On May 19, 9:13 am, "Chris Thomasson" <cris...@comcast.net> wrote:
"Szabolcs Ferenczi" <szabolcs.feren...@gmail.com> wrote in message
news:53d7b28a-337b-4b8c-ae57-f88bf5b047cd@a1g2000hsb.googlegroups.com...
On May 18, 11:43 am, darren <minof...@gmail.com> wrote:
3. A successful accepted connection is put into a queue (from the ST=
L
library).
4. Meanwhile, back at the ranch, another thread is
created and running that continuously checks for entries
into the queue.
Be aware that although STL is thread-safe to a certain extent,
Where does the current C++ standard say that the STL is
"thread-safe to a certain extent"???
For instance here:
"The SGI implementation of STL is thread-safe only in the sense that
simultaneous accesses to distinct containers are safe, and
simultaneous read accesses to to shared containers are safe. If
multiple threads access a single container, and at least one thread
may potentially write, then the user is responsible for ensuring
mutual exclusion between the threads during the container accesses. "
http://www.sgi.com/tech/stl/thread_safety.html
As others will no doubt point out, that document isn't the
standard, and only applies to a specific implementation. Other
than that, can you give some other definition of "thread safe"
which would be applicable to the standard containers. That is
not "thread-safe to a certain extent", that is "thread-safe",
pure and simple.
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34