By Arch Robison
Moving your application from TBB 2.2 to TBB 3.0 should be painless. We take backward compatibility seriously, and try to avoid breaking changes. But occasionally we judge the benefit of a break to outweigh its costs. For TBB 3.0, the breaking changes are few. It’s unlikely you’ll run into trouble with them.

Breaking Changes

The breaking changes for TBB 3.0 are that the following methods of class task are changed to static methods:

* spawn
* destroy
* allocate_additional_child_of

The changes are unlikely to break existing code, because these methods are almost always used in expressions such as “x.spawn(y)”, where x and y are expressions. Though spawn is now a static method, the expressions x and y are still evaluated. The only difference is that the value of expression x is no longer used by method spawn.

Full Story