Linked by Thom Holwerda on Wed 11th Jun 2008 23:37 UTC
Thread beginning with comment 318268
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.





Member since:
2005-07-07
For instance, how does it compare to Intel's Thread Building Blocks library (www.threadingbuildingblocks.org), which was open sourced (GPLv2) last year? It is described as "C++ template library that simplifies the development of software applications running in parallel."
Apple has not released any information on OpenCL, which I find rather amusing for something touted as "open"
Intel's threading building blocks would not be suitable for general OS X development. While it is a nice library, it is too reliance on templates and it borrows heavily from the STL. That's a really good thing, if you're targeting C++ developers. Since the majority of development under OS X is in Objective-C*, that's not very useful.
Because of that, OpenCL has to be C based. In fact, I'm going to guess it's just a C library and if they manage to do in C what Intel have done in C++, that's still going to be very useful. Not everyone uses C++ and language bindings (for Python, Perl, etc) are a lot easier to write for C libraries.
*You can use C++ code in Objective-C++ but it's not that common as it's very complex.