Re: Threading in new C++ standard
On Apr 17, 11:31 pm, "Chris Thomasson" <cris...@comcast.net> wrote:
"Szabolcs Ferenczi" <szabolcs.feren...@gmail.com> wrote in message
news:2427d471-dad0-4b26-ab9e-7eaf26353c9d@d1g2000hsg.googlegroups.com...
On Apr 16, 12:28 am, "Dann Corbit" <dcor...@connx.com> wrote:
Rather than create a new way of doing
things:http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2497.htm=
l
...
I like that some higher level construction is also there at last (at
condition_variable):
[...]
Indeed. That's a major plus for me. The really cool thing, for
me at least, is that the next C++ will allow me to create a
100% standard implementation of my AppCore library
<http://appcore.home.comcast.net> which currently uses POSIX
Threads and X86 assembly. The fact that C++ has condition
variables, mutexs, atomic operations and fine-grain memory
barriers means a lot to me. Finally, there will be such a
thing as 100% portable non-blocking algorithms. I think that's
so neat.
That was, I believe, a do or die requirement from some of the
participants.
I haven't mentionned it much here because it's not really
relevent to the work I do, and I'm not too familiar with it.
But it is definitly one reason why just adopting an existing
library isn't sufficient. Threading is used for different
purposes, at different levels, and someone who's interested in
parallelizing array operations on a multi-core system will have
different requirements than someone who just needs a worker
thread in a GUI.
--
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