How does OpenMP 3.0 work better with C++ (Part 2)?
Michael_Wong 120000M1EH Visits (8408)
This part will talk about enabling threadprivatization of static class member variables.
In 2.5, as a result of ambiguous language, the support for this was inconsistent. In general, it would claim that a threadprivate variable must be namespace, file or block scope.
In 3.0, this code is now allowed:
This may seem a trivial change, but for C++, it enables a powerful idiom of singletons and allocators, which all rely on static class member variable.
Next posting will continue with the semantics of private, first/lastprivate, thre