• Nick B (9/9) Dec 02 2009 See
• Daniel de Kok (6/19) Dec 04 2009 I read the book a bit. It is quite inconvenient that you need yet
• Dejan Lekic (3/3) Dec 04 2009 My thought exactly - STDC++ (I do not like to call it STL) should have

Nick B <"nick_NOSPAM_.barbalich" gmail.com> writes:

See

http://www.threadingbuildingblocks.org/


Does any know anything about the library ?

This library seems  to do a lot of things that this community whats to 
do with D, although it is written in C++.

It seems to allow the user to write code that will run of multiple cores

Any downside or issues ?

cheers
Nick

Daniel de Kok <me danieldk.eu> writes:

On 2009-12-03 04:34:31 +0100, Nick B <"nick_NOSPAM_.barbalich" gmail.com> said:
 See
 
 http://www.threadingbuildingblocks.org/
 
 
 Does any know anything about the library ?
 
 This library seems  to do a lot of things that this community whats to 
 do with D, although it is written in C++.
 
 It seems to allow the user to write code that will run of multiple cores
 
 Any downside or issues ?

I read the book a bit. It is quite inconvenient that you need yet 
another set of containers and functions. Currently, I am more in favor 
of making the standard algorithms parallel when requested. It should be 
painless, without rewriting too much code.

-- Daniel

"Dejan Lekic" <dejan.lekic gmail.com> writes:

My thought exactly - STDC++ (I do not like to call it STL) should have  
this functionality inside, switchable with some macro definition, like  
"ENABLE_PARALLELISM" or something...