Re: Request for comments about synchronized queue using boost
On Oct 17, 10:24 am, Szabolcs Ferenczi <szabolcs.feren...@gmail.com>
wrote:
On Oct 17, 9:43 am, James Kanze <james.ka...@gmail.com> wrote:
On Oct 16, 5:42 pm, Szabolcs Ferenczi <szabolcs.feren...@gmail.com>
wrote:
On Oct 15, 3:36 pm, Nordl=F6w <per.nord...@gmail.com> wrote:
[...]
Are there any resources out there on the Internet on how to
design *thread-safe* *efficient* data- structures?
Sure.http://www.google.nl/search?q=boost+thread+safe+queue=
You have to be very careful with googling in cases like
this. There's an awful lot of junk on the net. Just
looking at the first hit, for example, it's quite clear that
the author doesn't know what he's talking about, and I
suspect that that's true in a large number of cases.
Hmmmm... For me the first hit is a didactic piece by Anthony
Williams:
Implementing a Thread-Safe Queue using Condition Variables ...
In those cases, it might be worth using something like boost::optional
to avoid this requirement ... Tags: threading, thread safe, queue,
condition variable ...www.justsoftwaresolutions.co.uk/threading/implement=
ing-a-thread-safe-...
Yep. That was the example I was talking about.
Saying that "it's quite clear that the author doesn't know
what he's talking about" is, hmmm..., at least indicates
something about you.
Yes. That I know a bit about programming in a multithreaded
environment, and can spot basic stupidities right away.
I do not want to defend him but if you just read it to the
end, you must have learnt something, I guess.
I learned that he doesn't fully understand the implications.
You should not stop by the first fragment which is just a
starting point illustrating the problem.
When I see threaded code returning a reference into a protected
structure, after having freed the lock, I stop. No one who
understands threading would ever write something like that.
I agree in that he should not have suggest such a bad habit of
handling a shared resource in the front part of his article
or, at least, he should have warned the smattering reader that
it is not the correct way.
The rest just goes on to present what everyone knows anyway.
--
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